ContextKit MCP / onlinecontext:write
Remote agent memory

Give every coding agent durable context tools.

Connect once, authenticate with OAuth, then let Claude, Codex, Cursor, or another MCP host summarize, compress, hand off, extract profile memory, estimate tokens, and inspect credits.

https://contextkit.pro/mcp

01

Add remote server

Choose Streamable HTTP, never STDIO.

02

Sign in with OAuth

ContextKit registers the client and uses PKCE.

03

Approve access

Tools now spend the same scoped account credits.

04

Auto-capture policy

After useful completed work, call consider; publish only after user approval.

01 / Claude app

Connect from Claude's Connector UI.

Use this when you are adding ContextKit from the Claude app settings, not by editing a local file.

Claude connector

Add it in four clicks.

  1. 1Open Claude Settings, then Connectors or Integrations.
  2. 2Choose Add custom MCP or Add connector.
  3. 3Select Streamable HTTP and paste the ContextKit server URL.
  4. 4Press Connect, sign in to ContextKit, then approve context:write.

Leave OAuth client ID empty unless your organization has its own registered client. ContextKit supports automatic registration for compatible connector UIs.

CLAUDE APP

Values to enter in Claude

Name: ContextKit
Transport: Streamable HTTP
Server URL: https://contextkit.pro/mcp
Authentication: OAuth / Connect

02 / Codex

Add from the Codex desktop app or terminal.

Use OAuth when your Codex install supports it. The bearer option is a safe fallback for a dedicated, scoped API key.

CODEX CLI

OAuth connection

codex mcp add contextkit \
  --url https://contextkit.pro/mcp

codex mcp list

CODEX CLI

Bearer fallback

export CONTEXTKIT_MCP_KEY="ck_live_your_scoped_key"

codex mcp add contextkit \
  --url https://contextkit.pro/mcp \
  --bearer-token-env-var CONTEXTKIT_MCP_KEY

Codex desktop app

Open Settings, choose Add custom MCP, select Streamable HTTP, and enter https://contextkit.pro/mcp. Choose Connect to finish OAuth in the browser. If the UI only supports a key, use the bearer fallback with a dedicated context:write key.

03 / Cursor + JSON IDEs

Use OAuth JSON first. Add a bearer header only when OAuth is unavailable.

Cursor and other JSON-configured MCP hosts usually accept a remote URL configuration. The exact file location can vary by host, but the server entry is the same.

OAUTH JSON

Cursor or OAuth-capable IDE

{
  "mcpServers": {
    "contextkit": {
      "url": "https://contextkit.pro/mcp"
    }
  }
}

BEARER JSON

JSON host without OAuth

{
  "mcpServers": {
    "contextkit": {
      "url": "https://contextkit.pro/mcp",
      "headers": {
        "Authorization": "Bearer ${CONTEXTKIT_MCP_KEY}"
      }
    }
  }
}

Use a dedicated key

Create a key with only context:write for a single IDE integration.

Never commit secrets

Store CONTEXTKIT_MCP_KEY in the IDE secret store or environment, not source control.

Prefer OAuth

OAuth avoids copying an API key into a config file and supports account consent.

04 / Tools

What your connected agent can call.

All tools use the authenticated account's ContextKit credits and the same request safeguards as direct API calls.

Auto-capture rule

Add this instruction to your agent: after every completed non-trivial task, call contextkit_experience_consider with the user request, actions, final result, and reusable lesson. If it returns shouldSave:true, ask the user before calling contextkit_experience_publish. Never publish publicly without explicit approval.

01contextkit_summarize
02contextkit_compress_context
03contextkit_handoff
04contextkit_extract_profile
05contextkit_experience_consider
06contextkit_experience_save
07contextkit_experience_publish
08contextkit_experience_search
09contextkit_experience_buy
10contextkit_estimate_tokens
11contextkit_get_credits

Need credits before the agent runs paid tools?

OAuth and bearer MCP tools spend the same ContextKit account credits as direct API requests.

Open Credits