MCP for businesses
A business can connect its own MCP client — a chat assistant, a copilot, an internal tool — to MasterDB to prepare its records and see how they are doing. Sealed, or not published holds on every transport: nothing reaches AI companies through MCP without a person’s passkey.
The hosted server
Section titled “The hosted server”POST https://mcp.business.masterdb.ai/v1/mcp/business, over MCP’s Streamable HTTP transport, signed in as a person of the business — the same sign-in as the Business Portal, with the same roles.
| Tool | Does |
|---|---|
draft |
creates or edits a draft and validates it, with every reason at once |
publish |
validates the draft, shows the change since the last publish, and returns a link to the Business Portal’s save screen — where the person reviews it and seals it with their passkey. The server never seals. |
status |
your drafts, what is published, and where each record is live |
receipts_for_my_records |
your publish receipts, and which AI companies are asking |
Every call runs under the person’s own permissions. This server can never seal, spend, change people, place or lift a block, or change keys: those stay in the portal, behind a passkey.
Sessions work as on the AI companies’ hosted servers: an Mcp-Session-Id from initialize, 30 minutes idle, DELETE to end one. The endpoint is in the reference.
Machine publishing
Section titled “Machine publishing”A business whose own systems publish uses an integration key under a mandate, exactly as any connector does: see Pushes and mandates.