Spicy Regs MCP Server

Pro · Max · Team · Enterpriseweb & desktop

1. Open Settings → Connectors → Add custom connector.
2. Name it Spicy Regs.
3. Set the URL to the endpoint above.
4. Leave authentication as None — the dataset is public.
5. Save, then toggle the connector on in any conversation.

Remote HTTP:

claude mcp add --transport http spicy-regs https://mcp.spicy-regs.dev/mcp

Local stdio via uvx (no remote dependency):

claude mcp add spicy-regs -- uvx --from "spicy-regs @ git+https://github.com/civictechdc/spicy-regs" spicy-regs-mcp

Add to your MCP config, then enable it under Settings → MCP.

~/.cursor/mcp.json (global) · .cursor/mcp.json (per-project)

{
  "mcpServers": {
    "spicy-regs": { "url": "https://mcp.spicy-regs.dev/mcp" }
  }
}

Add a workspace MCP config (Copilot Agent mode required).

.vscode/mcp.json

{
  "servers": {
    "spicy-regs": { "type": "http", "url": "https://mcp.spicy-regs.dev/mcp" }
  }
}

Add to the Cascade MCP config, then refresh the server list.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "spicy-regs": { "serverUrl": "https://mcp.spicy-regs.dev/mcp" }
  }
}

Most clients accept a remote streamable-HTTP URL:

https://mcp.spicy-regs.dev/mcp

Or run it locally over stdio with uvx:

uvx --from "spicy-regs @ git+https://github.com/civictechdc/spicy-regs" spicy-regs-mcp