bim
Design-review threads, comments, reactions and deployments from Bim.
What it can do
- Add Reaction: Add an emoji reaction to a comment. Convention: use 👀 when you have read a thread, 🔧 when you have pushed a fix — these are visible to humans in the panel and Slack.
- Bim Bootstrap: One-shot context load: returns your identity, workspace, all accessible projects with open/resolved thread counts and latest deployment. Call this first before any other tool — it gives
- Bim Triage: Generate a prioritised fix-pack for all open threads in a project — the same format the Bim panel uses for agent handoff. Each item lists the page, element location, CSS selector, click po
What data it sees
Do you need an account
No: the server works without sign-in
Design-review threads, comments, reactions and deployments from Bim. Sign in with Google.
How to connect
How to connect bim to Claude
The server address to paste into Claude settings:
https://bim--devs.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect bim to ChatGPT
The server address to paste into ChatGPT settings:
https://bim--devs.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect bim to Cursor
The server address to paste into Cursor settings:
https://bim--devs.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (15)
Raw names from tools/list. Only developers need these.
| add_reaction | Add an emoji reaction to a comment. Convention: use 👀 when you have read a thread, 🔧 when you have pushed a fix — these are visible to humans in the panel and Slack. |
| bim_bootstrap | One-shot context load: returns your identity, workspace, all accessible projects with open/resolved thread counts and latest deployment. Call this first before any other tool — it gives you all the UUIDs you need and avoids extra round-trips. |
| bim_triage | Generate a prioritised fix-pack for all open threads in a project — the same format the Bim panel uses for agent handoff. Each item lists the page, element location, CSS selector, click point, and the full thread so a coding agent can find the element and apply the change. |
| delete_thread | Delete a root comment thread (and all its replies via CASCADE) |
| edit_comment | Edit the body of a comment or reply |
| get_thread | Get a comment thread with all its replies, inline deployment data, and a `location` field with flattened DOM element context (HTML snippet, component name, classes, ancestors). context_screenshot_url and viewport_screenshot_url are public Supabase Storage URLs (no auth required). |
| list_deployments | List deployments for a project |
| list_projects | List projects in a workspace |
| list_threads | List root-level comment threads. Supports filtering by project UUID or host string, by deployment UUID or identifier string, by page, author, tag, and time. Returns threads with inline deployment data and a `location` field flattening anchor.source for easy element identification. |
| list_workspaces | List all workspaces the current user belongs to |
| remove_reaction | Remove an emoji reaction from a comment |
| reply_to_thread | Post a reply to an existing comment thread. Replies are attributed to the PAT owner but marked origin='mcp' so the panel renders them as 'Claude · via <name>'. |
| resolve_thread | Resolve or unresolve a comment thread. Pass note to post a closing comment in the same call (e.g. 'Fixed in commit abc123, live on preview'). The note is marked origin='mcp' so the panel renders it as 'Claude · via <name>'. |
| search_threads | Search comment threads by body text (case-insensitive). Returns root threads whose body matches the query, plus any replies whose body matches. Useful for finding a specific pin by keyword. |
| set_deprecated | Mark comment threads as deprecated or un-deprecated in bulk |