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

LynxMCP belongs to the Developer Tools category with local stdio execution, while Moxie Docs MCP belongs to the Developer Tools category with local stdio execution.

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

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

Which MCP server has more tools and community activity?

LynxMCP lists 0 tools with 1 views and 8 GitHub stars. Moxie Docs MCP lists 12 tools with 17 views and 2 GitHub stars.

Can I use both LynxMCP and Moxie Docs 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.

How do I install LynxMCP or Moxie Docs MCP in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are LynxMCP and Moxie Docs MCP free to use, or do they require API keys?

LynxMCP is listed under a Free / Open Source model with No auth required . Moxie Docs MCP operates under a Freemium model with API Key required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both LynxMCP and Moxie Docs MCP at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both lorenzo-cambiaghi-lynxmcp and moxie-docs-mcp as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, LynxMCP has a Quality Score of 39 /100 ( Emerging ) with 1 views, 0 installs, and 8 GitHub stars. Moxie Docs MCP holds a Quality Score of 72 /100 ( Great ) with 17 views, 25 installs, and 2 GitHub stars.

Side-by-Side Model Context Protocol Comparison

LynxMCP vs Moxie Docs MCP

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

LynxMCP

Developer Tools · Local stdio

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

Moxie Docs MCP

Developer Tools · Local stdio

Quality: 72/100 (Great) | Auth: API Key required

Verdict Summary: Choose LynxMCP if you need specialized Developer Tools tools running via a local process. Choose Moxie Docs MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose LynxMCP when:

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

Explore LynxMCP Details

Choose Moxie Docs MCP when:

You need dedicated capabilities in the Developer Tools 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

Feature & Specification Comparison

Specification	LynxMCP lorenzo-cambiaghi Developer Tools	Moxie Docs MCP FeaturedVerifiedDeveloper Tools
Summary	100% local semantic code search for AI agents: AST-aware chunking (tree-sitter), hybrid BM25+dense retrieval, and a code knowledge graph (callers, inheritance, imports) over codebases, docs sites, and PDFs. Install via pipx install lynx-mcp.	MCP & Agent Skills for Automated Documentation, and codebase conventions + context
Category & Scope	Developer Tools	Developer Tools
Quality signal	39/100 (Emerging)	72/100 (Great)
Transport Protocol	Local Subprocess (stdio)	Local Subprocess (stdio)
Auth Requirement	No auth required	API Key required
Pricing Model	Free / Open Source	Freemium
Required Env Vars	None required	`MOXIE_TOKEN`
Compatible Clients	Claude DesktopCursorWindsurfClineVS Code	Claude DesktopCursorWindsurfClineVS Code
Install path signal	`npx · low`	`npx · high`
Engagement & Health	1 views 0 copies 0 upvotes 8 stars	17 views 25 copies 4 upvotes 2 stars
Verified / Official	Community Listing	Yes (Verified)
Open full listing	View LynxMCP Listing	View Moxie Docs MCP Listing

Tools & Capabilities Breakdown

LynxMCP Tools (0)

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

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

Discovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.

moxie.search_docs

Semantic + keyword search over generated docs, conventions, gaps, and AI context.

moxie.get_doc_gaps

Unresolved documentation gaps with severity and the paths they concern.

moxie.get_documentation_opportunities

Recommended doc work: missing docs, drift repairs, and PR templates.

moxie.get_documentation_patterns

How the repository organizes and maintains its docs (where new docs belong).

moxie.list_docs

Paginated, section-grouped table of contents of every generated doc.

moxie.propose_doc_update

Add or update a doc as part of your current change; returns the target path + Markdown to write into your branch.

moxie.propose_doc_removal

Remove a Moxie-tracked doc your change makes obsolete; returns the path to delete in your branch.

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

LynxMCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "lorenzo-cambiaghi-lynxmcp": {
      "command": "npx",
      "args": [
        "-y",
        "lorenzo-cambiaghi-lynxmcp"
      ]
    }
  }
}

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"
      }
    }
  }
}

Frequently Asked Questions

LynxMCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Moxie Docs MCP belongs to Developer Tools using local stdio subprocess. Select LynxMCP when you need capabilities focused on developer tools and Moxie Docs MCP when you require tools for developer tools.

More alternatives to LynxMCP More alternatives to Moxie Docs MCP Developer Tools category hub