Exploded view of a connector illustrating how an MCP connection is built

Insights · AI interfaces

How does MCP work for websites?

An MCP server makes selected website content available to connected applications. Follow the path from a request to a verifiable source.

01Insights · AI interfaces

Client, server and published content.

The AI application contains an MCP client. It connects to a server and discovers the available capabilities. Our server exposes published pages as resources and provides tools for searching and retrieving them. It does not generate an AI answer itself: it returns content for the client to use.

Chat window, server and content pages on one rail – how an MCP connection is structured

02Insights · AI interfaces

A search on LEVERLY HILLS.

A connected client might search for MCP integration in English. The search tool returns matching pages with a title, excerpt and source URL. The client can then retrieve a complete page. This content comes from the same data as the visible website and is updated together with the next deployment.

  • search_content: search published pages
  • get_page: retrieve a known page
  • Resources: read pages directly as text
Search loop: from chat via server to website and back as a result

03Insights · AI interfaces

MCP, APIs and llms.txt have different jobs.

An existing API can serve data to many applications. MCP exposes selected data or capabilities through a common protocol for supporting clients. An llms.txt file is a guide with links, not an executable server. None of these interfaces guarantees indexing or an AI citation.

Plug, curly brackets and text file on three pedestals – MCP, API and llms.txt compared

04Insights · AI interfaces

Public access has deliberate boundaries.

Our example contains published website text only. It cannot access emails, credentials or private files. Pages are selected by known identifiers; arbitrary internet addresses cannot be fetched. Content search and retrieval require neither write access nor external model calls.

Shelf with openly accessible documents and a locked section

05Insights · AI interfaces

When does a server make sense?

When applications need repeated access to maintained content and suitable clients are available. For a small website whose main goal is discovery, useful expert pages and technical SEO are often the first step. Protected data or actions require additional work on identity, permissions and confirmation.

Scale balancing content pages against a server – when a dedicated MCP server pays off

Insights · AI interfaces

Common questions

Will AI automatically discover my server?

Do not rely on that. The endpoint needs to be explicitly connected in a compatible application. Supported connections depend on the client's capabilities and configuration.

Is the content live?

Our server reflects the published website version. Changes are deployed together with the site. Projects with frequently changing content can connect a CMS or another maintained source.

Flashcards with plug, brackets, document and key – common questions about MCP

Next step

What would this look like with your content?

We show you what your own MCP connection can do for your website – and tell you if it isn't worth it yet.