MCP integration
Give MCP-compatible AI agents direct, read-only access to the international llmsmap.me catalog. The public server is stateless and does not require an API key.
Server endpoint
https://llmsmap.me/api/mcp/Client configuration
Add the remote HTTP server to the MCP configuration supported by your client:
{
"mcpServers": {
"llmsmap": {
"url": "https://llmsmap.me/api/mcp/"
}
}
}Configuration file names and remote-server support vary by client. Check the current documentation for your MCP host before editing its configuration.
Available tools
list_catalog
Returns approved international websites and their llms.txt metadata.
Optional parameter: limit (maximum 50).
search_catalog
Searches the international directory by product name or URL.
Required: query. Optional: limit.
Example prompts
- “List 20 websites in the llmsmap directory.”
- “Find documentation websites with llms.txt.”
- “Show the llms-full.txt URL and token count for example.com.”
How requests are scoped
Calls sent to llmsmap.me/api/mcp/ are scoped to the .me editorial edition throughsource_edition. The server returns public catalog data only.
Operational limits
- Results are capped at 50 items per tool call.
- The service may apply IP-based rate limits.
- Clients should cache stable results and retry temporary failures with backoff.
REST alternative
If your tool does not support MCP, use the same catalog through the public REST API.
Versioned MCP manifests, the OpenAPI contract, and the Postman collection are published in the public llmsmap distribution repository.