What is the key difference between CourtListener and Reginfo?

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

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

CourtListener operates under a Free / Open Source model (No auth required). Reginfo operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

CourtListener lists 0 tools with 2 views and 3 GitHub stars. Reginfo lists 0 tools with 0 views and 0 GitHub stars.

Can I use both CourtListener and Reginfo 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

CourtListener vs Reginfo

In-depth architectural comparison of the CourtListener and Reginfo 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

CourtListener

Developer Tools · Remote HTTP/SSE

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

Reginfo

Developer Tools · Local stdio

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

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

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

Feature & Specification Comparison

Specification	CourtListener Developer Tools	R Reginfo Developer Tools
Summary	MCP for CourtListener: US federal and state opinions, dockets, judges, plus eCFR regulations.	reginfo MCP — the Unified Agenda of Federal Regulatory and Deregulatory
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

CourtListener Tools (0)

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

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

CourtListener Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "courtlistener": {
      "url": "https://mcp.courtlistener.com/"
    }
  }
}

Reginfo Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "reginfo": {
      "command": "npx",
      "args": [
        "-y",
        "reginfo"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to CourtListener More alternatives to Reginfo Developer Tools category hub