Cursor Setup
Prerequisites
Download and install Cursor (free tier works)
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
- 1Get 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_PROFILEIf you haven't set up Civic yet, the onboarding takes about 2 minutes:
- 1Create a free Civic account
Go to app.civic.com and sign in with Google, GitHub, or email.
- 2Select your MCP servers
During onboarding, choose which services you want your AI to access — GitHub, Slack, Google Workspace, Dropbox, and more. This creates your default toolkit.
- 3Get your MCP URL
Your connection URL is the same for every Civic account:
https://app.civic.com/hub/mcpThe URL is not personalized — what makes it yours is authentication. When you connect your client and complete the OAuth flow, Civic links that session to your account and toolkit.
- 2Open Cursor MCP Settings
Go to Settings → Tools & MCPs → New MCP Server
- 3Add Civic MCP Server
Paste the following configuration:
{"mcpServers": {"civic": {"url": "YOUR_CIVIC_URL","headers": {"Authorization": "Bearer YOUR_TOKEN_HERE"}}}}Replace
YOUR_CIVIC_URLwith your Civic URL andYOUR_TOKEN_HEREwith your API token. - 4Enable 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
- Make sure you saved the configuration after adding it
- Check that your URL and token are correct
- Try disabling and re-enabling the server
- Restart Cursor
Authentication errors
- Verify your token is correct and hasn't expired
- Make sure you're using the
Bearerprefix in the Authorization header - Try generating a new token from app.civic.com
Connection timeouts
- Check your internet connection
- Verify the Civic URL is correct
- 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).
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)
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.