Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.conductor.is/llms.txt

Use this file to discover all available pages before exploring further.

Conductor provides a hosted MCP server at https://conductor.stlmcp.com/, so you can connect supported AI tools directly to Conductor without running your own local MCP server. All setups below require a Conductor secret key.

​
Client setup

​
Claude Code

If you want to use Conductor from Claude Code, run: 
claude mcp add conductor \
  --env CONDUCTOR_SECRET_KEY="sk_conductor_..." \
  -- npx -y mcp-remote@latest https://conductor.stlmcp.com/ \
  --transport http-only \
  --header 'x-conductor-secret-key:${CONDUCTOR_SECRET_KEY}'
This uses Conductor’s hosted MCP server. mcp-remote just makes it look like a local stdio server to Claude Code.

​
Cursor

Cursor uses .cursor/mcp.json for project config and ~/.cursor/mcp.json for global config. Use this config:
.cursor/mcp.json
{
  "mcpServers": {
    "conductor": {
      "url": "https://conductor.stlmcp.com/",
      "headers": {
        "Authorization": "Bearer sk_conductor_..."
      }
    }
  }
}
Replace the placeholder sk_conductor_... value with your real Conductor secret key.

​
VS Code

Open the Command Palette and run MCP: Open User Configuration, then add: 
{
  "mcpServers": {
    "conductor": {
      "url": "https://conductor.stlmcp.com/",
      "headers": {
        "Authorization": "Bearer sk_conductor_..."
      }
    }
  }
}
Replace the placeholder sk_conductor_... value with your real Conductor secret key.

​
Claude Desktop

Claude Desktop can use the hosted server directly with:
claude_desktop_config.json
{
  "mcpServers": {
    "conductor": {
      "url": "https://conductor.stlmcp.com/",
      "headers": {
        "Authorization": "Bearer sk_conductor_..."
      }
    }
  }
}
Config file locations:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\\Claude\\claude_desktop_config.json
Your MCP client can read and write data using whatever Conductor secret key you provide. Treat that key like any other production credential.

​
Notes

  • The hosted MCP server uses the same auth model as the Conductor API. Standard header: Authorization: Bearer <your Conductor secret key>. Also supported: x-conductor-secret-key: <your Conductor secret key>.
  • Some web-based MCP clients still do not let you attach custom headers. If your client cannot send an Authorization or x-conductor-secret-key header, prefer one of the desktop setups above.

​
Self-hosting

If you intentionally want to run or customize the MCP server yourself, use the open-source conductor-node-mcp package and its README in the SDK repo: quickbooks-desktop-node/packages/mcp-server That keeps local installation, tool filtering, and self-hosting instructions in the package repo, while this guide stays focused on the recommended hosted setup.