strateegia-mcp

Remote MCP server that exposes the Strateegia Projects API to MCP clients (Claude.ai, Claude Desktop, Cursor, ChatGPT, etc.).

Runs on Cloudflare Workers. Stateless — the user's Strateegia API key is passed through on every request, never stored.

v1 Tools

Related MCP server: @restforge-dev/mcp-server

Development

npm install
npm run dev

This starts 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. Add an Authorization: Bearer <your_strateegia_api_key> header.

Deploy

npx wrangler deploy

Your MCP server will be available at https://strateegia-mcp.<your-account>.workers.dev/mcp.

Build the .mcpb bundle

npm run mcpb:pack

Output: strateegia.mcpb na raiz do projeto. Pode ser anexado em uma GitHub Release e baixado pelos usuários. Para mudar o Worker URL apontado pelo bundle, edite a entrada em server.mcp_config.args de mcpb/manifest.json antes de empacotar.

Client Configuration

Claude.ai (Web)

Settings > Connectors > Add custom connector:

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

• Add header: Authorization: Bearer <your_strateegia_api_key>

Cursor / Claude Code (mcp.json)

These clients support remote MCP servers with url + headers directly:

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

Claude Desktop — Extensão .mcpb (recomendado)

Instalação sem editar JSON. Ideal para usuário leigo.

1. Baixe o arquivo strateegia.mcpb mais recente (ver Releases ou gere localmente com npm run mcpb:pack)

2. Dê duplo clique — o Claude Desktop abre a tela de instalação

3. Cole sua API key do Strateegia (gere em https://app.strateegia.digital → Configurações → API Keys)

4. Clique em "Instalar". Pronto.

Requer Claude Desktop ≥ 0.10.0.

Claude Desktop — manual (claude_desktop_config.json)

Alternativa sem a extensão. Edite ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) ou %APPDATA%\Claude\claude_desktop_config.json (Windows):

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

Other stdio-only clients

Any client that only supports stdio transport can use the same mcp-remote approach shown above.

Auth Model

The user provides their Strateegia API key (PAT) as a Bearer token. The worker:

1. Extracts Authorization: Bearer <api_key> from each request

2. Rejects with 401 if missing

3. Exchanges the API key for a JWT via POST /users/v1/auth/api

4. Uses the JWT to call the Strateegia Projects API

5. Propagates any 401/403/422/429 errors from the API

No credentials are stored. The JWT is ephemeral — it only exists during the request lifecycle. If the API key is revoked in Strateegia, it stops working here automatically.