strateegia-mcp

Remote MCP server that exposes the Strateegia Projects API to MCP clients (Claude, Claude Desktop, Claude Code, Cursor, and others).

Runs on Cloudflare Workers and implements MCP spec 2026-07-28: stateless, no sessions, no handshake. Clients on the 2025 protocol (including the mcp-remote bridge) are still served. The user's Strateegia API key is passed on every request and never stored.

Services inside the Strateegia platform can send the user's session JWT instead of an API key (Authorization: Bearer <jwt>); the server uses it directly and skips the key exchange.

Tools

Every tool declares risk annotations (read-only, additive, reversible or overwrite), and failures come back with isError: true. No tool deletes anything.

Related MCP server: Context Weaver

Development

npm install
npm run dev

This starts the Wrangler dev server at http://localhost:8787. The MCP endpoint is /mcp.

Testing with MCP Inspector

npx @modelcontextprotocol/inspector

Enter http://localhost:8787/mcp as the server URL and add the header Authorization: Bearer <your_strateegia_api_key>.

Deploy

The worker reads the Strateegia API root from the STRATEEGIA_API_URL var in wrangler.jsonc. npm run deploy publishes strateegia-mcp against production; npm run deploy:dev publishes a separate strateegia-mcp-dev worker against https://api.dev.strateegia.digital. For local work against dev, use npm run dev:env-dev.

npm run deploy

Wrangler authenticates with CLOUDFLARE_API_TOKEN when it is set (it also reads it from .env); otherwise it falls back to npx wrangler login. The server is served at https://strateegia-mcp.<your-account>.workers.dev/mcp.

Build the .mcpb bundle

npm run bundler

Output: strateegia.mcpb at the project root, ready to attach to a GitHub Release. The bundle is a thin mcp-remote bridge pointing at the deployed Worker, so it only needs rebuilding when mcpb/manifest.json or the mcp-remote version changes, not when tools change. To point it at another Worker, edit server.mcp_config.args in mcpb/manifest.json.

Client configuration

Get an API key at https://app.strateegia.digital (Configurações > API Keys). Treat it like a password.

Claude (web, desktop and mobile): custom connector

This connects straight over HTTP, with no local process, and works everywhere you use Claude. It needs the Request headers option in the connector dialog, which is in beta and not yet enabled for every organization. If you don't see it, use one of the Claude Desktop options below.

Customize > Connectors > Add custom connector:

• MCP server URL: https://strateegia-mcp.<your-account>.workers.dev/mcp

• Authentication: No sign-in

• Request headers: name authorization, value Bearer <your_strateegia_api_key> (include the word Bearer and the space; Claude sends the value exactly as typed)

Claude Desktop: .mcpb extension

No JSON editing, suited to non-technical users.

1. Download the latest strateegia.mcpb (see Releases, or build it with npm run bundler)

2. Double-click it; Claude Desktop opens the install screen

3. Paste your Strateegia API key

4. Click Install

Claude Desktop: manual (claude_desktop_config.json)

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows). claude_desktop_config.json launches local processes, so mcp-remote acts as the bridge to the remote server:

{
  "mcpServers": {
    "strateegia": {
      "command": "npx",
      "args": [
        "mcp-remote@0.14.3",
        "https://strateegia-mcp.<your-account>.workers.dev/mcp",
        "--header",
        "Authorization: Bearer <your_strateegia_api_key>"
      ]
    }
  }
}

Claude Code / Cursor (mcp.json)

These clients connect to remote servers directly with url and headers (Claude Code needs "type": "http"; Cursor infers it from url):

{
  "mcpServers": {
    "strateegia": {
      "type": "http",
      "url": "https://strateegia-mcp.<your-account>.workers.dev/mcp",
      "headers": {
        "Authorization": "Bearer <your_strateegia_api_key>"
      }
    }
  }
}

Other stdio-only clients

Use the same mcp-remote bridge shown in the Claude Desktop manual setup.

Auth model

The user's Strateegia API key (PAT) is sent as a Bearer token. On every request the Worker:

1. Reads Authorization: Bearer <api_key>

2. Exchanges the key for a short-lived JWT via POST /users/v1/auth/api

3. Passes the JWT to the tools, which call the Strateegia Projects API with it

4. Propagates API errors to the model as tool errors (isError: true)

This server does not use OAuth. Failed authentication is answered so that clients stop instead of going looking for OAuth:

The 403 is deliberate: on any 401, mcp-remote starts an OAuth flow, fails at client registration and hides the real cause. No credentials are stored, and a key revoked in Strateegia stops working here immediately.