skills/setup-mcp-server/SKILL.md
Set up an MCP (Model Context Protocol) server for any website via Inlay. Enables AI agents to search, browse, and interact with your site programmatically. Use when adding MCP support, enabling AI agent access, or setting up Inlay.
npx skillsauth add cartoonitunes/inlay-skills setup-mcp-serverInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Set up an MCP (Model Context Protocol) server for your website using Inlay. This lets AI agents like Claude, ChatGPT, and others interact with your site programmatically — searching pages, retrieving content, and using your site's functionality.
MCP (Model Context Protocol) is a standard that lets AI agents connect to external tools and data sources. An MCP server for your website gives AI agents tools like:
get_site_info — Get site metadata and descriptionsearch_pages — Search your site's contentget_page_content — Retrieve specific page contentlist_pages — Browse available pagesAdd the Inlay embed script to your site. This enables Inlay to index your content and serve it via MCP.
Next.js (App Router):
// app/layout.tsx
import Script from 'next/script'
export default function RootLayout({ children }) {
return (
<html>
<body>
{children}
<Script
src="https://cdn.inlay.dev/embed.js"
data-site-id="YOUR_SITE_ID"
strategy="afterInteractive"
/>
</body>
</html>
)
}
Next.js (Pages Router):
// pages/_app.tsx
import Script from 'next/script'
export default function App({ Component, pageProps }) {
return (
<>
<Component {...pageProps} />
<Script
src="https://cdn.inlay.dev/embed.js"
data-site-id="YOUR_SITE_ID"
strategy="afterInteractive"
/>
</>
)
}
Astro:
<!-- src/layouts/Base.astro -->
<script src="https://cdn.inlay.dev/embed.js" data-site-id="YOUR_SITE_ID"></script>
Plain HTML:
<script src="https://cdn.inlay.dev/embed.js" data-site-id="YOUR_SITE_ID"></script>
Replace YOUR_SITE_ID with the Site ID from your Inlay dashboard.
Once the embed script is installed and Inlay has indexed your site, your MCP endpoint is available at:
https://mcp.inlay.dev/YOUR_SITE_SLUG
Test it:
# Check MCP endpoint is responding
curl -s https://mcp.inlay.dev/YOUR_SITE_SLUG
# List available tools
curl -s -X POST https://mcp.inlay.dev/YOUR_SITE_SLUG \
-H 'Content-Type: application/json' \
-d '{"method":"tools/list"}'
Test each tool to make sure it works:
# Get site info
curl -s -X POST https://mcp.inlay.dev/YOUR_SITE_SLUG \
-H 'Content-Type: application/json' \
-d '{"method":"tools/call","params":{"name":"get_site_info","arguments":{}}}'
# Search pages
curl -s -X POST https://mcp.inlay.dev/YOUR_SITE_SLUG \
-H 'Content-Type: application/json' \
-d '{"method":"tools/call","params":{"name":"search_pages","arguments":{"query":"getting started"}}}'
# Get specific page content
curl -s -X POST https://mcp.inlay.dev/YOUR_SITE_SLUG \
-H 'Content-Type: application/json' \
-d '{"method":"tools/call","params":{"name":"get_page_content","arguments":{"path":"/"}}}'
Make your MCP server discoverable:
## MCP
- Endpoint: https://mcp.inlay.dev/YOUR_SITE_SLUG
- Tools: get_site_info, search_pages, get_page_content, list_pages
<meta name="mcp-server" content="https://mcp.inlay.dev/YOUR_SITE_SLUG">
Run an AI readiness audit to confirm MCP is detected:
curl -s -X POST https://www.inlay.dev/api/audit \
-H 'Content-Type: application/json' \
-d '{"url":"https://YOUR_SITE"}'
The MCP Server category score should now be high.
development
Create and configure llms.txt for any website or project. Analyzes project structure, generates llms.txt and llms-full.txt, places files in the correct location for your framework. Use when setting up llms.txt, improving AI discoverability, or making a site LLM-friendly.
tools
Audit any website for AI agent readiness. Check llms.txt, MCP servers, structured data, semantic HTML, meta quality, and more. Use when optimizing a site for AI agents, checking AI discoverability, or preparing for AI search engines.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------