Quickstart
- Add our remote MCP server to your agent of choice using the URL:
- Authenticate with CraftCX via OAuth (run your agent mcp auth command)
- Setup is complete
Endpoint
Protected resource metadata is available at:
Authentication
CraftCX MCP uses OAuth. When you connect a client, it opens a browser flow so you can sign in to CraftCX and approve access for an organization. You do not create an API token for MCP. Authorization uses your CraftCX account and the scopes you approve during consent.Permissions
Access will be granted using the following scopes;
Tools only appear when the session includes the matching scope. The MCP server is currently read-only.
Available tools
Learn more about the product concepts these tools return:
Setup
Most agents are smart enough for you to simply ask them;
Add the CraftCX MCP server - the remote URL is https://mcp.craftcx.com/mcp
Cursor
- Open Cursor Settings → MCP → Add new global MCP server
- Paste:
- Save and restart Cursor if needed. Complete the OAuth flow the first time you use a CraftCX tool.
.cursor/mcp.json in the project root.
Claude Code
/mcp in Claude Code and complete the OAuth flow.
Codex
Add via the CLI using~/.codex/config.toml file:
OpenCode
CraftCX publishes an OpenCode remote config at:opencode.json or opencode.jsonc:
VS Code (GitHub Copilot)
Create.vscode/mcp.json in your workspace:
Claude Desktop
- Open Settings → Connectors
- Add a connector with URL
https://mcp.craftcx.com/mcp - Complete the OAuth flow
Other clients
If your tool supports remote MCP over Streamable HTTP, use:mcp-remote:
Example prompts
Once connected, try questions like:- “What are the open high-priority findings in CraftCX?”
- “Search CraftCX for conversations about refunds with low AXIS scores this month.”
- “Summarize support performance for the last 30 days.”
- “Show recent customer signal groups related to shipping delays.”
- “Open conversation
<id>and explain the findings and signals attached to it.”
Troubleshooting
- Complete the OAuth consent flow and select the correct organization.
- If tools are missing, confirm the session approved the matching
*:readscopes. - Disconnect and reconnect from your client’s MCP settings if auth state looks stale.
- Confirm you can sign in to app.craftcx.com with access to that organization.