Claude MCP Connector (Draft)

How a Claude MCP connector would point at the local tool server. Draft only, nothing published.

Status: draft, internal. No app, plugin, connector or extension has been submitted to ChatGPT, Claude, the Chrome Web Store, the Apple App Store, Google Play or any other marketplace, and none has been approved. The web app is the product; everything on this page is a distribution experiment that is not live.

Where this stands

The MCP tool server is the connector target, so no separate build is needed. What is missing is the part that makes it reachable and safe to reach: a public transport, authentication, rate limiting, and an owner decision about customer data leaving the server.

Nothing has been listed, published or submitted for review.

Local use today

An MCP client running on this host can call the server directly over loopback. That is genuinely useful for internal agents and for testing tool behaviour, and it is where the capability stops until the owner decides otherwise.

Tool server details

Blockers

Owner approval for any public connector.
Public transport with authentication and rate limiting.
Privacy policy covering third-party AI processing of quote text.
Domain and support address.

Customer data rule

Contractor quotes contain names, addresses, phone numbers and prices. No customer data should be sent through an AI app, plugin or connector until a privacy policy and account terms covering that data flow have been reviewed and approved. That is why the tool server currently binds to loopback and has no public route: it cannot leak what it cannot receive.

Related: legal drafts

Educational document review only. Not legal, engineering, pricing, contractor-vetting, or building-code advice. Nothing here has been submitted to or approved by any app marketplace.