Log inSubmit server

Ca Rate Filings vs Posthog

A side-by-side look at the Ca Rate Filings and Posthog MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

C
Ca Rate FilingsDeveloper ToolsNatural-language search over California's public insurance rate, rule & form filings.12EmergingAuth: not declaredPosthog logoPosthogDeveloper Tools · Local subprocess (stdio)Interact with PostHog analytics, feature flags, error tracking and more.55GoodAuth: api key required

Verdict: choose Ca Rate Filings for developer tools work; choose Posthog for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

C
Choose Ca Rate Filings when

  • You need dedicated capabilities in the Developer Tools domain.
Explore Ca Rate Filings

Posthog logoChoose Posthog when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: POSTHOG_AUTH_HEADER.
Explore Posthog

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
C
Ca Rate Filings		Posthog logoPosthog
CategoryDeveloper ToolsDeveloper Tools
Quality signal12/100 · Emerging55/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredNot declared
Required env varsNone listedPOSTHOG_AUTH_HEADER
Verified ownerCommunity listingCommunity listing
GitHub stars—40,429
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView Ca Rate Filings View Posthog

Tools & capabilities

Ca Rate Filings tools

No tool names declared yet. Check the project README from the listing page.

Posthog tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Ca Rate Filings

No confirmed install command for Ca Rate Filings yet — follow the setup steps linked from its listing page rather than a guessed package name.

Posthog

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "posthog-posthog": {
      "command": "npx",
      "args": [
        "-y",
        "@posthog/wizard@latest"
      ],
      "env": {
        "POSTHOG_AUTH_HEADER": "YOUR_POSTHOG_AUTH_HEADER_HERE"
      }
    }
  }
}

Frequently asked questions

Ca Rate Filings is categorized under Developer Tools and uses an install path we have not confirmed yet. Posthog belongs to Developer Tools and uses a local stdio subprocess. Pick Ca Rate Filings for developer tools work and Posthog for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Ca Rate Filings has no confirmed install command yet — follow its own setup instructions.

Ca Rate Filings has no declared pricing — check the project's own site. Posthog has no declared pricing — check the project's own site. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add ca-rate-filings and posthog-posthog as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Ca Rate Filings has a quality signal of 12/100 (Emerging) with 1 views, 0 installs and 0 GitHub stars. Posthog has 55/100 (Good) with 1 views, 0 installs and 40,429 GitHub stars.

Popular comparisons with Ca Rate Filings

Popular comparisons with Posthog