Inlay
Expose your site to AI crawlers and answer engines with Inlay’s MCP endpoint, llms.txt, and structured data so agents can cite your product accurately.
Overview
Inlay is a Launch-phase MCP server that makes your website discoverable to AI agents via per-site MCP, llms.txt, and structured data.
What is this MCP server?
- Per-site MCP remotes at inlay.dev/api/mcp/{site_key} with streamable-http and SSE transports
- Publishes llms.txt and structured data so AI agents can find and summarize your pages
- Site key from inlay.dev/dashboard—required URL variable in the MCP manifest
- Version 1.0.1 from cartoonitunes/inlay-skills on GitHub
- Targets builders who care about Perplexity, ChatGPT Search, and agent-driven discovery—not only classic Google SEO
- Manifest version 1.0.1
- Two remote transports: streamable-http and sse at the same URL pattern
- Required path variable: site_key (from inlay.dev/dashboard)
Community signal: 1 GitHub stars.
What problem does it solve?
Solo builders ship landing pages that rank poorly in AI search because agents lack a structured, MCP-friendly view of the site.
Who is it for?
Founders with a live marketing site or docs who want AEO/GEO coverage and MCP exposure without building a custom agent API.
Skip if: Pre-launch ideas with no URL yet, or teams that only need on-page SEO plugins with no AI-agent channel.
What do I get? / Deliverables
After you configure your Inlay site key and MCP remote, agents can pull governed site context instead of guessing from noisy HTML snippets.
- Per-site MCP endpoint wired with your site_key
- llms.txt and structured data surfacing for agent consumption
- Clearer AI-agent and answer-engine discovery path for your brand
Recommended MCP Servers
Journey fit
Discoverability for AI search and agents is a Launch concern—after you have something to show, not while you are still scoping the idea. GEO (generative engine optimization) is the right shelf for tooling that makes sites legible to LLMs via MCP and llms.txt.
How it compares
AI discoverability and llms.txt MCP layer, not a code generator or vehicle-data integration.
Common Questions / FAQ
Who is Inlay MCP for?
Solo builders and small teams with a deployed site who want AI agents and answer engines to discover accurate product information through MCP and structured exports.
When should I use Inlay MCP?
Use it at Launch when pages are live and you are optimizing for AI search visibility, citations, and agent-readable site metadata—not before you have a site key and public URLs.
How do I add Inlay MCP to my agent?
Create a site at inlay.dev, copy your site_key from the dashboard, and add the remote URL https://inlay.dev/api/mcp/{site_key} (streamable-http or SSE) to your MCP client configuration.