What is the key difference between Cli and Docvet?

Cli belongs to the Developer Tools category with cloud HTTP/SSE execution, while Docvet belongs to the Developer Tools category with local stdio execution.

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

Cli operates under a Free / Open Source model (No auth required). Docvet operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Cli lists 0 tools with 0 views and 0 GitHub stars. Docvet lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Cli and Docvet 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 Cli or Docvet 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 Cli and Docvet free to use, or do they require API keys?

Cli is listed under a Free / Open Source model with No auth required . Docvet operates under a Free / Open Source model with No auth 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 Cli and Docvet at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both cli and docvet 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, Cli has a Quality Score of 46 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars. Docvet holds a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Cli vs Docvet

In-depth architectural comparison of the Cli and Docvet 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

Cli

Developer Tools · Remote HTTP/SSE

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

Docvet

Developer Tools · Local stdio

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

Verdict Summary: Choose Cli if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Docvet 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 Cli when:

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

Explore Cli Details

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

Feature & Specification Comparison

Specification	C Cli Developer Tools	D Docvet Developer Tools
Summary	Slide decks locally: templates, checks, HTML to editable PowerPoint, .pptx rescue. No AI inside.	Docstring quality vetting for Python -- enrichment, freshness, coverage, and presence checks
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Cli Tools (0)

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

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

Cli Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "cli": {
      "url": "https://www.unpaper.ai/agents"
    }
  }
}

Docvet Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "docvet": {
      "command": "uvx",
      "args": [
        "docvet"
      ]
    }
  }
}

Frequently Asked Questions

Cli is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Docvet belongs to Developer Tools using local stdio subprocess. Select Cli when you need capabilities focused on developer tools and Docvet when you require tools for developer tools.

More alternatives to Cli More alternatives to Docvet Developer Tools category hub