MCP server
MCP server overview
Brunel's Model Context Protocol server lets AI agents like Claude Code, Cursor, VS Code and Windsurf analyze repositories, design priced infrastructure and fetch Terraform as tools.
Brunel speaks the Model Context Protocol: any MCP client can use Brunel's tools, with an API key.
Connection
| URL | https://api.brunel.cloud/mcp (also https://brunel.cloud/api/mcp) |
| Transport | Streamable HTTP, stateless: every POST gets one JSON answer, no session, no event stream |
| Authentication | Authorization: Bearer <API key> on every request |
| Protocol | JSON-RPC 2.0 |
Protocol versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05. The server answers with the version the client asks for when it knows it, else the newest.
Tools
| Tool | Does |
|---|---|
whoami | The account behind the key: login, plan and key scope |
list_projects | Your projects, most recent first |
analyze_repository | Read a repository: facts with evidence, services, security check, suggested context |
design_infrastructure | Four priced tiers, with an optional context |
get_architecture | A project's state and its tiers |
refine_architecture | Ask a question or request a change |
get_files | The generated files of a tier, or one file's content |
Full parameters: Tool reference. Read-only keys can call the read-only tools.
The flow agents follow
The server tells clients how to use it: analyze_repository → design_infrastructure (optionally adjusting budget, traffic, compliance or provider) → get_architecture / refine_architecture → get_files for Terraform and CI. Prices are euros per month from official catalogs; agents are told to quote them as estimates and link the project.
Try it by hand
curl -s https://api.brunel.cloud/mcp \
-H "Authorization: Bearer $BRUNEL_API_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'The console's MCP server page has a playground with history, timing and explained errors.
Metering
Every tool call is recorded in your request logs with the tool name, and counts against your plan like the app. A tool error is still an HTTP 200 in MCP; the log records its real status.