Skip to main content

Overview

Goose (Block’s autonomous developer agent) now supports direct remote HTTP endpoints for connecting to Civic Nexus MCP servers with full OAuth2 support.

Prerequisites

Setup with Remote HTTP Endpoint

1

Get your MCP URL

  1. Sign in to nexus.civic.com
  2. Select the MCP servers you want to use
  3. Copy the MCP URL: https://nexus.civic.com/hub/mcp
2

Configure Goose

Add the Civic Nexus MCP server to your Goose configuration:
  1. Open your Goose configuration file (typically ~/.config/goose/config.yaml or project-specific .goose/config.yaml)
  2. Add the following MCP server configuration:
mcp:
  servers:
    civic-nexus:
      type: http
      url: https://nexus.civic.com/hub/mcp
      name: "Civic Nexus"
Goose supports HTTP endpoints directly, no local bridge required.
3

Restart Goose

Restart Goose to load the new configuration:
goose restart
Or if running as a service:
goose stop
goose start
4

Test Connection

Verify the connection is working:
"What MCP servers are available?"
"Show me my connected tools"
Goose should respond with the list of available Civic Nexus tools.
5

Authenticate Services

When you first use a tool that requires authentication:
  1. Goose will prompt you to authorize access
  2. A browser window will open for OAuth authentication
  3. Sign in to the service and authorize access
  4. Return to Goose when complete
Authentication is handled securely by Civic Nexus. Your credentials are never exposed to Goose or stored locally.

Alternative: Hub Bridge Setup

If you prefer to use the local Hub Bridge instead of direct HTTP endpoints:
1

Configure Hub Bridge

Add this to your Goose configuration:
mcp:
  servers:
    civic-nexus:
      type: stdio
      command: npx
      args: ["-y", "@civic/hub-bridge"]
2

Install Node.js

Make sure Node.js 18+ is installed for the Hub Bridge to work
3

Restart and Test

Restart Goose and test with: “What MCP servers are available?”

Resources