Platform

Agent Access (MCP Server)

Your firm's knowledge, in every AI tool your team uses. Connect Claude, Cursor, Gemini, Codex, or any MCP-capable AI assistant directly to your firm's BIM Monkey account — your drawing library, firm standards, code-compliance history, and firm memory. Your staff asks questions in the tools they already work in; the answers come from your own projects.

Included with every plan. Agent Access is part of every BIM Monkey subscription at mcp.bimmonkey.ai — authenticated with your firm's API key, honoring your data residency and Private AI configuration. See plans.

What it is

Agent Access is a hosted MCP server — the open protocol AI assistants use to call external tools. Add BIM Monkey as a connector and every conversation your team has with their AI assistant can pull real answers from your firm's account, mid-thought:

"Have we detailed a roof eave with exposed knee braces before? Which sheet?"
"What did the last code check on 1710 NE 70th say about egress?"
"How does this firm label kitchen appliances?"
"Remember that this client always wants standing-seam metal roofing."

No code, no integration project — a URL and an API key.

Available tools

Tool	What the agent gets
get_account_capabilities	Plan tier, Private AI provider and entitled Claude models, data residency state.
query_library	Every uploaded CD set — sheet counts, building types, upload dates.
get_project	One project's full sheet breakdown — numbers, titles, scales, notes, catalogued details.
search_details	Search the firm's detail library across all projects — by type, description, or key elements.
get_firm_standards	The firm's synthesized drawing-standards document.
get_firm_memory	Standing rules and conventions saved from Banana Chat sessions.
add_firm_memory	Save a new standing rule — additive, audited, attributed to agent access.
get_compliance_runs	IBC code-compliance audit history, down to individual check results and narratives.
get_sheet_image	The actual drawing — any sheet from the firm's library, rendered in the chat with a secure expiring view link. Served from the firm's own storage bucket under data residency.
add_project_todo / get_project_todos	Field-captured tasks — save a to-do from a site visit or client call; it lands on the project, waiting at your desk.

Connect

Your firm's API key is in app.bimmonkey.ai → Settings. It starts with bm_.

Claude (web, desktop & mobile apps)

Go to claude.ai → Settings → Connectors → Add custom connector and enter https://mcp.bimmonkey.ai/mcp. You'll be taken to a BIM Monkey authorization page — paste your firm's API key once and approve. The connector syncs to the Claude mobile apps automatically, so your firm's library, standards, and compliance history are available from your phone. Access uses secure rotating tokens; rotating your API key revokes all connected agents instantly.

Claude Code

claude mcp add --transport http bimmonkey https://mcp.bimmonkey.ai/mcp \
  --header "Authorization: Bearer bm_YOUR_KEY"

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "bim-monkey": {
      "url": "https://mcp.bimmonkey.ai/mcp",
      "headers": { "Authorization": "Bearer bm_YOUR_KEY" }
    }
  }
}

Gemini CLI

Add to ~/.gemini/settings.json:

{
  "mcpServers": {
    "bim-monkey": {
      "httpUrl": "https://mcp.bimmonkey.ai/mcp",
      "headers": { "Authorization": "Bearer bm_YOUR_KEY" }
    }
  }
}

VS Code (GitHub Copilot)

Add to .vscode/mcp.json in your workspace:

{
  "servers": {
    "bim-monkey": {
      "type": "http",
      "url": "https://mcp.bimmonkey.ai/mcp",
      "headers": { "Authorization": "Bearer bm_YOUR_KEY" }
    }
  }
}

Everything else

MCP is a vendor-neutral standard, so the same two values work in any MCP-capable client — endpoint https://mcp.bimmonkey.ai/mcp, header Authorization: Bearer bm_YOUR_KEY:

OpenAI Codex — add an MCP server entry in ~/.codex/config.toml with the endpoint URL and Authorization header (syntax varies by version; see OpenAI's MCP docs).
Antigravity / Windsurf — add a remote MCP server from the MCP settings panel with the same URL and header.
Enterprise copilots & agent frameworks — any client or SDK that speaks MCP Streamable HTTP with custom headers connects the same way.

BIM Monkey supports OAuth 2.1 with dynamic client registration, so OAuth-based connector directories (like claude.ai's, above) work out of the box. And because MCP is the industry standard, when a vendor adds MCP support their client works with BIM Monkey on day one, with no change on our side.

Security posture

Per-firm authentication — every request carries your firm's key; agents see only your firm's data. No key, no answer.
Honors your infrastructure choices — if your firm runs data residency, agent queries read from your database. Inference triggered under Private AI runs in your cloud.
Read-mostly by design — the only write is firm memory, which is additive, audited, and attributed to agent access. Agents can never modify a Revit model, your library, or your standards through this surface.
Rate-limited and logged — every call is metered per firm with tool, timing, and client identity.
Revocable instantly — rotate your API key and every connected agent loses access, including OAuth-connected apps.
Know the boundary — BIM Monkey's side runs in your infrastructure: your database, your cloud inference under Private AI. The AI assistant you connect processes the data it retrieves under your firm's agreement with that vendor — connect assistants your firm has approved.
Plan-aware server-side enforcement — every request re-checks the firm's current plan, and access ends immediately on cancellation.

Questions

Email [email protected]. Looking for the REST API for software integrations instead? See the API reference.