Entity Bind and Claude Desktop

1. 01

   Local stdio, for a developer evaluating

   The client launches the process and talks to it over pipes. The config holds database credentials directly, so this route belongs on a machine whose operator already has them. It serves one configured tenant and nothing else, at the Scale plan, and every call is metered against the key id mcp_stdio, so an evaluation on a laptop never arrives in a usage export looking like customer traffic. The module path and the environment variable names below are the engine package's own, verbatim: the process reads exactly those strings, which is why they carry the engine's name rather than the product's.

   Local stdio, for a developer evaluating

   {
     "mcpServers": {
       "entitybind": {
         "command": "uv",
         "args": ["run", "python", "-m", "resolvd.mcpserver"],
         "env": {
           "RESOLVD_DATABASE_URL": "postgresql+asyncpg://user@localhost/dbname",
           "RESOLVD_MCP_TENANT_ID": "ten_acme",
           "RESOLVD_ANTHROPIC_API_KEY": "sk-ant-..."
         }
       }
     }
   }

2. 02

   Remote connector, for everybody else

   Three actors in a fixed order. We register the connector once against your client's exact redirect URI — matched by exact string equality, so a trailing slash is a different URI and a wildcard is refused. Your tenant administrator then mints a single-use install ticket with an admin-scoped key; it appears in that response and nowhere else, works once, and expires in fifteen minutes. The person installing pastes the server URL into the client, the client runs the authorisation-code flow, and the consent page asks for the ticket.

   Remote connector, for everybody else

   # 2. A tenant administrator mints the single-use install ticket:
   curl -sX POST "$BASE/v1/admin/oauth/install-tickets" \
     -H "Authorization: Bearer $ADMIN_KEY" \
     -H 'Content-Type: application/json' \
     -d '{"tenant_id":"ten_acme"}'
   
   # 3. The person pastes the server URL into the client. PKCE is required and
   #    S256 only; plain is refused permanently. Every client is public — there
   #    is no client_secret and no field for one.

3. 03

   Know what the ticket authorises

   A tenant, not a person. The OAuth flow carries no end-user identity — no users, no passwords, no sessions and no upstream identity provider behind the consent page — so there is nobody for the authorisation server to authenticate at the consent step. Anyone holding a ticket authorises as that tenant, and the audit trail records which admin key minted it rather than who used it. Design the install around that. It is also why a ticket works once and expires quickly.

4. 04

   Tell the agent what an abstention is

   Put two things in the agent's own instructions before it calls anything. An abstention is a successful answer rather than an error: the tool returns a ranked shortlist, a typed reason, the column that would have decided, and a review id, and it costs nothing. And a confidence number is read against the recorded evidence behind that particular decision, not as a universal score. Confidence bounds depend on the recorded evidence population; there is no universal score for every match. Read match_confidence_basis and the evidence. A 0.99 filter can return some v8 adjudicated matches while excluding valid identifier matches, so validate its coverage cost on your own inputs.

Claude Desktop sits with Claude Code and Cursor on the same shelf: configure and call. If you are weighing a shipped integration against a pattern, the line between the two shelves is drawn on the hub.