Configure MCP

Bring context anywhere with Configure MCP.

Configure MCP allows you to take your context to any MCP compatible agent. For developers, it is an optional alternative adapter to the Configure SDK.

Developer MCP requires Launch Preview approval. Personal MCP does not require a developer API key.

Choose A Setup

For Myself

Use this when you want Codex, Claude, Cursor, or another MCP client to access your own Configure profile. No developer API key is required.

npx configure setup

Choose For myself, then choose Codex, Claude, Cursor, or another client slug. The wizard delegates to personal MCP and signs you into your own Configure profile.

Direct path:

npx -y @configure-ai/mcp login --personal --client codex

For Codex, setup updates ~/.codex/config.toml, which is shared by the Codex desktop app, IDE extension, and CLI. Restart the surface you use so it reloads config. App and extension users should start a new chat after restart; CLI users can run /mcp to confirm Configure is connected. Writes are attributed to the selected client, for example /agents/codex/.

For My App Or Agent

Use this when you are building an MCP-compatible agent for other people.

npx configure setup

Choose For my users. Developer setup signs you in as a developer, asks which Configure agent MCP should act as, and connects that agent with an API key after preview approval.

Remote MCP URL

Use this when a client asks for a hosted MCP server instead of an npx command.

https://mcp.configure.dev

This is the personal MCP endpoint. Tool calls require a personal MCP bearer token from personal setup. Developer MCP requires For my users setup and Launch Preview approval.

MCP Or SDK

MCP connects an AI client. The TypeScript SDK is for building Configure directly into your app after choosing For my users in setup.

Use the SDK when you own the product surface, auth flow, and model loop. Use MCP when the host already expects tools through the MCP protocol.

Next: Configure as an MCP adapter.