A typed set of tools over the buyer’s own live business database, connected to their chat client as a custom connector, so staff ask questions and create records in plain language instead of opening the application. Authentication is solved properly: directory OAuth with protected-resource metadata, plus an API-key scheme side by side for desktop and CLI clients.
What ports as-is
- The MCP host inside an existing .NET API
- Dual auth schemes
- Protected-resource metadata
- The forwarded-protocol fix that makes the challenge work behind a shared reverse proxy
- The documented directory resource-parameter fix
- The interactive-form write pattern where the model may only produce a draft and a UI resource inside the chat client performs the single write
- One shared query layer used identically by connector
- In-app chat and automations
- Fuzzy name resolution
Tool families already written: scheduling, member and contract, tax figures, vouchers, contact revenue, liquidity, invoice creation, work time and billing.
What we build for you
- The tool set itself over that customer's schema
- Worded in the office's own vocabulary including domain terms in their language
- The app registration and verified custom domain for the OAuth path
- Key issuance
- The connector entry in their client
- Pointing it at staging first
