# alfredoizdev/contextforge-mcp [Health: Active]

**Category:** 🧠 Knowledge & Memory  
**Repository:** https://github.com/alfredoizdev/contextforge-mcp  
**GitHub Stars:** 2  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/alfredoizdev-contextforge-mcp

## Description
Persistent memory for Claude Code, Cursor, and GitHub Copilot via MCP. Semantic search, Git commit/PR sync, project-based organization, team collaboration. Free tier available. npx contextforge-mcp

## Tools
Capabilities this server exposes over MCP:

- **memory_ingest** — Save knowledge to memory
- **memory_query** — Search your knowledge semantically
- **memory_list_items** — List all stored items
- **memory_delete** — Remove specific items
- **memory_ingest_batch** — Save multiple items at once
- **memory_delete_batch** — Delete items by filter
- **memory_list_spaces** — List your spaces
- **memory_create_space** — Create a new space
- **memory_delete_space** — Delete a space
- **memory_move_space** — Move space to project
- **memory_list_projects** — List your projects
- **memory_create_project** — Create a new project
- **memory_delete_project** — Delete a project
- **memory_link_project** — Link directory to project
- **memory_unlink_project** — Unlink directory
- **memory_current_project** — Show linked project
- **memory_git_connect** — Connect a GitHub repo
- **memory_git_list** — List connected repos
- **memory_git_activate** — Activate/deactivate webhook
- **memory_git_sync** — Import existing history
- **memory_git_commits** — List synced commits
- **memory_git_prs** — List synced PRs
- **memory_git_disconnect** — Disconnect a repo
- **issues_list** — List your issues
- **issues_create** — Create a new issue
- **issues_start** — Mark as in progress
- **issues_resolve** — Mark as resolved
- **issues_resolve_by_name** — Resolve by title
- **issues_assign** — Assign to collaborator
- **issues_what_next** — Get recommendation
- **project_share** — Share project by email
- **collaborators_list** — List collaborators
- **memory_snapshot_create** — Create a backup
- **memory_snapshot_list** — List all snapshots
- **memory_snapshot_restore** — Restore from backup
- **memory_snapshot_delete** — Delete a snapshot
- **memory_export** — Export to JSON/MD/CSV
- **memory_import** — Import from file
- **memory_stats** — View usage statistics
- **memory_relate** — Link two items
- **memory_help** — Show help

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "contextforge-mcp": {
    "command": "npx",
    "args": ["-y","contextforge-mcp"],
    "env": {
      "CONTEXTFORGE_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `CONTEXTFORGE_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What alfredoizdev/contextforge-mcp MCP server does

The alfredoizdev/contextforge-mcp MCP server connects MCP-compatible coding assistants to long-term project memory. Agents can save decisions, architecture notes, debugging details, and other knowledge, then retrieve related information with semantic search rather than relying only on exact keywords. Stored items can be listed, deleted individually, or processed in batches.

Memory is organized through spaces and projects. The available project operations can create or remove projects, associate a local directory with a project, show the active project, and move spaces between projects. This structure is useful when one developer or team works across multiple repositories or separate areas of knowledge.

The server also includes GitHub repository operations. An agent can connect and disconnect repositories, list connected repositories, enable or disable webhook activity, import existing history, and inspect synchronized commits and pull requests. Issue tools support listing and creating issues, starting work, resolving issues by identifier or title, assigning collaborators, and asking what to work on next.

## How it works

The server runs locally as an MCP process while using the ContextForge service for the account and stored data. Clients start it with Node.js through `npx`, and authentication is supplied with the `CONTEXTFORGE_API_KEY` environment variable. A free tier is available, but an API key must be generated from the ContextForge website.

From version 0.5.1 onward, the server sends startup instructions when a client supports them. Claude Desktop and Claude Code can therefore load project memory at session start and save relevant decisions without additional editor rules. Clients that do not honor those instructions can use the `init` command to add explicit memory, session-presence, and startup-context rules to `CLAUDE.md` or `.cursorrules`.

The README describes a lean default tool exposure to reduce context usage, with a full mode available through `CONTEXTFORGE_TOOLS=full`. The supplied tool set covers memory, spaces, projects, GitHub synchronization, and issue tracking.

## Setup and configuration

Install-on-demand configuration uses `npx -y contextforge-mcp` as the MCP command. Configure the command and `CONTEXTFORGE_API_KEY` in the client’s MCP settings, then restart the client. The documented clients include Claude Desktop, Claude Code, Cursor, and GitHub Copilot; the project description also names Windsurf as supported.

Generate the API key at `contextforge.dev` under Settings and API Keys. The key starts with `cf_` according to the setup instructions. Node.js 20 or newer is required. A global npm installation is optional, while `npx` fetches the package when the client launches it.

Running `npx contextforge-mcp init` is recommended when explicit project instructions are useful. It detects Claude or Cursor project markers, or can target an editor with `--editor=claude`, `--editor=cursor`, or `--editor=all`. Re-running the command preserves existing sections and adds missing ones.

## Limitations and notes

The server depends on the external ContextForge service and an account API key; it is not a standalone local memory database. Automatic startup behavior varies by client, so editor rule generation may still be needed for clients that do not process server instructions. Git synchronization requires connecting a GitHub repository before history, commit, pull-request, or webhook operations can provide repository data.

The project is open source under the MIT license. Its package requires Node.js 20 or newer, and its free tier is available without a credit card according to the README.

_Full upstream README: https://allmcps.com/mcp/alfredoizdev-contextforge-mcp/readme_