API vs Epiphany

In-depth architectural comparison of the API and Epiphany 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.

Which MCP Server Should You Choose?

Choose API 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 API Details

E

Choose Epiphany 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 Epiphany Details

Feature & Specification Comparison

Specification	API Foundry Knowledge & Memory	E Epiphany Knowledge & Memory
Summary	Bounded tools for rendering, extraction, RAG, enrichment, local discovery and review analysis.	One private, local memory your AI tools share. Cross-model, on-device, never lose a session.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

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

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

{
  "mcpServers": {
    "epiphany": {
      "url": "https://modelcontextprotocol.io"
    }
  }
}

Related MCP Server Comparisons