GEO-300 · Lesson 8 of 12 · Module 3: Ready for Agents · 2:59
APIs and MCP for brands
Assistants and agents can call you directly. Expose one source of truth as an API: an OpenAPI description, read-only endpoints for facts such as price, stock, hours and specs, and the same data your pages show. The Model Context Protocol (MCP) standardises how an assistant connects: a server offers tools and resources over Streamable HTTP, with OAuth 2.1 for anything personal, and consent before any action. Rate-limit, log and version it, and keep it in sync with the site, because two sources of truth make two different answers. App directories are built on MCP servers (as of October 2026, ChatGPT's plugin directory, which replaced its app directory in July 2026); treat their rules as dated.

What you will learn
- Describe your facts as an API
- Build an MCP server with tools and resources
- Keep the API, the pages and the data in sync
The one thing to remember
One truth, many doors.
Common mistake: A stock API that says "in stock" while the page says "sold out"
Two sources of truth give two answers, and the assistant trusts neither.
The fix: Pages and API read the same record; a test compares them on every deploy.
Key terms
- Source of truth
- The one place a fact is stored; pages and APIs both read from it.
- OpenAPI description
- A machine-readable file that describes your endpoints, inputs and outputs.
- MCP server
- A service that exposes tools and resources to AI applications over the Model Context Protocol.
- Tool
- An MCP function an assistant can call, with a schema and a description.
Part of Technical GEO Specialist (GEO-300)
For developers and technical SEOs: build a site AI can fetch, read and act on, and keep it that way.
12 lessons, practice quizzes, a final exam and the Sophyx Certified Technical GEO Specialist – Professional certificate. Regular price USD 129. Your first certification is free. Free with any paid Sophyx plan.
Start the course free