MCP Integration Guide
Overview
reasoning.services exposes four cognitive tools as MCP (Model Context Protocol) servers:
- Structured Reflection β Guided self-reflection that surfaces what you are missing
- Sequential Thinking β Stage gates that prevent skipping steps
- Context Switcher β Multi-perspective analysis from 9 viewpoints
- Decision Matrix β Weighted criteria with sensitivity analysis
Prerequisites: An active reasoning.services subscription and your API token from the account dashboard.
Claude Desktop
Claude Desktop has native MCP support. Add reasoning.services to your configuration file:
1. Locate your configuration file
The config file location varies by operating system:# macOS
~/Library/Application Support/Claude/claude_desktop_config.json
# Windows
%APPDATA%\Claude\claude_desktop_config.json
# Linux
~/.config/Claude/claude_desktop_config.json2. Add the MCP server configuration
{
"mcpServers": {
"reasoning-services": {
"command": "npx",
"args": [
"-y",
"@anthropic-ai/mcp-remote",
"https://reasoning.services/mcp/sse",
"--header",
"Authorization: Bearer YOUR_API_TOKEN"
]
}
}
}3. Restart Claude Desktop
Quit and reopen Claude Desktop. You should see the reasoning.services tools available in your tools menu.
Cursor
Cursor supports MCP servers through its settings. Add reasoning.services tools to your coding workflow:
1. Open Cursor Settings
Go to Settings β Features β MCP Servers
2. Add new MCP server
{
"reasoning-services": {
"command": "npx",
"args": [
"-y",
"@anthropic-ai/mcp-remote",
"https://reasoning.services/mcp/sse",
"--header",
"Authorization: Bearer YOUR_API_TOKEN"
]
}
}3. Reload Cursor
Use the command palette (Cmd/Ctrl + Shift + P) and run "Developer: Reload Window" to activate the new MCP server.
Claude Code (CLI)
Add reasoning.services to your Claude Code MCP configuration:
1. Edit your MCP settings
# Open MCP settings
claude mcp add reasoning-services
# Or edit directly at:
~/.claude/claude_settings.json2. Add the server configuration
{
"mcpServers": {
"reasoning-services": {
"command": "npx",
"args": [
"-y",
"@anthropic-ai/mcp-remote",
"https://reasoning.services/mcp/sse",
"--header",
"Authorization: Bearer YOUR_API_TOKEN"
]
}
}
}Authentication
Getting Your API Token
- Sign in to your reasoning.services account
- Navigate to Account β API Tokens
- Generate a new token
- Copy and securely store the token (it won't be shown again)
Security note: Keep your API token secure. Don't commit it to version control. Use environment variables or secret management tools for production deployments.
Using Environment Variables
# In your shell profile (.zshrc, .bashrc, etc.)
export REASONING_SERVICES_TOKEN="your_api_token_here"
# Then in your MCP config, use:
"--header",
"Authorization: Bearer $REASONING_SERVICES_TOKEN"Available Tools
Once connected, you'll have access to these MCP tools:
start_reflection / reflect / conclude_reflection
Structured Reflection tools for guided problem-solving sessions.
> Start a reflection session about this architecture decision
> reflect: "I'm not sure if I should use microservices or monolith"
> Get insights from the sessionprocess_thought / generate_summary
Sequential Thinking tools for staged reasoning with checkpoints.
> Process thought: "First, let's define the problem clearly"
> Stage: Problem Definition
> Continue with Research stage...start_context_analysis / analyze_from_perspectives / synthesize
Context Switcher tools for multi-perspective analysis.
> Analyze "Should we migrate to Kubernetes?" from:
> - Technical perspective
> - Business perspective
> - Risk perspective
> Synthesize findingsstart_decision_analysis / add_criterion / evaluate_options
Decision Matrix tools for weighted decision-making.
> Compare PostgreSQL vs MongoDB vs DynamoDB
> Criteria: consistency (weight: 1.5), scalability (1.0), cost (0.8)
> Run sensitivity analysisTroubleshooting
"Server not responding" or connection timeouts
- β’Verify your API token is correct and not expired
- β’Check that
npxis available in your PATH - β’Ensure you have network access to
reasoning.services - β’Try restarting your MCP client after configuration changes
"Unauthorized" errors (401)
- β’Regenerate your API token from the account dashboard
- β’Ensure the token is prefixed with
Bearer(note the space) - β’Check that your subscription is active
Tools not appearing in client
- β’Verify your JSON configuration syntax is valid
- β’Check client logs for MCP connection errors
- β’Try testing the mcp-remote package directly:
npx @anthropic-ai/mcp-remote \
https://reasoning.services/mcp/sse \
--header "Authorization: Bearer YOUR_TOKEN"