What is the key difference between Locus and Myplan?

Locus belongs to the Knowledge & Memory category with local stdio execution, while Myplan belongs to the Knowledge & Memory category with local stdio execution.

How do I install Locus or Myplan 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 Locus and Myplan free or paid?

Locus operates under a Free / Open Source model (No auth required). Myplan operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Locus lists 0 tools with 2 views and 0 GitHub stars. Myplan lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Locus and Myplan 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

Locus vs Myplan

In-depth architectural comparison of the Locus and Myplan 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

Locus

Knowledge & Memory · Local stdio

Quality: 40/100 (Fair) | Auth: No auth required

Myplan

Knowledge & Memory · Local stdio

Quality: 25/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Locus if you need specialized Knowledge & Memory tools running via a local process. Choose Myplan 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 Locus when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Locus Details

Choose Myplan when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Myplan Details

Feature & Specification Comparison

Specification	Locus Knowledge & Memory	M Myplan Knowledge & Memory
Summary	Hierarchical markdown memory palace for AI agents — structured palace navigation via MCP tools.	Shared Markdown notes and canvases that people and AI agents edit together; agents suggest edits.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

Locus Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Myplan Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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).

Locus Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "locus-2": {
      "command": "uvx",
      "args": [
        "locus-mcp"
      ]
    }
  }
}

Myplan Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "myplan": {
      "command": "npx",
      "args": [
        "-y",
        "myplan"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Locus More alternatives to Myplan Knowledge & Memory category hub