Skip to main content
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

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.
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.
Enhance your agent’s toolset with Meta Tools for real-time discovery, curation, and augmentation of available actions. Every tool has structured input/output schemas and documentation.
Toggle tools on or off, customize your toolset, or create your own connectors using StackOne’s Connector Engine and AI Builder.
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

​
Manual Testing (cURL)

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": {}
    }
  }'

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"
  }'

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 }
    }
  }'

​
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

ErrorSolution
401/403Check API key encoding and that x-account-id belongs to the same project
405Ensure you’re using POST and Content-Type: application/json
Empty tools listVerify account is active and actions are enabled in integration config
For more, see Troubleshooting Guide and Authentication & Security.