Integration
How to make your site's content consumable by AI tools via the AnySiteMCP public REST API: meta tag, MCP URLs, sitemap, and client behaviour.
Meta tag (per-page discovery)
Place this meta tag in the <head> of each page you want to expose to AI. Use it only when the page is published in the portal.
<meta name="mcp-url" content="https://www.anysitemcp.com/mcp/yourdomain-tld/page-slug.json" />
Where to get the MCP URL
- Log in to the portal → Sites → your site → Pages.
- Open the page → in the System card find MCP URL (link + Copy button).
- Use that exact URL in your meta tag. Do not build it from internal IDs.
URL patterns
- Page JSON:
/mcp/{site_slug}/{page_public_hash}.json - Sitemap:
/mcp/{site_slug}/sitemap.xml(published pages only)
Behaviour rules
| Situation | HTTP | Client action |
|---|---|---|
| Page not found or not published | 404 | Do not list in sitemap; do not show meta tag. |
| Site disabled or suspended | 503 | Treat as temporarily unavailable. |
| Rate limit exceeded | 429 | Respect Retry-After and error.retry_after; retry later. |
| Bandwidth quota exceeded | 429 | Same REST shape; back off and retry after the period. |
Integration checklist
- Add the meta tag only for published pages, using the MCP URL from the System card.
- Use the Copy button in the page editor to avoid typos.
- On 404: treat as page not available (e.g. unpublished).
- On 503: treat as site temporarily unavailable.
- On 429: honour Retry-After and back off.
Full API contract and error details: see MCP Endpoints and Troubleshooting.
Coming soon: A WordPress plugin is currently in development and will be available soon.
Need help? Contact support