Navigation

Getting Started

Connect in Minutes

Paste your API key, add the config snippet, restart your client — that is it. Your reasoning tools will be available in Claude's tool list.

Connect Claude Desktop

Claude Desktop reads MCP server definitions from a JSON config file. Add the following block — substituting your rsvc_ key — then restart the app. The "type": "http" format uses native streamable HTTP transport: no local proxy or additional tooling required.

1. Locate your config file

bash
# macOS
~/Library/Application Support/Claude/claude_desktop_config.json

# Windows
%APPDATA%\Claude\claude_desktop_config.json

# Linux
~/.config/Claude/claude_desktop_config.json

2. Add the MCP server entries

Each service is its own MCP server. Add all four entries under mcpServers and replace YOUR_RSVC_API_KEY with the key from your welcome email.
json
{
  "mcpServers": {
    "structured-reflection": {
      "type": "http",
      "url": "https://reasoning.services/tools/structured-reflection/mcp",
      "headers": { "Authorization": "Bearer YOUR_RSVC_API_KEY" }
    },
    "sequential-thinking": {
      "type": "http",
      "url": "https://reasoning.services/tools/sequential-thinking/mcp",
      "headers": { "Authorization": "Bearer YOUR_RSVC_API_KEY" }
    },
    "context-switcher": {
      "type": "http",
      "url": "https://reasoning.services/tools/context-switcher/mcp",
      "headers": { "Authorization": "Bearer YOUR_RSVC_API_KEY" }
    },
    "decision-matrix": {
      "type": "http",
      "url": "https://reasoning.services/tools/decision-matrix/mcp",
      "headers": { "Authorization": "Bearer YOUR_RSVC_API_KEY" }
    }
  }
}

3. Restart Claude Desktop

Quit the app completely and reopen it. Claude Desktop initializes MCP connections at startup — a partial reload is not sufficient.

Connect Claude.ai

Claude.ai supports remote MCP servers via the Connectors UI (requires a Pro or Team plan). No local tooling is needed — the browser connects directly to the hosted server.

Steps

  1. Open claude.ai and navigate to Settings → Connectors.
  2. Click Add connector and enter one of the server URLs above (e.g. https://reasoning.services/tools/context-switcher/mcp).
  3. Claude.ai will open an OAuth authorisation prompt. Approve it to grant access. Your rsvc_ key is used behind the scenes — you do not need to paste it manually.
  4. Repeat for each server you want to enable.

Note: The Connectors UI is separate from the Desktop config file. You can enable the same servers in both environments independently.

Your API Key

Your welcome email contains an API key that starts with rsvc_. This key authenticates every request from your MCP client to our servers.

Using the key

Pass it as a standard HTTP Bearer token in the Authorization header:

bash
Authorization: Bearer rsvc_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Managing your keys

You can create additional keys, revoke compromised ones, and view usage from your account page. Each key is shown only once at creation time — store it in a password manager or secret vault.

Manage API keys in Account →

Keep it secret: Do not commit your key to version control or paste it into shared documents. If a key is exposed, revoke it immediately from the account page and generate a replacement.

Verify the Connection

Once connected, the reasoning tools appear automatically in Claude's tool list — no extra commands needed.

What to look for

  • In Claude Desktop, open a new conversation and click the tools icon. You should see entries for structured-reflection, sequential-thinking, context-switcher, and decision-matrix.
  • In Claude.ai, the connected server names appear in the Connectors panel with a green status indicator.

Test with a simple prompt

Send this to Claude to confirm the tools are reachable:

markdown
Use the context-switcher to analyze this decision from three perspectives:
Should I use a monolith or microservices for a new side project?
If the connection is working, Claude will invoke the tool and return a multi-perspective analysis. If you see an error instead, check that your API key is correct and that your subscription is active.