MCP Overview

Sprigr Teams supports the Model Context Protocol (MCP), an open standard that lets AI applications connect to external tools and data sources. With MCP enabled, you can manage your entire Sprigr Teams platform — agents, workflows, knowledge bases, marketplace apps, schedules, and more — directly from tools like Claude Code, Cursor, VS Code, and any other MCP-compatible client.

This is not just a chatbot bridge. The MCP server exposes 41 tools that give you full read and write access to the platform, so your external AI client becomes a complete management interface for your Sprigr Teams workspace.

What is MCP?

The Model Context Protocol is an open standard for connecting AI assistants to external systems. Think of it like a universal adapter: instead of building custom integrations for every AI tool, MCP provides a single protocol that any compatible client can use to discover and call tools from any compatible server.

Sprigr Teams acts as an MCP server, exposing your agents, knowledge bases, workflows, apps, and platform management capabilities as tools that external AI clients can use.

How it works

When you connect an MCP client (like Claude Code or Cursor) to your Sprigr Teams workspace:

1. The client discovers all 41 tools available in your workspace
2. You can invoke those tools from within the client’s interface
3. Most tools call the Sprigr Teams API directly — no AI tokens consumed, no latency from agent processing
4. Only send_message routes through an agent (because that is the one operation where you want the agent to think and respond)
5. Results are returned to the client and incorporated into the conversation

This architecture means you can list agents, create workflows, search knowledge bases, manage apps, and configure schedules without any agent token cost. The MCP client itself is the intelligence — it reads data through Sprigr Teams, decides what to do, and writes changes back directly.

MCP Client → MCP Worker → Provisioning API → Database
                                (direct — no agent involved, no tokens used)

MCP Client → MCP Worker → Gateway → Agent → AI Response
                                (only for send_message — uses agent tokens)

Supported clients

Sprigr Teams works with any application that supports the MCP standard via Streamable HTTP transport. Popular clients include:

• Claude Code — Anthropic’s CLI tool for developers (recommended — supports remote HTTP servers natively)
• Claude Desktop — Anthropic’s desktop application (add via Settings > Integrations)
• Cursor — The AI-powered code editor
• VS Code — With MCP-compatible extensions
• Any MCP client — Any application that implements the MCP Streamable HTTP client specification

Available tools via MCP

Sprigr Teams exposes 41 tools through MCP, organised into read tools and write tools. Which tools are available depends on the API key’s scope.

Read tools (21 tools)

Read tools fetch data from your platform without consuming any agent tokens:

Tool	Description
list_agents	List all agents with name, slug, status, and role. Use the slugs from this list to call other tools.
get_agent_info	Get detailed agent configuration including persona, model tier, and integrations.
list_teams	List all agent teams in the company.
get_team	Get team details including members and routing rules.
list_workflows	List all workflows.
get_workflow	Get workflow details including steps and configuration.
list_executions	List recent workflow executions across all workflows.
list_apps	List all marketplace apps available to the company.
get_app	Get app details including versions and installation status.
list_webhooks	List all configured webhooks.
list_integrations	List all connected integrations (simPRO, Xero, Gorgias, etc.).
list_users	List all team members.
get_usage	Get company usage statistics (messages, tokens, costs).
get_plan	Get current subscription plan and limits.
get_dashboard	Get dashboard overview: active agents, messages today, monthly spend, escalations.
list_schedules	List all scheduled tasks.
search_knowledge	Search an agent’s knowledge base using natural language.
list_knowledge	List knowledge base entries.
list_conversations	List recent conversations for a specific agent.
list_threads	List inbox threads (support tickets, customer conversations).

Write tools (20 tools)

Write tools create, update, and manage platform resources:

Tool	Description
send_message	Send a message to an agent and receive its AI response. This is the only tool that consumes agent tokens.
create_agent	Create a new AI agent with name, slug, persona, and model tier.
update_agent	Update an existing agent’s configuration (persona, status, model tier, etc.).
create_team	Create a new agent team for collaborative task routing.
add_team_member	Add an agent to a team.
remove_team_member	Remove an agent from a team.
create_workflow	Create a multi-step workflow with agent assignments and approval gates.
update_workflow	Update an existing workflow’s steps or configuration.
start_workflow	Start a workflow execution with optional input data.
approve_execution	Approve or reject a workflow step that requires human approval.
create_app	Create a new marketplace app with code that runs in a V8 isolate sandbox.
install_app	Install a marketplace app with specific scopes and agent restrictions.
uninstall_app	Remove a marketplace app from the company.
publish_version	Publish a new version of an existing marketplace app.
create_webhook	Create a new webhook endpoint (inbound or outbound).
write_knowledge	Write or update entries in an agent’s knowledge base.
create_knowledge	Create a new knowledge base entry.
create_schedule	Create a scheduled task with a cron expression and prompt.
update_schedule	Update or toggle a scheduled task.
delete_schedule	Remove a scheduled task.
invite_user	Invite a new team member to the company.

User-level permissions

Every MCP API key is linked to the user who created it. The key inherits that user’s data visibility — the same restrictions they have in the portal apply through MCP:

• An admin or owner key sees all agents, conversations, threads, and company data.
• A member key only sees agents they are assigned to and their own conversations.

All 41 tools remain available to every user regardless of role. The difference is in what data comes back. A member calling list_agents sees only their assigned agents. An admin calling list_agents sees every agent in the company.

This ensures that MCP access never exceeds what the user can do through the web portal. You cannot gain broader access by using MCP instead of the dashboard.

Use your own AI tokens to build infrastructure

This is one of the most powerful aspects of the MCP integration: when you connect Claude Code, Cursor, or Claude Desktop to Sprigr Teams, the AI reasoning happens on your side using your own Claude tokens (from your Anthropic subscription or IDE licence). Sprigr Teams just serves as the data layer.

Here is why that matters:

• 40 out of 41 tools are free API calls. When Claude Code calls list_agents, create_workflow, or install_app, it hits the Sprigr provisioning API directly. No Sprigr agent is involved. No Sprigr tokens are consumed. The intelligence is your Claude session — it reads data, reasons about it, and writes changes back.
• Only send_message uses Sprigr agent tokens. This is the one tool where you deliberately want a Sprigr agent to think and respond — for example, asking your Gorgias agent to check for urgent tickets. Everything else is a direct database operation.
• Your AI client does the heavy lifting. When you ask Claude Code to “set up a new agent team with three specialists and a workflow”, Claude plans the work, calls create_agent three times, calls create_team, calls add_team_member three times, and calls create_workflow — all using your Claude tokens for the reasoning and Sprigr’s free API for the execution.

This means you can use the most capable AI models available to you (Claude Opus, Sonnet, or whatever your IDE provides) to orchestrate complex platform setup — without worrying about Sprigr token costs for the planning and decision-making.

Example: Setting up a new department from your IDE

Imagine you are onboarding a new finance department. In Claude Code, you say:

“Set up our finance department. Create three agents — an Accounts Payable agent, an Accounts Receivable agent, and a Financial Reporting agent. Put them in a team called ‘finance-team’. Give the AP agent a persona focused on invoice processing and supplier management. Give the AR agent a persona for customer invoicing and collections. Give the reporting agent a persona for generating P&L summaries and expense reports. Then create a workflow called ‘Monthly Close’ with steps for each agent to compile their data and a final approval gate for the CFO.”

Claude Code reads the instruction, plans the work, and executes it using MCP tools:

1. create_agent × 3 — creates each agent with tailored personas (free)
2. create_team — creates the finance-team (free)
3. add_team_member × 3 — adds each agent to the team (free)
4. create_workflow — creates the Monthly Close workflow with steps and an approval gate (free)

Total Sprigr token cost: zero. All the reasoning was done by your Claude Code session using your own Anthropic tokens. Sprigr just processed the API calls.

Example: Building and deploying a custom app

“Create a marketplace app called ‘invoice_status’ that connects to our Xero API and returns the status of an invoice by number. It should accept an invoice number as input and return the invoice status, amount, due date, and whether it’s overdue. Declare Xero as a required dependency. Use the domain api.xero.com in the allowlist.”

Claude Code writes the handler code, defines the input schema, and calls create_app — all in one shot. Your Claude tokens handle the code generation. Sprigr stores and deploys the app for free.

Example: Building a website dashboard

“Create a website dashboard that shows our team’s daily metrics — active conversations, messages processed today, pending escalations, and monthly spend. Use get_dashboard to pull the data and create a clean HTML page with auto-refresh.”

Claude Code calls get_dashboard to understand the data shape, then writes the dashboard code and deploys it — all from your terminal.

Example: Communicating with your agents

When you do need an agent’s intelligence — its persona, integrations, and domain knowledge — use send_message:

“Ask the gorgias-support agent if there are any urgent tickets and have it notify Harry about the status.”

This is the one operation that uses Sprigr agent tokens, because you want the Gorgias agent to actually check Gorgias, apply its customer support expertise, and compose a notification. The cost is one agent conversation turn — the same as if you had typed the message in the portal chat.

The economics in practice

A typical MCP session might involve 20-30 tool calls to set up infrastructure, search knowledge, and configure workflows — all free. Then 1-2 send_message calls to have agents do actual work. You get the full power of your AI subscription to orchestrate the platform, and only pay Sprigr tokens when you need an agent to think.

Use cases

Full platform management

Manage your entire Sprigr Teams workspace from your IDE. Create agents, configure workflows, install apps, and invite users — all without opening the portal or spending agent tokens.

Build apps from your IDE

Write custom marketplace apps in Claude Code or Cursor. Your AI writes the handler code, defines the schema, and deploys it to Sprigr — all using your own Claude tokens for the code generation.

Automated workflows

Build and trigger complex workflows from your terminal. Create a workflow, assign agents to steps, start an execution, and approve results — all through MCP tools with zero Sprigr token cost.

Knowledge management

Write to and search knowledge bases from your external AI client. Push documentation, process data, and keep your agents’ knowledge up to date without opening the portal.

Multi-tool orchestration

Combine Sprigr Teams tools with other MCP servers in the same client. Read local files, process them with your agent’s knowledge base, and write results back — all in one conversation.

Agent conversations

Send messages to any agent and get AI-powered responses. Check urgent support tickets, ask your accounting agent for invoice status, or have your scheduling agent find available slots — the only operation that uses Sprigr tokens.

Example: checking urgent tickets from your IDE

From Claude Code or any MCP client, you can ask:

“Send a message to the gorgias-support agent asking if there are any urgent tickets, and have it notify Harry.”

This uses one send_message call (the only tool that costs Sprigr agent tokens). The Gorgias Support agent checks for urgent tickets, finds what needs attention, and notifies Harry — all triggered from your terminal.

Getting started

To connect an MCP client to your Sprigr Teams workspace, you will need:

1. An API key — Generated from the MCP page in the Sprigr Teams portal. See API Keys for instructions.
2. The server URL — https://mcp.team.sprigr.com/mcp
3. Client configuration — Depends on your client. See the API Keys page for setup instructions for Claude Code, Claude Desktop, and other clients.

Tip

For Claude Code (CLI), add the server with a single command:

claude mcp add --transport http "my-sprigr" https://mcp.team.sprigr.com/mcp --header "Authorization: Bearer sk_mcp_YOUR_KEY_HERE"

Next steps

• API Keys — Create and manage API keys for MCP access.
• Knowledge Bases — Set up knowledge bases that MCP clients can search.
• Creating Agents — Create agents that MCP clients can interact with.
• Marketplace Apps — Build and install custom tools that agents can use.