Counsel MCP Server

An open-source Model Context Protocol (MCP) server that connects AI agents to the Counsel API for strategic reasoning and multi-perspective analysis.

Features

• Hosted & Self-Hosted - Use the hosted server instantly or run your own instance
• Strategic Reasoning - Access Counsel's debate and multi-perspective reasoning engines
• Advisor Sessions - Run interactive intake and profile tuning sessions
• Native OAuth 2.0 - Standard MCP authentication handled automatically by clients
• Dual Transport - STDIO for local clients, HTTP for web clients and shared servers

Table of Contents

• Quick Start (Hosted)
• Installation (Self-Hosted)
  • Claude Desktop
  • Claude Code (CLI)
  • Cursor
  • Windsurf
  • VS Code with Copilot
  • Other MCP Clients
• Authentication
• Available Tools
• Usage Examples
• Configuration
• Troubleshooting
• Development
• Contributing
• License

Quick Start (Hosted)

Connect instantly to the hosted Counsel MCP server - no installation required:

http://counsel-mcp.getmason.dev/mcp

For MCP clients that support HTTP transport, simply add:

{
  "mcpServers": {
    "counsel": {
      "url": "http://counsel-mcp.getmason.dev/mcp",
      "transport": "http"
    }
  }
}

OAuth authentication is handled automatically by your MCP client.

Installation (Self-Hosted)

Run your own instance of the Counsel MCP server locally.

Prerequisites

1. Node.js 18+ installed on your system
2. A Counsel account at counsel.getmason.dev

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "counsel": {
      "command": "npx",
      "args": ["-y", "counsel-mcp-server", "start"]
    }
  }
}

{
  "mcpServers": {
    "counsel": {
      "command": "npx",
      "args": ["-y", "counsel-mcp-server", "start"]
    }
  }
}

Claude Code (CLI)

claude mcp add counsel -- npx -y counsel-mcp-server start

Or manually add to your MCP settings:

{
  "mcpServers": {
    "counsel": {
      "command": "npx",
      "args": ["-y", "counsel-mcp-server", "start"]
    }
  }
}

Cursor

Add to your Cursor MCP configuration (.cursor/mcp.json in your project or global settings):

{
  "mcpServers": {
    "counsel": {
      "command": "npx",
      "args": ["-y", "counsel-mcp-server", "start"]
    }
  }
}

Windsurf

Add to your Windsurf MCP configuration:

{
  "mcpServers": {
    "counsel": {
      "command": "npx",
      "args": ["-y", "counsel-mcp-server", "start"]
    }
  }
}

VS Code with Copilot

Add to your VS Code settings (settings.json):

{
  "mcp.servers": {
    "counsel": {
      "command": "npx",
      "args": ["-y", "counsel-mcp-server", "start"]
    }
  }
}

Other MCP Clients

The server supports two transport modes. Choose based on your client's capabilities:

STDIO Mode (Default)

Most MCP clients use STDIO transport. Configure with:

{
  "mcpServers": {
    "counsel": {
      "command": "npx",
      "args": ["-y", "counsel-mcp-server", "start"],
      "env": {
        "COUNSEL_API_KEY": "your_api_key_here"
      }
    }
  }
}

HTTP Mode with OAuth

For clients that support HTTP transport with OAuth 2.0, run the server separately:

# Start the HTTP server
npx -y counsel-mcp-server http --port 3000

This starts an HTTP server with:

• MCP endpoint: http://localhost:3000/mcp
• OAuth discovery: http://localhost:3000/.well-known/oauth-authorization-server

Then configure your client to connect:

{
  "mcpServers": {
    "counsel": {
      "url": "http://localhost:3000/mcp",
      "transport": "http"
    }
  }
}

HTTP mode uses OAuth 2.0 with automatic token management - no API key required.

Transport Comparison

Authentication

The server supports two authentication modes:

STDIO Mode (Default)

Set the COUNSEL_API_KEY environment variable with your API key from counsel.getmason.dev:

export COUNSEL_API_KEY=your_api_key_here

Or add it to your MCP client configuration:

{
  "mcpServers": {
    "counsel": {
      "command": "npx",
      "args": ["-y", "counsel-mcp-server", "start"],
      "env": {
        "COUNSEL_API_KEY": "your_api_key_here"
      }
    }
  }
}

HTTP Mode (OAuth 2.0)

When running in HTTP mode (npx -y counsel-mcp-server http), authentication is handled automatically through OAuth 2.0:

1. When you first use a Counsel tool, your MCP client will prompt for authentication
2. You'll be redirected to sign in with your Counsel account
3. After authorization, tokens are managed automatically

No manual API key required in HTTP mode - your MCP client handles the entire OAuth flow.

OAuth Endpoints (HTTP Mode)

The server exposes standard OAuth 2.0 endpoints:

Available Tools

start_consultation

Start a new strategic consultation (debate) to analyze a complex question with multiple perspectives.

Example:

Start a consultation about "Should we migrate our monolith to microservices?"
with context about our 50-person engineering team and mode set to deep

get_consultation_status

Check the status of an ongoing consultation.

get_consultation_report

Retrieve the final synthesis report from a completed consultation.

list_consultations

List your past consultations.

sharpen_question

Refine and improve a strategic question before starting a consultation.

Example:

Sharpen this question: "Is AI good for our company?"

consult_advisor

Start an interactive advisor session for brainstorming or scoping problems.

Usage Examples

Strategic Decision Making

Use Counsel to analyze: "Should we expand into the European market in 2025?"

Consider these stakeholders: CEO, CFO, Head of Sales, Legal
Use deep analysis mode

Question Refinement

Use the sharpen_question tool to improve this question:
"How do we fix our culture?"

Context: We're a 200-person startup experiencing rapid growth

Checking Consultation Progress

Check the status of consultation abc-123-def

Configuration

Environment Variables

CLI Commands

# STDIO mode (default) - for most MCP clients
npx -y counsel-mcp-server start

# HTTP mode - for clients supporting OAuth
npx -y counsel-mcp-server http [options]

HTTP Options:
  -p, --port <port>  Port to listen on (default: 3000)
  --host <host>      Host to bind to (default: localhost)

Troubleshooting

"Tool not found" Error

Ensure the MCP server is properly configured in your client. Restart your client after adding the configuration.

Authentication Issues

1. Check that you have a valid Counsel account
2. Try removing and re-adding the MCP server configuration
3. Clear your client's MCP cache if available

Connection Refused