What is the key difference between Moxie Docs MCP and Tela?

Moxie Docs MCP belongs to the Knowledge & Memory category with local stdio execution, while Tela belongs to the Knowledge & Memory category with local stdio execution.

How do I install Moxie Docs MCP or Tela 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 Moxie Docs MCP and Tela free or paid?

Moxie Docs MCP operates under a Freemium model (API Key required). Tela operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Moxie Docs MCP lists 12 tools with 19 views and 2 GitHub stars. Tela lists 6 tools with 3 views and 52 GitHub stars.

Can I use both Moxie Docs MCP and Tela 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

Moxie Docs MCP vs Tela

In-depth architectural comparison of the Moxie Docs MCP and Tela 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

Moxie Docs MCP

Knowledge & Memory · Local stdio

Quality: 80/100 (Excellent) | Auth: API Key required

Tela

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Moxie Docs MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Tela 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 Moxie Docs 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: MOXIE_TOKEN.
Primary tools included: moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.

Explore Moxie Docs MCP Details

Choose Tela when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: TELA_API_KEY_SECRET, TELA_SHARE_SECRET, TELA_PG_PASSWORD, TELA_PUBLIC_BASE_URL.
Primary tools included: Built-in MCP endpoint at /api/mcp, Ranked PostgreSQL full-text search, Optional pgvector semantic search.

Feature & Specification Comparison

Specification	Moxie Docs MCP FeaturedVerifiedKnowledge & Memory	Tela zcag Knowledge & Memory
Summary	MCP & Agent Skills for Automated Documentation, and codebase conventions + context	Self-hostable, markdown-native team wiki with a built-in MCP server: agents search, read, and write your wiki pages (ranked Postgres full-text + semantic search, backlink traversal). Plus Atlas, which auto-generates a cited, coverage-checked wiki from your git repos and Jira. Go + Postgres. npx tela-mcp

Tools & Capabilities Breakdown

Moxie Docs MCP Tools (12)

moxie.get_ai_context

Compact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.

moxie.get_doc_impact

Given the paths you're about to change (and any you're deleting), returns the conventions, gaps, and existing docs whose evidence overlaps them - and flags net-new/undocumented surfaces.

moxie.get_api_context

Given paths you're about to touch, returns structured context for any API endpoints they map to: method, path, schema, and known consumers/features.

moxie.review_change

Self-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docs, undocumented surface, and broken references.

moxie.get_conventions

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

Moxie Docs MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "moxie-docs-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "moxie-docs"
      ],
      "env": {
        "MOXIE_TOKEN": "YOUR_MOXIE_TOKEN_HERE"
      }
    }
  }
}

Tela Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "zcag-tela": {
      "command": "npx",
      "args": [
        "-y",
        "tela-mcp"
      ],
      "env": {
        "TELA_API_KEY_SECRET": "YOUR_TELA_API_KEY_SECRET_HERE",
        "TELA_SHARE_SECRET": "YOUR_TELA_SHARE_SECRET_HERE",
        "TELA_PG_PASSWORD": "YOUR_TELA_PG_PASSWORD_HERE",
        "TELA_PUBLIC_BASE_URL": "YOUR_TELA_PUBLIC_BASE_URL_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Moxie Docs MCP More alternatives to Tela Knowledge & Memory category hub