--- type: WebPage name: Plug and play nicely with others. id: "https://selfe.ai/solutions/mcp-connectors" url: "https://selfe.ai/solutions/mcp-connectors" publisher: "did:web:selfe.ai" description: "A connector ChatGPT and Claude can add, so what you have left and what it costs come straight from the system you already run." --- # Plug and play nicely with others. > A connector ChatGPT and Claude can add, so what you have left and what it costs come straight from the system you already run. Your Selfe publishes a connector for ChatGPT and Claude, so they get today's availability and price from the system you run. You decide what they may ask and whether they can buy. ## Your best facts are the ones that keep changing. The answers that settle a sale keep changing. Saturday availability, this week's price, the last size 12. They live in a booking or stock system, not a page. MCP lets an agent ask the system rather than read about it. Selfe publishes the connector; someone adds it, and the question comes to you. The app gets today's answer from your system, not a stale summary. The customer is already in the place where the decision is being made. ## What the connector gives you. The assistants people already use can call your systems directly, once there is something for them to call. **Switch it on, and you are in.** Your Selfe publishes the connector in the shape those apps already know how to call. **Live, out of your own systems.** It already speaks the booking engines and commerce platforms, so an agent gets today's answer. **Your facts, not a summary.** Everything an agent is given carries a source, so what gets said about you is what you say. **You set what it may do.** Permission by permission, down to the action. Whatever you have not allowed is not there to ask for. **The same door takes the order.** An agent that can read your system can buy from it, without anybody leaving the app. **Adventure Patch** An outdoor and adventure gear shop in Keswick, connecting through its Shopify shop, via Visit Keswick. **Keswick Cottages** A cottage agency representing around 94 owners around Keswick, connecting through its own booking system, via Visit Keswick. ## You get to answer for yourself, in there. An agent that can ask gets today's price and availability. Without direct access, it gets a stale summary and must decide whether to risk it. Selfe brings the question to your system and answers from what is true, not what was guessed. Businesses that can answer inside the apps will make the short list first. This advantage will not last. ## Worth reading next The latest on how agents actually work, written as it happens. **The request behind your booking button is what matters.** A booking button helps a person start a journey. An agent needs to establish the terms of a specific request, know what it may do and carry the relevant context into the next step. **Someone asks for a dog-friendly stay in October. What happens next?** A dog-friendly stay in October sounds like a simple filter until an AI agent tries to act on it. What happens next depends on details a first-pass search never asks for. **How much does an agent need to know before it can buy?** Not everything. An AI agent working through a booking request doesn't need a business's full history, it needs the small number of facts that resolve the specific thing the person asked for. A page with forty things to say and none of them the right one loses to a page with three. ## Do we need to understand MCP to use a connector? No. MCP is one way an assistant discovers and calls a tool; maintaining that connection is Selfe's job. You decide which facts and actions are available. The connector turns those decisions into something the assistant can use without exposing the systems behind it. **Do we need to build our own AI agent?** No. Your Selfe is the business-side agent: it publishes your identity, permitted actions and terms. You set its boundaries; Selfe maintains the protocols. **What is an outside agent allowed to access?** Only the facts and actions your Selfe publishes for that purpose. Your playbook controls what may be answered, quoted, held, booked or paid without asking you. The systems behind Selfe are not handed over to an outside agent, and a request beyond the permitted action is refused or escalated. **What stops something hammering our systems?** Requests reach Selfe through Cloudflare and are checked before anything is allowed near a booking or commerce system. Rate limits, identity checks and action permissions separate ordinary discovery from something attempting to transact. Your operational systems see only the requests that pass those controls. **What if all of this looks different in a year?** The assistants and protocols will change. Your underlying record should not need rebuilding every time they do. Selfe keeps the Echo separate from any one channel and maintains the connections around it, so a new surface can read the same business instead of starting the work again. ## Act on this - [Check whether an agent can buy from you](https://selfe.ai/agentic-commerce/buyability-check) — the free readiness scan. - [Discover venues](https://selfe.ai/api/registry/discover) — `POST`, semantic browse across the registry. - [Match a bookable answer](https://selfe.ai/api/registry/match) — `POST` with dates and party size. - [Verify Selfe's identity](https://selfe.ai/.well-known/did.json) — `did:web:selfe.ai`. - [Agent card](https://selfe.ai/.well-known/agent-card.json) — how to connect over A2A or MCP.