What is the key difference between Cursor History and Shadcn Ui MCP Server?

Cursor History belongs to the Developer Tools category with local stdio execution, while Shadcn Ui MCP Server belongs to the Developer Tools category with local stdio execution.

How do I install Cursor History or Shadcn Ui MCP Server 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 Cursor History and Shadcn Ui MCP Server free or paid?

Cursor History operates under a Free / Open Source model (No auth required). Shadcn Ui MCP Server operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Cursor History lists 8 tools with 0 views and 32 GitHub stars. Shadcn Ui MCP Server lists 10 tools with 3 views and 2,999 GitHub stars.

Can I use both Cursor History and Shadcn Ui MCP Server 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

Cursor History vs Shadcn Ui MCP Server

In-depth architectural comparison of the Cursor History and Shadcn Ui MCP Server 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

Cursor History

Developer Tools · Local stdio

Quality: 56/100 (Good) | Auth: No auth required

Shadcn Ui MCP Server

Developer Tools · Local stdio

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

Verdict Summary: Choose Cursor History if you need specialized Developer Tools tools running via a local process. Choose Shadcn Ui MCP Server 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 Cursor History 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).
Primary tools included: cursor_history_list, cursor_history_show, cursor_history_search.

Explore Cursor History Details

Choose Shadcn Ui MCP Server when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: MCP_TRANSPORT_MODE, MCP_PORT, MCP_HOST, MCP_CORS_ORIGINS, GITHUB_PERSONAL_ACCESS_TOKEN, UI_LIBRARY.
Primary tools included: get_component, get_component_demo, list_components.

Feature & Specification Comparison

Specification	Cursor History Developer Tools	Shadcn Ui MCP Server Jpisnice Developer Tools
Summary	MCP server for browsing, searching, exporting, and backing up your Cursor AI chat history	MCP server that gives AI assistants seamless access to shadcn/ui v4 components, blocks, demos, and metadata.
Category & Scope	Developer Tools

Tools & Capabilities Breakdown

Cursor History Tools (8)

cursor_history_list

List sessions with IDs, index scope, source and data status. `limit`, `offset`, `workspace

cursor_history_show

Inspect available messages. Exactly one of `sessionId` / `sessionIndex`; optional `workspace

cursor_history_search

Search text. `query`, `limit`, `context` (neighboring source lines), `workspace

cursor_history_export

Return Markdown or JSON content, not a file written by the server. One selector, `format`, `workspace

cursor_history_backup

Create a Composer archive. `outputPath`, optional `force

cursor_history_restore

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

Cursor History Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "cursor-history": {
      "command": "npx",
      "args": [
        "-y",
        "cursor-history-mcp@0.3.1"
      ]
    }
  }
}

Shadcn Ui MCP Server Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "jpisnice-shadcn-ui-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@jpisnice/shadcn-ui-mcp-server"
      ],
      "env": {
        "MCP_TRANSPORT_MODE": "YOUR_MCP_TRANSPORT_MODE_HERE",
        "MCP_PORT": "YOUR_MCP_PORT_HERE",
        "MCP_HOST": "YOUR_MCP_HOST_HERE",
        "MCP_CORS_ORIGINS": "YOUR_MCP_CORS_ORIGINS_HERE",
        "GITHUB_PERSONAL_ACCESS_TOKEN": "YOUR_GITHUB_PERSONAL_ACCESS_TOKEN_HERE",
        "UI_LIBRARY": "YOUR_UI_LIBRARY_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Cursor History More alternatives to Shadcn Ui MCP Server Developer Tools category hub