StackOne MCPs

The Model Context Protocol (MCP) is an open protocol that standardizes how AI applications provide context to LLMs. StackOne provides production-ready MCP servers for each linked account, giving your AI agents direct access to 10,000+ actions across hundreds of integrations. See the complete list at stackone.com/integrations.

Not sure if MCP is right for you? Check out our Agent Protocols Guide to understand when to use MCP vs AI Toolset (SDK) vs A2A.

MCP Server Endpoint

https://api.stackone.com/mcp

Required headers:

Authorization: Basic <base64-encoded-api-key>
x-account-id: <account-id> (or ?x-account-id= query param)

Authentication to third-party providers is completely abstracted - you only need your StackOne API key and account ID. Accounts must be linked beforehand through the StackOne Hub or via auth links.

Fastest Way to Test

AI Playground

No setup. Test with natural language instantly

Postman

Fork the StackOne collection and test MCP requests

MCP Inspector

Run npx @modelcontextprotocol/inspector https://api.stackone.com/mcp

How It Works

The StackOne MCP Server dynamically generates its tool catalog based on your account’s configured integrations and enabled actions.

Multiple Integration Options

Use the MCP server, the Actions RPC endpoint, the Unified API endpoints, or A2A Agents, all using the same linked account. You can also access the StackOne AI Toolset for specialized LLM tools.

Accuracy & Context Engineering

Enhance your agent’s toolset with Tool Search for natural language discovery of relevant tools. Every tool has structured input/output schemas and documentation.

Customizable & Extensible

Toggle tools on or off, customize your toolset, or create your own connectors using StackOne’s Connector Engine and StackOne Agent.

Purposeful Action Design

StackOne tools aren’t direct wrappers to single API endpoints. Many are mapped to high-value, context-optimized actions tailored to common business use cases.

Framework Guides

Most frameworks support MCP natively:

Claude SDK

Vercel AI SDK

OpenAI Agents

Pydantic AI

CrewAI

Google ADK

App Guides

Claude Desktop

Goose

n8n

Postman

Manual Testing (cURL)

Initialize connection

curl -X POST https://api.stackone.com/mcp \
  -H 'Authorization: Basic <BASE64_APIKEY_COLON>' \
  -H 'x-account-id: <ACCOUNT_ID>' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{
    "jsonrpc": "2.0",
    "id": "init-1",
    "method": "initialize",
    "params": {
      "clientInfo": { "name": "my-client", "version": "1.0.0" },
      "protocolVersion": "2025-06-18",
      "capabilities": {}
    }
  }'

List available tools

curl -X POST https://api.stackone.com/mcp \
  -H 'Authorization: Basic <BASE64_APIKEY_COLON>' \
  -H 'x-account-id: <ACCOUNT_ID>' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{
    "jsonrpc": "2.0",
    "id": "tools-1",
    "method": "tools/list"
  }'

Call a tool

curl -X POST https://api.stackone.com/mcp \
  -H 'Authorization: Basic <BASE64_APIKEY_COLON>' \
  -H 'x-account-id: <ACCOUNT_ID>' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{
    "jsonrpc": "2.0",
    "id": "call-1",
    "method": "tools/call",
    "params": {
      "name": "bamboohr_list_employees",
      "arguments": { "limit": 10 }
    }
  }'

Tool Modes

The MCP endpoint supports a tool-mode query parameter that controls how tools are registered.

Mode	Tools registered	When to use
`individual` (default)	One tool per action	Small action sets, full tool visibility
`search_execute`	2 tools: search + execute	Large catalogs, context window constraints

Search & execute mode is useful when an integration exposes many actions. Instead of registering hundreds of individual tools, the server exposes just two:

{provider}_search_actions — search for actions by natural language query
{provider}_execute_action — execute an action by its action_id

The agent calls search_actions first to discover available action IDs, then calls execute_action to run the chosen action. Enable it by appending ?tool-mode=search_execute to the MCP URL:

https://api.stackone.com/mcp?tool-mode=search_execute

See Tool Modes for full details, parameter reference, and setup examples for Claude Desktop and Claude Code.

Key Features

Account Specific: Each linked account gets its own MCP server endpoint
Streamable HTTP Transport: Uses modern HTTP-based MCP transport (not SSE)
Complete Platform Access: All StackOne actions available as MCP tools
Action Selection Control: Only enabled actions from your integration config are returned
Production Ready: Authentication, rate limiting, and security built-in

Troubleshooting

Error	Solution
`401/403`	Check API key encoding and that `x-account-id` belongs to the same project
`405`	Ensure you’re using POST and `Content-Type: application/json`
Empty tools list	Verify account is active and actions are enabled in integration config

For more, see Troubleshooting Guide and Authentication & Security.

Getting Started

SDKs & Frameworks

Applications & IDEs

API Behavior

Support

MCP Server Endpoint

Fastest Way to Test

AI Playground

Postman

MCP Inspector

How It Works

Framework Guides

Claude SDK

Vercel AI SDK

OpenAI Agents

Pydantic AI

CrewAI

Google ADK

App Guides

Claude Desktop

Goose

n8n

Postman

Manual Testing (cURL)

Tool Modes

Key Features

Troubleshooting

​MCP Server Endpoint

​Fastest Way to Test

AI Playground

Postman

MCP Inspector

​How It Works

​Framework Guides

Claude SDK

Vercel AI SDK

OpenAI Agents

Pydantic AI

CrewAI

Google ADK

​App Guides

Claude Desktop

Goose

n8n

Postman

​Manual Testing (cURL)

​Tool Modes

​Key Features

​Troubleshooting

MCP Server Endpoint

Fastest Way to Test

How It Works

Framework Guides

App Guides

Manual Testing (cURL)

Tool Modes

Key Features

Troubleshooting