Skip to main content

Connecting Claude (MCP)

Cobblr ships an MCP server, so you can connect your own Claude (Claude Code, Claude Desktop, or a claude.ai connector) to your workspace and work on it by talking.

What Claude can do​

Once connected, Claude works through the same API the app uses, and the same tool set the in-app assistant uses, so what your Claude can do and what Cobb can do stay in step:

  • Read your workspace: list the kinds of record you hold and their fields, list and read records, search across every kind at once, and follow the links between records.
  • Write your workspace: create a record, update fields on one, delete one, and run an action such as adjusting stock, marking a task done, or printing a label. Workspace settings like label-code prefixes go through the action tool too.
  • Build: validate and install a bundle, or draft a new one from a description for you to review and apply.

A kind is creatable, updatable, or deletable only where its module declares that route, so Claude gets a clear "can't do that here" rather than a surprise failure. Every call is permission-checked on the server against your token's own role, and writes go through Claude's own per-tool approval prompts on your side.

Driving and watching your screen​

Claude can also share your screen session, with your permission. Once a tab is granted, it can:

  • Open pages in your window. "Let me show you the low-stock view" and the view appears in your tab.
  • Point at things. A visible cursor (with an optional label) shows exactly where Claude means, so "click here" comes with a here.
  • Follow along, if you allow it. Claude sees the clicks and page changes you make in that tab, so it can help with what you're actually doing instead of guessing.

Driving is permissioned separately from the connection itself, in three independent layers:

  1. Its own token scope. Browser driving is a distinct capability a token can carry, and a token scoped to just driving can never read or write workspace data. You choose whether Claude's token can drive, touch data, or both.
  2. A standing per-workspace switch, off by default, with two on-levels: navigate only, or navigate plus observe. It's re-checked on every call, so flipping it off cuts Claude off immediately.
  3. A per-session tab pick. Claude asks, your open tabs show a prompt, and you tap "use this window" in the one it may drive.

It's a shared session, not a takeover: you keep using the tab normally the whole time.

Your Claude, not ours​

The MCP server is a thin, authenticated face over the REST API; Cobblr adds no AI middleman. Claude runs on your machine and your subscription, which is what makes this fine under Anthropic's consumer terms, and it works the same against a self-hosted install.