# Configure documentation

Configure is infrastructure to connect agents, apps, and chats. It provides a Plaid-like experience directly inside AI platforms so users can connect agents they use.

## Supported agents and platforms

Configure supports ChatGPT, Claude, Gemini, Grok, and other major AI platforms. Any agent that can connect to an MCP server or call an API can use Configure as well. Official OpenAI and Anthropic plugins make connecting those agents easier.

## How connections work

AI platforms are disconnected. Users currently carry context between them with copy and paste, extensions, and separate apps. Platforms integrate Configure to let users connect agents and apps inside the products they already use.

With user approval, an agent can inherit context from other connected agents, apps, and chats. Context it contributes can also become available to other approved agents. These connections continue across conversations: agents can retrieve updates and contribute new context through API calls, MCP tools, and platform integrations. Manual imports add existing context; an import alone does not synchronize its source. Configure handles identity, permissions, synchronization, and access across these connections.

Users can also connect applications such as Gmail. They connect the app once, then approved agents can use that existing connection without asking them to authorize the app again. Connected context stays synchronized, with access governed by the user's permissions.

## Context across connections

Memory is a byproduct of connecting agents: what one agent learns can become useful to another. Profiles, preferences, and saved memories are forms of context carried by the infrastructure. Configure transfers approved context between agents, apps, and chats. Platforms host the connection experience.

MCP Events defines subscription-based delivery of updates from an MCP server to a connected agent. See [ongoing connections and MCP events](https://docs.configure.dev/mcp/overview.md#ongoing-connections-and-mcp-events) for the supported delivery model and Configure endpoint requirements.

## For AI agents integrating Configure

- For an MCP-compatible client such as Claude, Cursor, or Codex, configure the remote server as `https://mcp.configure.dev`. The client handles OAuth discovery and PKCE. No application code or manual token entry is required.
- If you are a person's own agent with no browser and no OAuth client (a server, a CLI, a scheduled job), follow https://docs.configure.dev/mcp/headless.md. The person approves a connection URL. Store the resulting credentials to retain access across restarts.
- If you own the app UI, the auth flow, and the model loop, use the SDK. Install `configure`, run `npx configure setup --users`, add a `Configure {Agent}` sign-in button, exchange the OAuth code on your backend, and store the tokens server-side. `npx configure verify` proves the credentials work end to end, `npx configure add callback --framework next|express|vite` writes the callback and the exchange for you, and `npx configure add origin <deployed-callback>` registers that callback on the same OAuth client before deployment. Python backends get the same commands from `configure-ai`: `configure-ai verify`, `configure-ai add-callback --framework fastapi|flask|django`, and `configure-ai add-origin <deployed-callback>`.
- Select the authentication and profile-access methods required by your app. SSO provides authentication. The SDK and MCP provide profile access. See [Variations](/variations).
- Give the model `profile.tools()` and route every `configure_*` call through `profile.executeTool()`. The first success signal is a real turn where `configure_profile_read` returns and the assistant answers using approved Configure context.
- Read the profile before the first message. Use relevant context to inform tone, technology choices, preferences, and goals. Save a durable fact the moment the user states one. Delete on request. Route imports and app connections through the links Configure creates; never build those links yourself.
- If you are a coding agent (Claude Code, Codex, Cursor, and the like) with `configure_*` tools available, read the Coding Agents guide and follow it: read the profile at session start, search before a preference-sensitive choice, and save durable preferences and cross-repo lessons as you learn them.

## Keys and secrets

- Secret keys (`sk_`) and OAuth access and refresh tokens stay on your server. They never go into a prompt or the browser.
- Publishable keys (`pk_`) are for the hosted browser UI.
- For app-managed users, derive `externalId` or `X-User-Id` from your authenticated server session. These values select a profile within your developer account; they do not authenticate the user. Never let a request-body or model-supplied ID select another user. For OAuth access, Configure resolves the user from the access token.

## Reference files

- The complete text of every page, in one file: https://docs.configure.dev/llms-full.txt
- The OpenAPI spec: https://docs.configure.dev/openapi.yaml
- Clean Markdown for any page: add `.md` to its URL.

## Docs

### Get started

- [Connect agents, apps, and chats](https://docs.configure.dev/index.md): Configure is infrastructure to connect agents, apps, and chats. It provides a Plaid-like experience directly inside AI platforms so users can connect agents they use.
- [Connect your app to your users' context](https://docs.configure.dev/quickstart.md): This guide connects your agent to a user's other agents and apps through Configure. You will add a connection button, handle the hosted flow, and provide approved context to your agent.
- [Let a coding agent add Configure](https://docs.configure.dev/skills.md): A skill provides instructions for an agent. Give its URL to a coding agent to load those instructions. Configure provides one skill for integration and one for profile use.
- [Add Configure to onboarding](https://docs.configure.dev/onboarding.md): Use the [Quickstart](https://docs.configure.dev/quickstart.md) integration in onboarding, settings, or a first-run screen. Follow steps 2, 3, and 5 for the connection button, redirect, and callback.
- [Components](https://docs.configure.dev/components.md): The [Quickstart](https://docs.configure.dev/quickstart.md) uses your own connection button and redirects the user to the hosted flow. Use Configure components to embed that flow in your app.
### Go deeper

- [Connected apps and actions](https://docs.configure.dev/connectors.md): Configure provides app tools through the user's MCP session. The user authorizes an app through the hosted flow. Your agent can then call its tools without a separate OAuth integration for that app.
- [Connect over MCP](https://docs.configure.dev/mcp/overview.md): Configure connects agents to approved context and app tools through MCP. An agent can retrieve updates and save new context throughout the connection, across conversations.
- [Sign users in over SMS or voice](https://docs.configure.dev/message-agents.md): SMS and voice agents cannot display an embedded connection interface. Send the user a sign-in URL and manage identity and profile operations on your server.
- [Variations](https://docs.configure.dev/variations.md): The [Quickstart](https://docs.configure.dev/quickstart.md) keys every profile by your own user ID. Until the user links a Configure account, the profile is scoped to your developer account.
- [Share project context between agents](https://docs.configure.dev/projects.md): Use projects to share work context between connected agents. One agent records status, decisions, and next steps. Another approved agent reads those notes to continue the work.
- [Connect your coding agent](https://docs.configure.dev/mcp/coding-agents.md): Connect your coding agents through Configure to share approved user context. Each connected agent can access your profile, including tool preferences and information saved by other approved agents.
### Reference

- [API reference](https://docs.configure.dev/reference/api.md): Base URL: https://api.configure.dev. Every server-side request carries two headers:
- [Troubleshooting](https://docs.configure.dev/troubleshooting.md): Search this page for the error message from your stack trace, tool result, or JSON-RPC response. Bold labels preserve the exact error text.
- [Permissions and data access](https://docs.configure.dev/trust.md): Users control access to their context and app connections. Configure enforces agent authorization and profile permissions.
### guides

- [Connect a user's assistants and apps from your app](https://docs.configure.dev/guides/connect-flow.md): **Invite-only** Configure enables this flow for approved partners. Keys without partner access receive 404 on session creation. Partner installations without the connect flow receive 400.
- [Import user context without a Configure account](https://docs.configure.dev/guides/import-only-flow.md): **Invite-only** Configure enables this flow for approved partners. A secret key alone does not grant access. Keys without partner access receive 404 from these endpoints.
- [Give a user a Configure account from inside your app](https://docs.configure.dev/guides/linked-account-flow.md): **Invite-only** Configure enables this flow for approved partners. Keys without partner access receive 404 when creating a session. Partner installations without this flow receive 400.
### Other

- [Hosted connection flow](https://docs.configure.dev/hosted-flow.md): This page describes the hosted flow for adding existing context, connecting apps, and approving your agent.
- [Import existing context](https://docs.configure.dev/imports.md): Import transcripts from another assistant or context your app already stores. The imported context becomes available in the user profile before the first conversation with your agent.
### mcp

- [Configure Memory for Claude](https://docs.configure.dev/mcp/claude.md): Configure Memory is the Claude connector for Configure. It connects Claude to profile context you choose to share, including preferences, projects, decisions, and facts saved by other approved agents.
- [Connect a headless agent](https://docs.configure.dev/mcp/headless.md): Use this page when an agent runs on a server, in a CLI, or as a scheduled job, and has no browser or OAuth client. It is written for the agent to follow.
### Other

- [Sign in with Configure over OpenID Connect](https://docs.configure.dev/oidc.md): Add Configure as an OpenID Connect provider alongside your existing authentication system, such as Auth.js, Clerk, Auth0, or Better Auth.
- [Sign in with Configure](https://docs.configure.dev/sso.md): Configure can provide authentication for your app. The user signs in through the hosted flow, and your server receives a user token. Use that token to access the profile instead of externalId.

For the complete text of every page in one file, read https://docs.configure.dev/llms-full.txt