What is the key difference between Contextforge MCP and Threadctx MCP?

Contextforge MCP belongs to the Knowledge & Memory category with local stdio execution, while Threadctx MCP belongs to the Knowledge & Memory category with local stdio execution.

How do I install Contextforge MCP or Threadctx MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Contextforge MCP and Threadctx MCP free or paid?

Contextforge MCP operates under a Freemium model (API Key required). Threadctx MCP operates under a Freemium model (API Key required).

Which MCP server has more tools and community activity?

Contextforge MCP lists 41 tools with 3 views and 2 GitHub stars. Threadctx MCP lists 2 tools with 2 views and 1 GitHub stars.

Can I use both Contextforge MCP and Threadctx MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Contextforge MCP vs Threadctx MCP

In-depth architectural comparison of the Contextforge MCP and Threadctx MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Contextforge MCP

Knowledge & Memory · Local stdio

Quality: 55/100 (Good) | Auth: API Key required

Threadctx MCP

Knowledge & Memory · Local stdio

Quality: 57/100 (Good) | Auth: API Key required

Verdict Summary: Choose Contextforge MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Threadctx MCP if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Contextforge MCP when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: CONTEXTFORGE_API_KEY.
Primary tools included: memory_ingest, memory_query, memory_list_items.

Explore Contextforge MCP Details

Choose Threadctx MCP when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: THREADCTX_API_KEY, THREADCTX_MODE, THREADCTX_NO_AUTO_RULES.
Primary tools included: .

Feature & Specification Comparison

Specification	Contextforge MCP alfredoizdev Knowledge & Memory	Threadctx MCP threadctx-dev Knowledge & Memory
Summary	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	Shared team memory for AI coding agents. Decisions, fixes, and gotchas persist per repo and are shared across Claude Code, Cursor, and any MCP client — what one teammate's agent learns, everyone's agents remember. Local-first, zero-dependency. npx -y threadctx-mcp
Category & Scope

Tools & Capabilities Breakdown

Contextforge MCP Tools (41)

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

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Contextforge MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Threadctx MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "threadctx-dev-threadctx-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "threadctx-mcp"
      ],
      "env": {
        "THREADCTX_API_KEY": "YOUR_THREADCTX_API_KEY_HERE",
        "THREADCTX_MODE": "YOUR_THREADCTX_MODE_HERE",
        "THREADCTX_NO_AUTO_RULES": "YOUR_THREADCTX_NO_AUTO_RULES_HERE"
      }
    }
  }
}

Frequently Asked Questions

Contextforge MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Threadctx MCP belongs to Knowledge & Memory using local stdio subprocess. Select Contextforge MCP when you need capabilities focused on knowledge & memory and Threadctx MCP when you require tools for knowledge & memory.

More alternatives to Contextforge MCP More alternatives to Threadctx MCP Knowledge & Memory category hub