What is the key difference between Raycast and SHAFT MCP?

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

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

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

Which MCP server has more tools and community activity?

Raycast lists 0 tools with 1 views and 5 GitHub stars. SHAFT MCP lists 0 tools with 0 views and 0 GitHub stars.

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

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

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

Side-by-Side Model Context Protocol Comparison

Raycast vs SHAFT MCP

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

Raycast

Developer Tools · Local stdio

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

SHAFT MCP

Developer Tools · Local stdio

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

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

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

Feature & Specification Comparison

Specification	R Raycast Developer Tools	S SHAFT MCP Developer Tools
Summary	Raycast workflow automation MCP server with 9 tools	SHAFT browser automation, capture, and offline deterministic failure diagnosis
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Raycast Tools (0)

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

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

Raycast Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "raycast": {
      "command": "npx",
      "args": [
        "-y",
        "raycast-mcp-server"
      ]
    }
  }
}

SHAFT MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Raycast More alternatives to SHAFT MCP Developer Tools category hub

Related MCP Server Comparisons

Popular comparisons with Raycast

Popular comparisons with SHAFT MCP

S
SHAFT MCP vs Shiplight