Contextforge MCP Server

Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot.

Local serverstdioGo

What is the Contextforge MCP server?

If you already use Contextforge, the contextforge mcp server is the piece that lets your assistant work with it directly. Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot.

What the server does

ContextForge MCP is an open-source MCP server that connects your AI coding assistants to long-term, searchable memory. Decisions, architecture notes, debugging context, and project knowledge stay available across every session — across every tool that supports MCP.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Cursor — The Cursor tool exposed by this server
  • Collaboration — The Collaboration tool exposed by this server
  • Utility — The Utility tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: CONTEXTFORGE_API_KEY, CONTEXTFORGE_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Installation goes through your MCP client rather than a global install: point it at contextforge-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Contextforge's toolset — Cursor, Collaboration, Utility — is a fair guide to whether it matches your workflow. It is maintained by alfredoizdev; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
CursorThe Cursor tool exposed by this server.
CollaborationThe Collaboration tool exposed by this server.
UtilityThe Utility tool exposed by this server.

How to install the Contextforge MCP server

{
  "mcpServers": {
    "contextforge": {
      "command": "npx",
      "args": ["-y", "contextforge-mcp"],
      "env": {
        "CONTEXTFORGE_API_KEY": "your-api-key-here"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
CONTEXTFORGE_API_KEYCredential the server authenticates with.Yes
CONTEXTFORGE_API_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Contextforge to Cursor.
  • Use Contextforge to Collaboration.
  • Use Contextforge to Utility.

Frequently asked questions

It connects Contextforge to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Cursor, Collaboration, Utility) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Contextforge directly.