Agentic Server via MCP

Stood MCP: Friendly Guide for Agents and Automations

This guide helps you connect agentic platforms (like Dust.tt, Agentspace, n8n, or Mistral’s agents) to Stood using the standardized Model Context Protocol (MCP). Each team in Stood has its own API key, so agents only see the right data.

What you get

• Secure, team‑scoped access to your CRM data

• Simple, standardized MCP endpoint

• Tools for reading, creating, and updating Stood entities

1) Get your team API key

From the Stood Admin UI:

1. Open the Admin panel

2. Go to the Teams section

3. Select your team

4. Generate an API key and copy it

Keep your API key secret.

2) Endpoints (to setup into your agentic platform)

• Team-specific: https://mcp-PROJECT-od.a.run.app/{teamId}

• replace URL with your specific PROJECT ID (find it from firebase admin > functions > mcp)

• {teamId} must match the team tied to your API key.

Auth header:

Authorization: Bearer YOUR_TEAM_API_KEY

3) Available tools (high level)

• Read: get_*, list_* for accounts, contacts, deals, activities, posts

• Create: create_deal, create_activity, create_post

• Update: update_deal, update_activity

• Schema & Labels: get_entity_schema, get_team_labels, get_all_team_labels

Team filtering applies to: deals, activities, posts. Other collections are global.

4) Using agent platforms

Dust.tt

• Add a tool that connects to an MCP server.

• Configure the MCP endpoint URL and the Authorization header with your team API key.

• Give the agent instructions to use the tools to read and write deals/activities.

Prompt starter for Dust:

You are a CRM copilot for the Sales team. Use the MCP tools to:
- list_deals to review pipeline
- create_activity for follow-ups
- update_deal to move stages
When reporting, include friendly labels from get_team_labels where useful.

TIP: use Zapier to trigger agentic flows from DUST ZAP

Agentspace

• Register an MCP tool provider with the endpoint URL.

• Add the bearer API key in the provider’s auth config.

• Map actions (e.g., “Create follow-up”) to MCP tool calls.

Prompt starter for Agentspace:

Goal: Keep pipeline up to date.
Use tools:
- list_deals (filter by stage s2)
- create_activity (todo with due date)
- update_deal (stage changes, amount updates)
Be concise. Confirm actions you perform and surface next steps.

Mistral agents

• Create an agent with external tools support.

• Add the MCP server as a tool endpoint with the Authorization header.

• Instruct the agent to call tools when data is missing or changes are needed.

Prompt starter for Mistral:

Act as a sales assistant. If you need data, call the appropriate MCP tool.
Examples:
- list_deals to find deals closing this month
- create_activity for follow-ups
- update_deal to change stage to s3 when qualified
If labels are needed, call get_team_labels and use them in your response.

6) Helpful patterns

• Use list_deals then get_team_labels to present stages in your team’s language.

• After creating an activity or post, echo back the key fields to users.

• On updates, prefer minimal changes (only the fields that changed).

7) Security

• Keep API keys secret. Rotate if you suspect exposure.

• Use team-specific keys to ensure correct scoping.

• Review logs for tool usage if your platform provides them.

8) Troubleshooting

• 401/403: Check your bearer token and team match.

• Team-filtered results look empty: ensure the entity belongs to your team.

• Tool not found: refresh the tool list (tools/list) and verify name.

Contact - Stood CRM support & integration