Configure MCP
Your profile and tools, available to any MCP-compatible agent.
Connect Configure once, then use your memory profile, preferences, connected apps, and agent-specific memories from Codex, Claude, Cursor, or a remote MCP client.
Local MCP for Codex
Authenticates you and saves a local profile.
npx -y @configure-ai/mcp login --personal --client codex
Remote MCP URL
Paste into clients that support remote MCP with OAuth.
https://mcp.configure.dev
Developer adapter
Use when MCP should act as your app's agent.
npx -y @configure-ai/mcp login --developer
Choose The Right Mode
Explicit before login
For myself
No API key
Use your Configure profile in MCP clients. Writes are attributed to the client you choose, like /agents/codex/, and connected tools are available from your profile.
For my app or agent
Developer-owned
Connect MCP to an agent you own with an API key. Writes stay in that agent namespace, and app-local users stay scoped to your developer account.
What Happens
The personal flow
1
Pick a client
Choose Codex, Claude, Cursor, or another MCP client slug before browser auth starts.
2
Verify yourself
Configure links the MCP install to your phone-verified profile. No developer secret key is stored.
3
Use your tools
The agent can read approved profile context and connected tools like Gmail, Calendar, Drive, and Notion.
4
Keep attribution
Memories written from Codex stay under
/agents/codex/, while shared profile data remains user-owned.
Tools Included
Scoped by your connections
Profile memory
Read, search, remember, and commit profile context through Configure MCP tools.
Connected apps
Search email, calendar, files, and notes when you have connected those tools.
Actions
Send email and create calendar events when the install is scoped for actions.
Permissions
Cross-agent reads use your Configure permissions and fail closed when access is not approved.
Building Configure into your own app?
Use the SDK setup flow for product integration. MCP login is for connecting MCP-compatible agents.
Read Docs