Skip to main content

Compatibility Overview

Civic Nexus works with all major AI assistants and development tools. The setup method depends on whether your client supports remote MCP URLs or requires local configuration.

Get Started Now

Visit nexus.civic.com to select your tools and get your connection details
Quick rule: If your client settings mention “remote MCP URL” or “HTTP connector”, use Remote URL. If they only show “local MCP server” or “stdio/command”, use JSON Configuration.

Client Compatibility Matrix

ClientPlatformConnectionSetup TimePopularityGuide
Claude DesktopDesktopRemote URL2 mins🔥 Most PopularSetup
Claude.aiWebRemote URL2 mins🔥 Very PopularSetup
CursorDesktopHub Bridge3 mins🔥 Very PopularSetup
VS CodeDesktopHub Bridge3 mins🔥 PopularSetup
GooseCLIRemote URL2 mins📈 GrowingSetup
JetBrains IDEsDesktopHub Bridge2 mins💼 EnterpriseSetup
WindsurfDesktopHub Bridge2 mins🆕 NewSetup
Claude CodeCLIHub Bridge2 mins💻 DeveloperSetup
Gemini CLICLIHub Bridge2 mins🚀 GoogleSetup
ChatGPT Support: ChatGPT does not currently support MCP connectors and cannot connect to Civic Nexus. We’re monitoring ChatGPT’s roadmap and will add support when OpenAI releases MCP connector functionality. For now, we recommend Claude Desktop or Claude.ai for the best experience.

Connection Methods

How it works: Copy the MCP URL from nexus.civic.com and paste it into your client’s settings. Clients that support this:
  • Claude Desktop - Most popular choice
  • Claude.ai (Web) - No installation required
  • Goose - Developer CLI tool
  • Any client with “remote MCP URL” or “HTTP connector” options
Pros:
  • ✅ Fastest setup (2 minutes)
  • ✅ No local software needed
  • ✅ Automatic updates
  • ✅ Works across devices
  • ✅ Most reliable connection
Setup steps:
  1. Visit nexus.civic.com and select your tools
  2. Copy the MCP URL
  3. Paste into your client’s MCP settings

Claude Desktop Setup Guide

Complete walkthrough for the most popular setup method

JSON Configuration (Development Tools)

How it works: Edit your client’s JSON configuration file to add the Hub Bridge, which connects to Civic Nexus servers. Clients that need this:
  • Development Tools: Cursor, VS Code, JetBrains IDEs
  • CLI Tools: Windsurf, Claude Code, Gemini CLI
  • Any client with only “local MCP server” or “stdio” options
Pros:
  • ✅ Works with any MCP client
  • ✅ Local configuration control
  • ✅ Transparent setup process
Requirements:
  • Node.js 18+ installed
  • Access to edit configuration files
Common Configuration Formats:
  • Cursor
  • VS Code
  • Other Clients
File: .cursor/mcp.json in project root
{
  "mcpServers": {
    "civic-nexus": {
      "command": "npx",
      "args": ["-y", "@civic/hub-bridge@latest"]
    }
  }
}
Setup steps:
  1. Create account: Visit nexus.civic.com and select your tools
  2. Edit config file: Add the Hub Bridge configuration to your client’s JSON file
  3. Restart client: The bridge handles authentication automatically

Hub Bridge Setup Guide

Detailed configuration examples for all clients

Which Method Should I Use?

Start with Remote URL (If Supported)

If your client supports it, Remote URL is the better choice:
  • Faster setup - Just copy/paste a URL
  • 🚫 No Node.js requirement - Works immediately
  • 🔄 No local software to maintain - Always up to date
  • 🌐 Works across devices - Same URL everywhere

Use JSON Configuration When Required

Use JSON configuration for:
  • 💻 Development tools - IDEs like Cursor, VS Code, JetBrains
  • 🛠️ CLI tools - Command line interfaces and scripts
  • 📝 Local MCP clients - Tools that only support stdio/local servers
  • 🏢 Corporate environments - When remote URLs are blocked
Not sure which method? Check your client’s settings - if you see “remote MCP URL” options, use Remote URL. If you only see “local MCP server” or need to configure a command, use JSON configuration.

Common Setup Scenarios

🆕 First-Time Users

Recommendation: Start with Claude Desktop (Remote URL)
  • ✅ Easiest 2-minute setup process
  • ✅ Most reliable connection method
  • ✅ Best documentation and community support
  • ✅ Perfect for learning how Civic Nexus works

Start with Claude Desktop

Get up and running in 2 minutes with the most popular setup

👩‍💻 Developers

Popular development workflows: Pro tip: Many developers use Claude Desktop for quick queries alongside their IDE setup.

👥 Teams & Organizations

Team-friendly options:
  • 🌐 Claude.ai (Web): No installation required, works from any browser
  • 🖥️ Claude Desktop: Consistent experience across all team members
  • 🔗 Multiple clients: Each team member can use their preferred client with the same nexus.civic.com account

🏢 Enterprise Users

Enterprise considerations:
  • JetBrains IDEs: Popular in enterprise development environments
  • JSON Configuration: Better for IT management and deployment
  • Corporate firewalls: JSON config may work better with strict network policies

Troubleshooting Common Issues

Problem: Your client only supports local/stdio MCP serversSolution: Use JSON configuration instead of Remote URL:
  1. Find your client in our setup guides
  2. Follow the JSON configuration instructions
  3. Your client will use the Hub Bridge to connect to Civic Nexus
Problem: JSON configuration requires Node.js but it’s not installedSolution:
  • Install Node.js 18+ from nodejs.org
  • Or use a package manager: brew install node (macOS) or winget install OpenJS.NodeJS (Windows)
  • Restart your terminal/IDE after installation
  • Verify with node --version
Remote URL issues:
  • Check internet connection and firewall settings
  • Try visiting nexus.civic.com directly in browser
  • Corporate firewalls may block the connection
JSON configuration issues:
  • Ensure Node.js is properly installed (node --version)
  • Try restarting your client completely
  • Check that the JSON syntax is correct (no trailing commas, proper quotes)
Problem: OAuth authentication not workingSolutions:
  • Clear browser cache and try again
  • Use incognito/private browsing mode
  • Check if your organization blocks OAuth flows
  • Try from a different network (personal vs corporate)
  • Make sure you’re creating an account at nexus.civic.com first
Problem: Connected but can’t see/use toolsSolutions:
  • Make sure you selected tools during account creation at nexus.civic.com
  • Try asking: "What tools do I have available?" or "What MCP servers are connected?"
  • Restart your client completely after setup
  • For JSON config: verify the configuration file syntax is correct

Still Need Help?

Join our developer community with your specific client and error details

Getting Help & Next Steps

1

Select Your Tools

Visit nexus.civic.com to browse and select from dozens of available MCP servers
2

Test Your Connection

Try commands like: "What tools are available?" or "Check my GitHub repositories"
3

Add More Tools

Use chat commands: "Connect me to Slack" or "Add Dropbox to my tools"
4

Explore Capabilities

See our server reference for what each tool can do

Technical Details

Protocol: HTTP/HTTPS MCP over REST API Authentication: OAuth2 with PKCE flow Token Management: Automatic refresh, secure storage Transport: JSON-RPC over HTTP Benefits: Cloud-native, automatically updated, cross-platform
Protocol: stdio MCP (local process communication) Authentication: Proxied OAuth2 through local server Token Management: Local encrypted storage Transport: JSON-RPC over stdin/stdout Benefits: Works with any MCP client, local control