What is the key difference between SHAFT MCP and Dossier?

SHAFT MCP belongs to the Developer Tools category with local stdio execution, while Dossier belongs to the Developer Tools category with local stdio execution.

How do I install SHAFT MCP or Dossier 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 SHAFT MCP and Dossier free or paid?

SHAFT MCP operates under a Free / Open Source model (No auth required). Dossier operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

SHAFT MCP lists 0 tools with 0 views and 0 GitHub stars. Dossier lists 0 tools with 0 views and 7 GitHub stars.

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

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

Yes! MCP clients support multi-server orchestration. You can include both shaft-mcp-2 and dossier 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, SHAFT MCP has a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Dossier holds a Quality Score of 44 /100 ( Fair ) with 0 views, 0 installs, and 7 GitHub stars.

Side-by-Side Model Context Protocol Comparison

SHAFT MCP vs Dossier

In-depth architectural comparison of the SHAFT MCP and Dossier 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

SHAFT MCP

Developer Tools · Local stdio

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

Dossier

Developer Tools · Local stdio

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

Verdict Summary: Choose SHAFT MCP if you need specialized Developer Tools tools running via a local process. Choose Dossier 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 SHAFT MCP 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 SHAFT MCP Details

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

Feature & Specification Comparison

Specification	S SHAFT MCP Developer Tools	D Dossier Developer Tools
Summary	SHAFT browser automation, capture, and offline deterministic failure diagnosis	MCP server for dossier automation standard - enables LLMs to discover, verify, and execute dossiers
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

SHAFT MCP Tools (0)

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

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

SHAFT MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "shaft-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "shaft-mcp-2"
      ]
    }
  }
}

Dossier Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "dossier": {
      "command": "npx",
      "args": [
        "-y",
        "@ai-dossier/cli"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to SHAFT MCP More alternatives to Dossier Developer Tools category hub Canonical compare URL

Related MCP Server Comparisons

Popular comparisons with SHAFT MCP

Popular comparisons with Dossier

R
Dossier vs Raycast