What agents see
When an AI assistant discovers your endpoint and connects to it, here’s exactly what it finds — the tools available, what each one does, and what the data looks like from the agent’s perspective. No technical background required.
The endpoint, plain language
Your endpoint is a small server that lives at mcp.yourdomain.com. It speaks a protocol called MCP (Model Context Protocol) — the same standard used by ChatGPT, Claude, Gemini, Microsoft Copilot, and others. When an AI assistant asks it for information, it responds in a structured format the AI can read and reason with.
The endpoint only serves published data. Anything in your profile marked as draft — or anything you haven’t published — is never exposed to agents. You control the source of truth.
The tools list
Agents start by asking your endpoint what it can do. The endpoint responds with a list of available tools. Each tool is a specific action the agent can take. Your endpoint exposes up to five tools:
get_business_profile
Returns your complete structured profile: services with pricing, hours, service areas, booking process, policies, credentials, FAQs, and contact information. Agents are instructed to call this first. It’s the foundation — one call that gives the agent everything it needs to answer most questions about your business.
search_business_info
Searches your published website content (the text we ingested during setup) for specific details not covered by the profile. Useful for agents asking about something specific — a particular product, a page you referenced in your FAQ, a detail from your About page.
submit_inquiry
Submits a contact inquiry to your business on behalf of the user. The agent collects the customer’s name, message, and optionally their email or phone, then sends the inquiry through the endpoint. It appears in your dashboard immediately.
request_callback
Requests a phone callback from your business. The agent collects the customer’s name, phone number, preferred callback time, and topic. You receive it in your dashboard with everything you need to call them back.
request_quote
Requests a project quote. The agent collects the customer’s name, contact information, and project details (scope, location, timing). You receive a structured quote request in your dashboard.
What agents cannot do
- Access any data you haven’t published
- Change your profile or any business data
- Book appointments directly (booking requests go to your dashboard; you confirm)
- Access financial information, payment methods, or internal systems
- See draft content or unpublished profile fields
Sample conversation: the full call flow
Here’s what a full agent interaction looks like — from a customer asking for help through to a lead landing in your dashboard. The agent is Claude; the business is a fictional plumbing company.
Sample agent conversation
Can you find a plumber near Austin, TX who handles emergency work and book me a callback for this afternoon?
Let me check what I can find with an active endpoint in that area.
[calls get_business_profile on Green Valley Plumbing’s endpoint]
I found Green Valley Plumbing — they cover the Austin 78704–78745 zip range and run a 24/7 emergency line including weekends. Emergency pipe repair is $145/hr with a $65 after-hours dispatch fee. They’re licensed and insured, and they specialize in older home plumbing (pre-1970 systems).
To book you a callback I’ll need your name and phone number. What’s a good time this afternoon?
Maria Reyes, 512-555-0182. Anytime after 2 pm works.
[calls request_callback: name=“Maria Reyes”, phone=“512-555-0182”, preferredTime=“after 2 pm today”, topic=“emergency plumbing — pipe repair”]
Done. I’ve submitted a callback request to Green Valley Plumbing for Maria Reyes at 512-555-0182, after 2 pm. They typically respond within the hour for emergency requests.
At this point, the callback request appears in the business dashboard with Maria’s name, number, preferred time, and topic. The business owner calls her back. The conversation between Maria and her AI assistant is complete — she never had to search, click, or dial.
The resource document
In addition to tools, your endpoint exposes one resource: a Markdown document at the URI maap://business/your-slug/profile. Some agents prefer to read structured documents rather than call tools. This resource provides the same profile data in a readable Markdown format — same content, different access pattern.
What the discovery document looks like
Agents that check your domain for MCP endpoints look for https://mcp.yourdomain.com/.well-known/mcp.json. If they find it, they know your endpoint is live and how to connect. The file contains your endpoint address and server name. You don’t need to manage this file — it’s generated and served automatically.
Next: Agency portal guide → or Endpoint reference (technical) →