Configure MCP Adapter

Configure MCP lets MCP-compatible agents use Configure profile context, connected tools, and attributed memories without a direct SDK integration.

Developer MCP requires Launch Preview approval. Personal MCP signs into your own Configure profile and does not require a developer API key.

Use it when the agent runtime already speaks MCP, or when you need to connect Configure to a client you do not control. For products you own end to end, the Configure SDK is still the primary integration path.

Pick The Right Path

Use case	Choose	What acts as the agent
You want Codex, Claude, Cursor, or another local MCP client to use your own Configure profile	Personal MCP	The selected client, such as /agents/codex/
You are building an MCP-compatible app or hosted agent for your users	Developer MCP	A developer-owned Configure agent backed by an API key
A hosted client asks for an MCP server URL instead of a local command	Hosted MCP URL	A personal MCP installation with a bearer token
You own the product surface, auth flow, and model loop	Configure SDK	Your server-side Configure agent

Personal MCP

Use personal MCP when you are the end user connecting Configure to your own agent client.

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

The login flow signs you in to Configure and creates a local MCP profile for that client. Writes from that client stay attributed to its namespace, for example /agents/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.

[mcp_servers.configure-codex]
command = "npx"
args = ["-y", "@configure-ai/mcp", "serve", "--profile", "personal:codex"]
startup_timeout_sec = 20

For Claude Desktop, Cursor, or another MCP client, add the generated command to that client's MCP config.

Personal MCP does not require a developer API key.

Developer MCP

Use developer MCP when Configure is acting as an adapter for an MCP-compatible agent that you own.

npx configure setup

Choose For my users. Developer setup signs you in as a developer, asks which Configure agent MCP should act as, and creates a local MCP profile for that agent after preview approval. The generated config uses an API key for the selected agent.

Example MCP client config:

{
  "mcpServers": {
    "configure-atlas-dev": {
      "command": "npx",
      "args": ["-y", "@configure-ai/mcp", "serve", "--profile", "dev:atlas"]
    }
  }
}

Developer MCP still needs a user subject at runtime:

• Use CONFIGURE_USER_TOKEN for a linked Configure user.
• Use CONFIGURE_USER_ID for a developer-scoped app-local user.

Linked users can read portable profile context subject to their Configure permissions. App-local users are scoped to your developer account.

Hosted MCP URL

Some hosted clients ask for an MCP server URL instead of an npx command. Use:

https://mcp.configure.dev

This URL is the personal MCP endpoint. Tools require a bearer token from a personal MCP installation, so clients that cannot attach a token should use the local npx setup instead. Developer MCP remains gated behind Launch Preview approval.

How It Maps To The SDK

MCP is an adapter over the same Configure profile contract that the TypeScript SDK exposes.

SDK concept	MCP equivalent
configure.profile({ token })	Linked user token in the MCP profile
configure.profile({ externalId })	Developer-scoped CONFIGURE_USER_ID
profile.tools()	MCP tools/list
profile.executeTool()	MCP tools/call
profile.commit()	configure_profile_commit adapter tool

The SDK is better when your server owns the model loop, auth flow, and commit timing. MCP is better when the host already expects tools through the MCP protocol.

Tools

Configure MCP exposes the canonical Configure tools:

• configure_profile_read
• configure_profile_search
• configure_profile_remember
• configure_profile_commit

For linked users, connector tools can expose approved Gmail, Calendar, Drive, and Notion access. Action tools can send email or create calendar events when enabled for the runtime.

Connector and action tools are hidden for developer-scoped app-local users because those users are not linked to portable Configure accounts.

Boundaries

• Secret keys stay server-side. Do not paste sk_ keys into a browser or client-side app.
• API keys define the acting developer agent for writes.
• Personal MCP ignores developer environment variables.
• User input never chooses a storage namespace.
• MCP setup is separate from SDK installation; use the SDK when you are building Configure directly into your app.