Cursor Setup

Connect Cursor AI code editor to Civic in 3 minutes

Prerequisites

Cursor Editor

Download and install Cursor (free tier works)

Civic Account

Sign up at app.civic.com and grab your token

How authentication works

Civic supports two methods depending on how your client connects:

Client type	Method	How it works
Interactive clients (Claude Desktop, Cursor, VS Code, Gemini CLI, Goose, Windsurf)	OAuth	When you connect, your client opens a browser window to app.civic.com. Sign in once — no manual token needed.
Automated agents (LangChain, custom scripts, OpenAI SDK, Anthropic SDK)	Civic Token	Generate a bearer token at app.civic.com → Install → MCP URL. Pass it as an Authorization: Bearer header.

See Get Your Credentials for full details.

Setup Steps

1. Get Your Civic URL and Token

   Log in to app.civic.com and copy your Civic URL and API token from your account settings.

   Your Civic URL looks like this:

   https://app.civic.com/hub/mcp?profile=YOUR_PROFILE
   

   If you haven’t set up Civic yet, the onboarding takes about 2 minutes:
2. Open Cursor MCP Settings

   Go to Settings → Tools & MCPs → New MCP Server

3. Add Civic MCP Server

   Paste the following configuration:

   {
     "mcpServers": {
       "civic": {
         "url": "YOUR_CIVIC_URL",
         "headers": {
           "Authorization": "Bearer YOUR_TOKEN_HERE"
         }
       }
     }
   }
   

   Replace YOUR_CIVIC_URL with your Civic URL and YOUR_TOKEN_HERE with your API token.

4. Enable and Test

   The server should appear in your MCP servers list. If you don’t see it, try disabling and re-enabling it.

Test Your Connection

Try these prompts in Cursor to verify everything works:

"What MCP servers are available?"
"Show me my connected tools"
"Help me set up GitHub integration"

Troubleshooting

Civic not showing in MCP settings

1. Make sure you saved the configuration after adding it
2. Check that your URL and token are correct
3. Try disabling and re-enabling the server
4. Restart Cursor

Authentication errors

1. Verify your token is correct and hasn’t expired
2. Make sure you’re using the Bearer prefix in the Authorization header
3. Try generating a new token from app.civic.com

Connection timeouts

1. Check your internet connection
2. Verify the Civic URL is correct
3. Try removing and re-adding the MCP server

Legacy Setup: Hub Bridge

What is Hub Bridge? Hub Bridge (@civic/hub-bridge) is a lightweight local proxy that runs on your machine via npx and bridges stdio-only MCP clients to Civic’s remote HTTP endpoint. Use it when your client doesn’t support remote HTTP MCP connections natively. If your client supports HTTP/Streamable HTTP MCP — use that instead (it’s simpler and has no Node.js dependency).

Full Hub Bridge setup guide →

If you’re on an older version of Cursor that doesn’t support HTTP MCP servers, you can use Hub Bridge as a local stdio proxy instead. This requires Node.js 18+.

Hub Bridge setup (legacy)

One-Click Install

Manual Config File

Create .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "civic": {
      "command": "npx",
      "args": ["-y", "@civic/hub-bridge"]
    }
  }
}

The first time you use a tool, Hub Bridge opens a browser window to app.civic.com for authentication.

Managing Your Tools

Adding More Tools

You can add new tools directly in your Cursor chat:

"Connect me to GitHub"
"Add Slack to my available tools"
"I need access to PostgreSQL"
"Show me what tools are available to connect"

Removing Tools

You can disconnect from specific tools directly in chat:

"Disconnect from Slack"
"Remove GitHub from my tools"
"What tools do I currently have connected?"

Removing the MCP Server

Go to Settings → Tools & MCPs, find “Civic” in your MCP servers list, and delete it.

Resources

Client Compatibility

Technical details about Cursor’s MCP support

Troubleshooting

Common Cursor connection issues

Get Help

Join our developer community for setup assistance