Skip to main content

​
Overview

This section covers setup for development tools and IDEs that require more technical configuration than the primary ChatGPT/Claude clients.
New to Civic Nexus? Start with Claude Desktop for the simplest setup experience, then add development tools later.

​
Prerequisites

All development tools require:

Node.js 18+

Required for the Hub Bridge - check with node —version

Civic Account

Free signup - authenticate development tools via OAuth

​
Quick Start (2 Options)

​
Option 1: Direct HTTP Connection

1

Get MCP URL

Visit nexus.civic.com and copy your personal MCP endpoint URL
2

Configure Client

Add the HTTP endpoint directly to your development tool’s MCP configuration
3

Authenticate

Follow OAuth prompts when first using any server - tokens are securely stored

​
Option 2: Hub Bridge (Local Proxy)

1

Configuration

Add npx -y @civic/hub-bridge as your MCP server command in client settings
2

Authentication

Run any MCP command - OAuth browser window opens automatically for first-time setup
3

Usage

Hub Bridge handles authentication and routes requests to your selected Civic Nexus servers
Performance: HTTP endpoints are faster. Compatibility: Hub Bridge works with more clients that don’t support HTTP endpoints yet.

​
Cursor Setup

Most Popular Development Tool - AI-powered code editor with excellent MCP support.

Complete Cursor Setup Guide

One-click install available - Complete walkthrough with troubleshooting and testing steps
 Quick Summary:
  • ✅ One-click install button available
  • ✅ Node.js 18+ required
  • ✅ Works with free and paid Cursor plans
  • ⏱️ Setup time: 2 minutes

​
VS Code Setup

Industry Standard Editor - Support for both HTTP connectors and Hub Bridge method.

Complete VS Code Setup Guide

Multiple setup methods - HTTP connector, Hub Bridge, and one-click install options
 Quick Summary:
  • ✅ Remote HTTP connector support (recommended)
  • ✅ Hub Bridge fallback method available
  • ✅ One-click install link included
  • ⏱️ Setup time: 2 minutes

Get Support

Having setup issues? Join our developer community for assistance with your development environment.

​
Client Compatibility

​
AI-First Code Editors

Cursor

Setup Time: 3 minutes Method: One-click install or Hub Bridge HTTP Support: ✅ Via Hub Bridge

Windsurf

Setup Time: 3 minutes
Method: Hub Bridge configuration HTTP Support: ❌ Requires Hub Bridge

​
Traditional IDEs

VS Code

3 minutes - HTTP endpoint or Hub Bridge

JetBrains IDEs

5 minutes - Hub Bridge via MCP plugin

Vim/Neovim

Advanced setup - Community MCP plugins

​
Command Line Tools

Goose

2 minutes - HTTP endpoint support

Claude Code

Coming Soon - Direct integration planned

Gemini CLI

Coming Soon - MCP support planned

​
JetBrains IDEs Setup

Enterprise Development Environment - Full IDE suite with robust MCP plugin support.

Complete JetBrains Setup Guide

Plugin-based setup - Step-by-step guide for IntelliJ, PyCharm, WebStorm, and all JetBrains IDEs
 Quick Summary:
  • ✅ Supports all JetBrains IDEs (IntelliJ, PyCharm, WebStorm, etc.)
  • ✅ MCP plugin available in marketplace
  • ✅ Hub Bridge integration method
  • ⏱️ Setup time: 2 minutes

​
Windsurf Setup

Codeium AI IDE - Modern AI-powered development environment with MCP support.

Complete Windsurf Setup Guide

Hub Bridge method - Configuration steps for Windsurf’s MCP integration
 Quick Summary:
  • ✅ Codeium AI IDE integration
  • ✅ Hub Bridge configuration required
  • ✅ JSON-based setup process
  • ⏱️ Setup time: 2 minutes

​
Goose Setup

Block’s Developer Agent - Command-line AI assistant with direct HTTP endpoint support.

Complete Goose Setup Guide

Direct HTTP support - No Hub Bridge needed, direct MCP URL configuration
 Quick Summary:
  • ✅ Direct HTTP endpoint support (no Hub Bridge needed)
  • ✅ YAML configuration file setup
  • ✅ Advanced toolkit configurations available
  • ⏱️ Setup time: 2 minutes

​
Best Practices

​
Development Workflow

  1. Start simple - Use one server first (like GitHub or Slack)
  2. Test incrementally - Add one server at a time
  3. Monitor usage - Check your Civic Nexus dashboard for activity
  4. Update regularly - Keep Hub Bridge updated with npm update -g @civic/hub-bridge

​
Team Collaboration

For teams using the same tools:
  1. Commit config files to version control (they don’t contain secrets)
  2. Document setup in your project README
  3. Use consistent naming across team members
  4. Share tool selections - use same Civic Nexus server selection

​
Security Considerations

  • Hub Bridge runs locally - tokens never leave your machine except to make API calls
  • Tokens are encrypted using OS-level key storage
  • OAuth scopes are minimal - only request necessary permissions
  • Revoke access anytime at nexus.civic.com

Security Details

Complete security documentation and compliance information