Skip to directory

Civic MCP Hub (listed as Civic Nexus)

Civic

Streamable HTTPTool names not enumerated1

About Civic MCP Hub (listed as Civic Nexus)

Civic Hub aggregates user-selected third-party MCP servers behind one authenticated connection, with server-specific guardrails and configuration.

What you can use it for

  • Connect to selected third-party services across productivity, development, databases, finance and analytics.
  • Configure a custom profile/toolkit and expose its selected tools to an AI client.
Connection and setup
Hosting
remote
Transport
Streamable HTTP
Endpoint
https://app.civic.com/hub/mcp
Authentication
Civic Hub OAuth or configured bearer token; selected profile/toolkit determines access.

Requirements

  • Civic account
  • At least one configured toolkit/server in the Civic app
  • Browser access for interactive OAuth, or Civic bearer token for automation

Setup steps

  1. Sign in at https://app.civic.com and configure a toolkit by selecting integrations/tools to expose.
  2. Add https://app.civic.com/hub/mcp as a remote Streamable HTTP MCP server in a supported client.
  3. For interactive clients, connect and complete browser OAuth sign-in. For automated clients, generate a Civic token in the app Install screen and send it as Authorization: Bearer <CIVIC_TOKEN>; store it outside chat and source control.
  4. Optionally add ?profile=<toolkit-alias> to the URL to select a toolkit; documentation says the default locks the session to that profile.
  5. Ask the client to list available tools to verify the configured profile. The exact tool catalog depends on the user toolkit and authorization.
Tools

No individual tool names are documented in the reviewed sources.

This is a configurable MCP aggregator rather than one fixed server inventory. Civic documentation reports ~200 tools across 85 servers in the catalog, while the user’s selected toolkit controls the actual tool list; exact names are not static.

Limitations and notes
  • Tools and schemas vary with the configured Civic profile and connected services. Civic renamed the Nexus product to Civic; do not treat the global catalog count as the number exposed by a single profile.
Source discrepancies
  • Original queue name is Civic Nexus; current first-party docs refer to Civic MCP Hub. Treated as the same vendor service based on official announcement and current docs, but no explicit rename notice found.
Original sources
  • official publisher documentation

    Official guide documents Hub MCP endpoint and remote/bridge connection options.

  • official publisher documentation

    Official changelog identifies rebrand from Nexus to Civic.

  • official publisher documentation

    Publisher or maintainer documentation reviewed 2026-10-28T19:30:00.000Z; capability and connection information recorded, with exact protocol tool identifiers added only when the source publishes them.

  • official crawl4ai tool inventory audit

    Crawl4AI 0.9.5 fetched the selected documentation page. No exact MCP tool identifiers were present in the captured page content; where attempted, the hosted tools/list endpoint required authorization.

  • official crawl4ai tool inventory audit

    Civic documents tools/list after authentication and toolkit/profile locking; returned tools depend on the configured toolkit, so there is no global static list.

Documentation checked 2026-10-28T19:30:00.000Z. Connection has not been runtime tested.