--- type: Article name: "\"We've set up MCP, so we're agent-ready.\" That covers your own team's tools. It's a different job from the one a stranger's agent needs done." id: "https://selfe.ai/insights/myth-vs-fact/weve-set-up-mcp-so-were-agent-ready" url: "https://selfe.ai/insights/myth-vs-fact/weve-set-up-mcp-so-were-agent-ready" publisher: "did:web:selfe.ai" description: "MCP is genuinely useful, just not for the case most businesses think it covers. It's strong for an operator's own tools, a chat assistant working against your booking system, less so for a stranger's AI agent trying to book or buy from you. Both are real, but only one of them is what \"agent-ready\" usually means." datePublished: "2026-09-15T15:35:35.873Z" author: The Selfe team --- # "We've set up MCP, so we're agent-ready." That covers your own team's tools. It's a different job from the one a stranger's agent needs done. > MCP is genuinely useful, just not for the case most businesses think it covers. It's strong for an operator's own tools, a chat assistant working against your booking system, less so for a stranger's AI agent trying to book or buy from you. Both are real, but only one of them is what "agent-ready" usually means. ## In short - MCP is genuinely strong for an operator's own tools, an assistant working against your own PMS or storefront systems. - It's weaker for the consumer-facing case: a stranger's agent trying to book or buy from a business it's never dealt with. - The consumer case needs identity, spending authorisation and a completed transaction too, none of which MCP alone provides. - Selfe covers the full chain a stranger's agent needs, not just the connection layer. Genuinely useful and genuinely incomplete aren't in tension. MCP is both at once, depending which question you're asking it. ## What that setup is good at A hotel group's operations manager sets up an AI assistant that can query the property-management system directly: tonight's occupancy, tomorrow's arrivals, which rooms need turning around. It's genuinely useful, built on the same connection protocol, MCP, that a lot of the industry talk about "agent-readiness" refers to. The team reasonably concludes the box is ticked. It isn't, not for the thing most of that talk is about. An assistant querying a property-management system directly, or any internal tool, is a real, working use of the same connection layer: an operator's own assistant calling into the operator's own systems. It's backwards-facing in the sense that matters, a member of staff using AI to work faster against tools they already run. That's a genuinely strong use of the technology, and it exists today. ## What it doesn't cover A stranger's agent, working on behalf of a guest who's never dealt with this hotel before, trying to check availability and book a room, needs something different. It needs to prove who it is, prove it's allowed to spend on the guest's behalf, and complete a transaction the hotel can settle, none of which the connection layer alone provides. Having MCP wired up to your own PMS tells you nothing about whether that separate, harder chain is in place. ## The two cases, side by side One is a person on your own team, using an assistant as a better interface to systems you already run. The other is a person who's never heard of you, whose agent needs to arrive, prove itself, get authorised, and complete a purchase, all without a human on your side doing anything by hand. The connection protocol is genuinely shared between both cases. Almost everything else about them isn't. MCP itself isn't a human-shaped tool the way a page or a chat widget is, it's real infrastructure, doing a real job. The mistake here is the same incompleteness behind every other myth in this hub, just from a different angle: one working piece mistaken for the whole system. ## Where this shows up for a business Selfe covers the identity, authorisation and checkout layers a stranger's agent needs, the parts MCP alone was never built to handle, alongside the connection itself. This site's protocols hub, starting with "The plumbing behind every agent purchase," covers each piece properly. ## So is MCP a waste of effort? No, it's genuinely useful for internal tooling. It's just answering a different question than "can a stranger's agent book from us." ## What's missing for the consumer case? Proof of who the agent is, proof it's allowed to spend, and a way to complete the transaction, covered properly in this site's protocols hub. ## 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.