Configure MCP

@configure-ai/mcp is the local stdio MCP adapter for Configure profile tools. It supports two explicit modes:

• For myself: use your Configure profile and connected tools in Claude, Codex, Cursor, etc. No developer API key required.
• For my app or agent: connect MCP to a developer-owned agent using an API key after Launch Preview approval.

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

The backend still owns auth, permissions, metering, and write namespaces.

Recommended entry point:

npx configure setup

Choose For myself for personal MCP. Choose For my users for developer MCP or SDK setup.

Run

npx configure setup

The setup wizard asks:

What are you setting up?

1. For myself
   Use my Configure profile and connected tools in Claude, Codex, Cursor, etc.

2. For my users
   Connect MCP to a developer-owned agent using an API key.

Skip the prompt when you already know:

npx configure setup --myself --client codex
npx configure setup --users

Personal MCP requires explicit client attribution. For Codex, writes land under /agents/codex/; for Claude, use --client claude; for Cursor, use --client cursor.

If you run personal setup without --client, the wizard asks for the client in your terminal before opening the browser. In non-interactive shells, rerun with --client.

Direct package path:

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

For Codex, setup writes the MCP server to ~/.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.

The Codex config entry looks like:

[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 profile-specific command to that client's MCP config.

For hosted MCP clients that accept a remote URL, use:

https://mcp.configure.dev

The hosted URL is the personal MCP endpoint. Tool calls require a personal MCP bearer token from the personal login flow; clients that cannot attach a token should use the local npx setup.

Developer profile example:

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

List profiles:

configure-mcp profiles list

Credentials

Personal MCP stores a hashed-refresh-token-backed local profile. It does not store an sk_ key and does not accept CONFIGURE_AGENT or CONFIGURE_USER_ID.

Developer MCP uses:

• Agent credentials: a saved dev:<agent> MCP profile, or CONFIGURE_API_KEY with an explicit serve --profile dev:<agent> command.
• User subject: CONFIGURE_USER_TOKEN or CONFIGURE_USER_ID.

CONFIGURE_USER_TOKEN is an agent-scoped linked/federated user token. It can read portable cross-agent profile context subject to the user's permissions.

CONFIGURE_USER_ID is a developer-scoped app-local user ID. It does not require phone OTP and does not federate the user across developers.

Advanced env-only developer startup is explicit via a developer profile name:

CONFIGURE_API_KEY=sk_... \
CONFIGURE_USER_TOKEN=eyJ... \
npx -y @configure-ai/mcp serve --profile dev:atlas

If multiple local profiles exist, bare configure-mcp serve fails closed and asks you to choose one.

Tools

With a user subject, package MCP exposes:

• configure_profile_read
• configure_profile_search
• configure_profile_remember
• configure_profile_commit
• read-only connector tools for linked users: Gmail, Calendar, Drive, and Notion
• action tools for linked users: send email and create calendar event

configure_profile_read accepts the same SDK sections, including imports for user-directed ChatGPT/Claude/etc. imported memories. Use configure_profile_search with source: "chatgpt" or source: "import:chatgpt" to list one imported source.

configure_profile_commit accepts memories plus optional bounded messages and toolResults. Use it after a read/search-backed turn to submit durable user memory candidates. Do not use it for raw transcript dumps or bulk import.

The TypeScript SDK's default profile.tools() omits commit because the host application can call profile.commit() after the model turn. Package MCP includes commit because generic MCP clients usually expose only tool calls.

Connector read tools are enabled by default for linked/federated users and hidden for developer-scoped X-User-Id subjects. To narrow the connector list:

CONFIGURE_CONNECTORS=gmail,calendar npx -y @configure-ai/mcp serve --profile personal:codex

Action tools are enabled by default for linked/federated users and hidden for developer-scoped X-User-Id subjects. To narrow or disable the action list:

CONFIGURE_ACTIONS=email.send npx -y @configure-ai/mcp serve --profile personal:codex
CONFIGURE_ACTIONS= npx -y @configure-ai/mcp serve --profile personal:codex

Unknown connector or action names fail at startup.

Boundaries

Model-visible MCP tools do not accept phone numbers, OTP codes, bearer tokens, API keys, user IDs, agent handles, raw CFS paths, or namespace selectors.

Bulk import/backfill uses configure.importProfiles() from server-side code with an sk_ key. It is not exposed through MCP.