chrome extension

C o m m e n t e x a c t l y w h e r e i t h a p p e n s .

pin the object,
not the canvas.

For product teams. Pin feedback to the exact element on your own live app.

Add to Chrome Free
slack sync

It lands in Slack. And Slack lands back.

Search Bim Studio

# bim-2d-feedbacks

Feedback pinned to elements on the live page

CLAUDE & MCP

Claude reads your feedback. And closes it.

Connect Bim to Claude on the web, Claude Desktop or Claude Code. Your agent browses threads, sees the exact element a comment is pinned to, replies and resolves — without opening the extension.

~/bim-website — claude bim · MCP

claude mcp add --transport http --scope user bim https://bim-mcp.vercel.app/mcp

claude mcp list

bim: https://bim-mcp.vercel.app/mcp (HTTP) - ✓ Connected

claude

Welcome to Claude Code!

/help for help, /status for your current setup

cwd: ~/bim-website

Ask Bim
How to install

Three ways in. Take the one you are on.

  1. TEAM · ENTERPRISE

    Claude.ai

    One URL, pasted into Connectors.

    Settings → Connectors → Add, then Custom. An owner adds it once — after that everyone gets a Connect button of their own.

    https://bim-mcp.vercel.app/mcp
  2. FREE · PRO

    Claude Desktop

    One block in the config file.

    Add it to claude_desktop_config.json — ~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows — and restart. mcp-remote does the sign-in in your browser, so there is no token to copy.

    { "mcpServers": { "bim": { "command": "npx", "args": [ "-y", "mcp-remote", "https://bim-mcp.vercel.app/mcp" ] } } }
  3. CLI

    Claude Code

    One command, then /mcp.

    Run it, then type /mcp in a session and sign in. Cursor and Windsurf take the same URL.

    claude mcp add --transport http --scope user bim https://bim-mcp.vercel.app/mcp

You sign in with Google in your browser — there is no token to copy or keep. Access is granted to bim-mcp and to nothing else, and revoking it from the same panel stops it.

how it works

Why it holds up.

A Bim comment pinned to an element, with its reply thread 🐛💡❓✨👏

Pins survive change.

Each comment ties to the element by selector, a text quote, and a structural path, with fallbacks. Re-deploy or re-render, the pin re-finds its spot instead of getting lost.

Bim's composer over the page, sealed off from the host site

Never touches the host site.

Everything lives in a closed shadow DOM. Styles never collide, and the page's JS can't reach your feedback layer.

A Bim comment and its Slack thread, in sync 💡🤔❤️🤔💪🏼💪🏼

Slack, both directions.

Comments post to your channel. Replies come back to the comment. Edits sync both ways.

A comment thread opened from a link, with no account 💡❓✨

Clients, no account.

Share a review link. A client comments under any name they pick, with no signup, scoped to one project.

in practice

We use it on our own work.

Makata built Bim to fix its own review process. We run it on every site we build, for client feedback and internal review.

  • Bim's review panel open next to the Bim landing page, on its empty state: Drop your first pin, Pin to an element, and a Connect Slack button in the footer

01 The panel opens beside the page. / 08

security

What Bim can and cannot see.

How far it reaches, and where it stops.

Chrome will tell you this extension can read the sites you visit. That is true, and it is what makes anchored comments possible at all: the layer runs on your page. Pick a side and see exactly what that means.

And what you can undo.

Delete a comment Any one you wrote, from the panel.
Disconnect Slack From settings, whenever you want.
Delete the whole account On request, at any time.

What it can see.

Ordered from your own machine outwards. Nothing here happens on a site you did not switch on.

  • On your machine storage
    • + Keeps you signed in.
    • + Remembers which sites you switched it on for.
  • On the page you switched on host_permissions: <all_urls> scripting sidePanel
    • + Draws the comment layer on a site after you switch it on: staging, production, behind the login.
    • + Opens the review panel beside the page instead of on top of it.
  • In the two services identity clipboardWrite
    • + Stores comments, accounts and workspace settings with Supabase, which is SOC 2 Type II certified.
    • + Posts to the Slack channel you picked, if you connect Slack.
    • + Copies a review link when you ask for one.

What it cannot see.

The same three places, and what stays out of reach in each one.

  • On your machine
    • − It does not track which pages you visit.
  • On the page you switched on
    • − It does not read the content of your pages.
    • − It does not record clicks or keystrokes outside its own panel.
    • − It does nothing at all on a site you did not switch on.
  • In the two services
    • − It does not sell your data.
    • − It does not pass it to anyone beyond those two.
    • − It never reads your clipboard.
› The Slack permissions we ask for

Only if you connect Slack. Bim does not ask for permission to create or archive channels, and cannot read a channel it was not added to.

  • chat:write — Posts your team's comments into the channel you picked.
  • channels:read, groups:read — Lists your channels so you can pick one. Names only.
  • channels:join — Lets Bim join the channel you picked, so posting works without you inviting it by hand.
  • users:read — Resolves a Slack display name when someone replies from Slack.
  • emoji:read — Renders your workspace's custom emoji on a reply.
  • files:read — Brings an image attached in Slack back onto the comment.
Read the full privacy policy

Pin it. Say it. Bim it.

Add to Chrome Free