MCP Integration

Overview

Sulus offers two distinct MCP (Model Context Protocol) integrations that share the same underlying MCP server package but serve very different purposes:

• Claude Desktop integration — exposes Sulus's platform APIs as tools so Claude can manage assistants, calls, and phone numbers conversationally, right from a chat with Claude Desktop.
• IDE integration — gives a coding assistant like Cursor accurate, up-to-date knowledge of the Sulus platform so its code suggestions and generated snippets are correct.

These are configured differently and used for different things — read the section for the one you need rather than assuming they're interchangeable.

The Sulus MCP server exposes platform APIs as tools Claude Desktop can call directly.

1. Get an API key from your Sulus Dashboard under API Keys.
2. Open Claude Desktop's Settings → Developer tab → Edit Config.
3. Add an mcpServers block to claude_desktop_config.json:

{
  "mcpServers": {
    "sulus": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.sulus.ai/mcp",
        "--header",
        "Authorization: Bearer ${CORE_SYSTEM_API_KEY}"
      ],
      "env": {
        "CORE_SYSTEM_API_KEY": "your-api-key"
      }
    }
  }
}

Save the file and restart Claude Desktop for the connection to take effect.

Once connected, Claude has access to the following tools:

With the connection configured, you can prompt Claude conversationally instead of writing API calls by hand, for example:

Have my customer support assistant call Jeremy at +15551234567 tomorrow at 10am.

Claude resolves this into the appropriate list_assistants and create_call tool calls on your behalf, using the assistant that matches "customer support" by name.

The IDE integration is separate from the Claude Desktop integration above — it gives your IDE's own AI (in Cursor or a similar editor) accurate, current knowledge of the Sulus platform's APIs and features, reducing hallucinated fields and outdated code suggestions.

Auto-configure every supported IDE in the current project:

core-system mcp setup

Or configure a single IDE explicitly:

core-system mcp setup cursor

Either command generates a project-level MCP config file (for example, a .cursor/mcp.json) that points the IDE at the @core-system/mcp-server package.

Check the current connection status at any time:

core-system mcp status

Keep the MCP server package up to date:

npm update -g @core-system/mcp-server

Remove the configuration entirely, or for a single IDE:

core-system mcp remove
core-system mcp remove cursor

• Restart the IDE after running any core-system mcp setup command — configuration changes aren't picked up until it restarts
• Check your IDE's output panel logs for MCP connection errors
• Verify npm is accessible from your IDE's environment (some IDEs use a different shell/PATH than your terminal)
• Confirm the MCP server package is installed globally: npm list -g @core-system/mcp-server
• If you see a permission error, check that your API key hasn't been revoked or rotated, and that the account running the IDE has write access to the project's MCP config directory

See CLI & API Key Auth for how the underlying API key is issued and stored, and CLI: Project Setup Wizard for the broader project setup flow this fits into.