strateegia-mcp
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
Tool | Description |
| List user's projects (paginated) |
| Full project details with members and maps |
| Create a project in a lab |
| List journey maps in a project |
| Full map with all points and structure |
| Collect ideas/responses (brainstorming) |
| Group decision-making via polls |
| Long-form text with optional peer evaluation |
| Track qualitative or quantitative progress |
| Add a response to a divergence question |
| Like (curtir) a response in a divergence point |
| Remove a previously given like on a response |
| Reply to an existing response (nested comment) |
Development
npm install
npm run devThis starts Wrangler dev server at http://localhost:8787. The MCP endpoint is /mcp.
Testing with MCP Inspector
npx @modelcontextprotocol/inspectorEnter http://localhost:8787/mcp as the server URL. Add an Authorization: Bearer <your_strateegia_api_key> header.
Deploy
npx wrangler deployYour MCP server will be available at https://strateegia-mcp.<your-account>.workers.dev/mcp.
Build the .mcpb bundle
npm run mcpb:packOutput: 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/mcpAdd 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.
Baixe o arquivo
strateegia.mcpbmais recente (ver Releases ou gere localmente comnpm run mcpb:pack)Dê duplo clique — o Claude Desktop abre a tela de instalação
Cole sua API key do Strateegia (gere em https://app.strateegia.digital → Configurações → API Keys)
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:
Extracts
Authorization: Bearer <api_key>from each requestRejects with 401 if missing
Exchanges the API key for a JWT via
POST /users/v1/auth/apiUses the JWT to call the Strateegia Projects API
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.