Cconxt.docs
Guide · about 5 minutes

Get started with Conxt.

Conxt captures the decisions, preferences and context from your Claude, ChatGPT and Gemini chats, and hands them to every editor you connect. Five steps take you from no account to an IDE that already knows your project.

01
Create an account
02
Install the extension
03
Check it captures
04
Connect your IDE
05
Verify it works

Free for individuals: unlimited memories, auto-capture (1,000 captures a month), every IDE and agent, and JSON import and export. Nothing here needs a card. Compare plans

1

Create an account

Sign up with email, Google, or a magic link. Your memory lives in this account, not in any one AI tool, so it is the same vault whichever model or editor you use.

Create your account →
2

Install the Chrome extension

The extension is what captures memory. It works in the background on Claude, ChatGPT and Gemini, with no configuration per site.

  1. Add Conxt — AI Memory Layer from the Chrome Web Store.
  2. Pin it, then click its icon in the toolbar.
  3. Click Sign in to Conxt and sign in with the account from step 1.
Add to Chrome →
You're done whenthe extension popup shows your email and a row of counts for Memories, Decisions and Prefs, instead of the sign-in button.
3

Check that it captures

Have a normal working conversation in Claude, ChatGPT or Gemini: pick a library, settle a naming rule, describe your project. Conxt extracts structured memory from it (decisions, preferences, entities, coding rules and more), not the raw transcript.

Open your dashboard →
You're done whennew memories appear in your dashboard feed, and the extension popup's "This session" count goes above zero.

Already have context in another AI? You can bring it in with one prompt; see Import your context. (JSON import is included on the Free plan.)

4

Connect your IDE

Conxt is a remote MCP server. Every client below uses the same endpoint and the same API key.

Using Claude? Claude on the web, Claude Desktop and Claude Code can sign in to Conxt instead of using a key: add the endpoint below as a connector, click Connect, and approve it on conxt.dev. See the Claude guide.

  1. Go to conxt.dev/connect-ide and click Generate API Key. It starts with cnxt_. Copy it now and keep it somewhere safe.
  2. Open the setup for your editor below and paste the key where it says <your-api-key>.
MCP endpoint
https://mcp.conxt.dev/mcp/
Cursor~/.cursor/mcp.json
  1. Open ~/.cursor/mcp.json (create it if it doesn't exist).
  2. Add Conxt under mcpServers, then restart Cursor.
~/.cursor/mcp.json
{
  "mcpServers": {
    "conxt": {
      "type": "http",
      "url": "https://mcp.conxt.dev/mcp/",
      "headers": { "Authorization": "Bearer <your-api-key>" }
    }
  }
}
Claude Codeone terminal command
  1. Run this once in your terminal. Conxt is then available in every Claude Code session.
terminal
claude mcp add --transport http conxt https://mcp.conxt.dev/mcp/ --header "Authorization: Bearer <your-api-key>"
Codex~/.codex/config.toml
  1. Set your key as an environment variable, in the shell profile Codex starts from.
  2. Add the server to ~/.codex/config.toml (create the file if it doesn't exist).
  3. Start a Codex session and run /mcp: conxt should be listed as connected.
shell
export CONXT_API_KEY="<your-api-key>"
~/.codex/config.toml
[mcp_servers.conxt]
url = "https://mcp.conxt.dev/mcp/"
bearer_token_env_var = "CONXT_API_KEY"

The header must be [mcp_servers.conxt]. Codex silently ignores mcpServers. Using the desktop app? Follow the Codex guide.

Windsurf~/.codeium/windsurf/mcp_config.json
  1. Open ~/.codeium/windsurf/mcp_config.json.
  2. Add Conxt under mcpServers. Windsurf uses serverUrl, not url. Then restart Windsurf.
mcp_config.json
{
  "mcpServers": {
    "conxt": {
      "serverUrl": "https://mcp.conxt.dev/mcp/",
      "headers": { "Authorization": "Bearer <your-api-key>" }
    }
  }
}
Claude DesktopSettings → Developer
  1. Open Claude Desktop → Settings → Developer and click Edit Config to open claude_desktop_config.json.
  2. Add Conxt under mcpServers, including the headers object.
  3. Save, fully quit Claude Desktop, and reopen it. Conxt appears in the tools menu.
claude_desktop_config.json
{
  "mcpServers": {
    "conxt": {
      "url": "https://mcp.conxt.dev/mcp/",
      "headers": { "Authorization": "Bearer <your-api-key>" }
    }
  }
}

Using Hermes, Perplexity or another MCP client? Any client that supports Streamable HTTP works with the same URL and header; connect-ide has setup for each.

5

Verify it works

Open a new chat in your editor and ask something only your memory can answer:

ask your editor
Use Conxt: what do you already know about this project and my preferences?
You're done whenthe agent calls get_context and answers with decisions and preferences from your chats in step 3. In Claude Code, claude mcp list should show conxt as connected; in Codex, /mcp.

To make it a habit, tell your agent to open every task with get_context and close it with add_memory, so what it builds is remembered too. The MCP tools reference covers all twenty tools.

?

Troubleshooting

The client can't connect, or calls fail with 401

The Authorization header is missing or the key is wrong. Check it reads Bearer cnxt_… with your full key, then restart the client. Clients that support sign-in, such as Claude, open the Conxt sign-in page instead when there is no key.

Codex doesn't list conxt

Check the section header is [mcp_servers.conxt], and that CONXT_API_KEY is set in the environment Codex was started from. Open a new terminal after editing your shell profile.

No memories appear after chatting

Open the extension popup and confirm you are signed in. Then reload the Claude, ChatGPT or Gemini tab, since the extension attaches when the page loads. Short small-talk chats may not contain anything worth remembering.

"Free tier limit reached"

The Free plan allows 1,000 captures a month, with unlimited memories. The count resets each month; for unlimited auto-capture, see the Team plan.

Still stuck?

Email hello@conxt.dev with the client you're connecting and the error you see. Never include your API key.