contextcore-mcp

Give Cursor, Claude Code, and any other MCP-aware agent secure, read-only access to your ContextCore project context — vision, audience, scope, tech decisions, rules, skills, risks, and open questions.

The agent gets exactly the context you can see. Access is enforced server-side by ContextCore's org/team/visibility federation — this client holds no authorization logic and can never widen access.

Most people don't need this package. ContextCore's gateway speaks MCP over HTTP, so any editor that supports remote MCP servers can connect with a URL and a token — no install. Use this package only if your client is stdio-only.

What your agent gets

Tool	What it returns
list_projects	Projects you can access (id, name, tagline)
get_context_core	A project's full context as one Markdown document
read_component	One component (e.g. vision, scope, tech) as Markdown
search_context	Keyword matches across pieces, rules, skills, risks, and problems

The tool list is fetched from the server at startup rather than baked in here, so it stays current without you upgrading the package.

Setup

1. Generate a token

In ContextCore, open Account → Integrations → Generate token and copy it (shown once).

2. Connect

Remote (preferred). Works in Cursor and Claude Code without installing anything:

{
  "mcpServers": {
    "contextcore": {
      "url": "https://contextcore.md/mcp",
      "headers": { "Authorization": "Bearer ${env:CONTEXTCORE_TOKEN}" }
    }
  }
}

Stdio (this package). For clients that don't support remote servers:

{
  "mcpServers": {
    "contextcore": {
      "command": "npx",
      "args": ["-y", "contextcore-mcp"],
      "env": { "CONTEXTCORE_TOKEN": "YOUR_TOKEN" }
    }
  }
}

Cursor reads ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project); Claude Code reads .mcp.json in your project root, or:

claude mcp add contextcore --env CONTEXTCORE_TOKEN=YOUR_TOKEN -- npx -y contextcore-mcp

3. Use it

Ask your agent things like "Load the context for my Loop project" or "What's the target audience according to ContextCore?". It will call the tools automatically.

Configuration

Env var	Required	Default	Description
CONTEXTCORE_TOKEN	yes	—	Personal Access Token from ContextCore
CONTEXTCORE_API_URL	no	https://contextcore.md	ContextCore deployment base URL

The pre-rename CONTEXTOS_TOKEN and CONTEXTOS_API_URL are still accepted.

Security

• The token maps to a single ContextCore user. Every read runs through the same federation gates as the web app — restricted context you can't see is never returned.
• Only a SHA-256 hash of your token is stored server-side. Revoke any token anytime from Account → Integrations.
• Never commit your token. Reference it via an environment variable in your MCP config where possible.

License

MIT