What is the key difference between On Board and Repo Memory?

On Board belongs to the Knowledge & Memory category with cloud HTTP/SSE execution, while Repo Memory belongs to the Knowledge & Memory category with local stdio execution.

How do I install On Board or Repo Memory 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 On Board and Repo Memory free or paid?

On Board operates under a Free / Open Source model (No auth required). Repo Memory operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

On Board lists 0 tools with 0 views and 4 GitHub stars. Repo Memory lists 0 tools with 0 views and 1 GitHub stars.

Can I use both On Board and Repo Memory 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

On Board vs Repo Memory

In-depth architectural comparison of the On Board and Repo Memory 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

On Board

Knowledge & Memory · Remote HTTP/SSE

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

Repo Memory

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose On Board if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Repo Memory 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 On Board when:

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

Explore On Board Details

Choose Repo Memory 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 Repo Memory Details

Feature & Specification Comparison

Specification	O On Board Knowledge & Memory	Repo Memory Knowledge & Memory
Summary	Cross-platform shared memory and ticket coordination for AI agents across MCP clients.	Shared, git-tracked working memory for AI agents on the same codebase.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

On Board Tools (0)

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

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

On Board Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "on-board": {
      "url": "https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE"
    }
  }
}

Repo Memory Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "repo-memory": {
      "command": "uvx",
      "args": [
        "repo-memory-mcp"
      ]
    }
  }
}

Frequently Asked Questions

On Board is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Repo Memory belongs to Knowledge & Memory using local stdio subprocess. Select On Board when you need capabilities focused on knowledge & memory and Repo Memory when you require tools for knowledge & memory.

More alternatives to On Board More alternatives to Repo Memory Knowledge & Memory category hub