Docs

Connect your AI client to Conducktor

Your workspace, in whichever AI app you use. Connect it once, and every connector, API, tool, file and Assistant you set up in Conducktor is there.

What you are connecting

Conducktor is the AI environment you own. Your connectors, the APIs you wire in, the tools you built with Claude, your files and the Assistants you created live in one workspace under your account. Any MCP client plugs into that workspace through one address. Switch apps or models and it is all still there.

Your connection URL

https://mcp.conducktor.com/mcp

Paste this where your AI client asks for an MCP server URL, then sign in with your Conducktor account. No key to generate, nothing to host.

Set up your client

Claude

Claude on the web, Claude Desktop and Cowork share one list of connectors.

  1. Open Customize → Connectors.
  2. Click + Add, then Add custom connector.
  3. Name it Conducktor and paste https://mcp.conducktor.com/mcp. Click Continue.
  4. Under OAuth client choose Register automatically. Under Authentication choose Sign in now. Click Add.
  5. Sign in with your Conducktor account and approve the connection.

On a Team plan only an Owner can add a connector, under Organization settings → Connectors; on Enterprise, an Owner or a role with Manage access to Libraries. Free accounts get one custom connector. The claude_desktop_config.json file is for local servers only; a remote server is added here, not there.

Claude Code

Add the server from the terminal, then sign in.

claude mcp add --transport http conducktor https://mcp.conducktor.com/mcp

Then run /mcp inside Claude Code and follow the sign-in link.

ChatGPT

ChatGPT adds remote MCP servers in Developer mode.

  1. Open Settings → Security and login and turn on Developer mode (in a workspace: Settings → Apps → Advanced settings).
  2. Open the Plugins page (Apps & Connectors in a workspace) and click +.
  3. Name it Conducktor, paste https://mcp.conducktor.com/mcp, choose OAuth, and save.
  4. Sign in with your Conducktor account when ChatGPT asks.
Cursor

Cursor reads MCP servers from a JSON file.

File: .cursor/mcp.json (this project) or ~/.cursor/mcp.json (everywhere)

{
  "mcpServers": {
    "conducktor": {
      "url": "https://mcp.conducktor.com/mcp"
    }
  }
}

Cursor opens the sign-in page the first time it connects.

VS Code / GitHub Copilot

VS Code reads MCP servers from mcp.json.

File: .vscode/mcp.json

{
  "servers": {
    "conducktor": {
      "type": "http",
      "url": "https://mcp.conducktor.com/mcp"
    }
  }
}

Or run MCP: Add Server from the Command Palette and paste the URL.

Any other MCP client

Any client that supports remote MCP servers over HTTPS with OAuth works the same way.

  1. Paste https://mcp.conducktor.com/mcp where the client asks for an MCP server URL.
  2. Choose OAuth (or 'sign in') when asked how to authenticate; the client registers itself with Conducktor.
  3. Sign in with your Conducktor account and approve the connection.
Test the connection

The official MCP Inspector opens a local page where you can call the server by hand.

npx @modelcontextprotocol/inspector

Then connect to https://mcp.conducktor.com/mcp.

What your client can do

Your client sees one tool, ask_conducktor. You say what you want in plain words; Conducktor runs it with the connectors, tools and Assistants in your workspace and returns the result. Reads run straight away. Whether a write needs your confirmation is the Assistant's autonomy level in Conducktor: Auto asks nothing; Supervised asks before a delete, a send outside your workspace or a spend. A confirmation cannot be given from an external client: Conducktor tells your client it has to come from you (a no from your client cancels the action), and nothing runs. Do the action in Conducktor itself. Today a Supervised Assistant holds every write it is asked for from an external client.

How sign-in works

OAuth authorization code with PKCE (S256 recommended; required for public clients). Your client registers itself with Conducktor; no shared secret is pasted anywhere.

You approve the connection on a Conducktor page, signed in as yourself. The token your client receives is tied to your account.

Conducktor issues the scopes mcp:tools, mcp:read and mcp:write. You can see every connected client, and disconnect one, on your Account page.

Data and privacy

Conducktor reaches the services you connected, the files you put in your workspace, and public web pages when you ask it to. Conducktor calls connected services with credentials held in its vault; your AI client receives the result of what you asked. Nothing is shared with other Conducktor users unless you bridge a connection to another workspace or share a link.

For administrators

  • Endpoint: https://mcp.conducktor.com/mcp, HTTPS only.
  • Authentication: OAuth authorization code with dynamic client registration; PKCE required for public clients (S256 recommended).
  • Each person signs in as themselves; a client is connected to one account and works inside that person's workspace.
  • A person can disconnect any client from their Account page at any time.

Need help

Email support@conducktor.com or visit .

Signed in already? Your URL and these steps are also on your Account page under AI Clients.

No workspace yet?