Llmref is a remote MCP server that gives an AI agent 4 tools, among them list_projects, list_versions, resolve_docs. It answers at https://api.llmref.org/v1/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Versioned documentation registry and semantic search for AI tools and coding assistants.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
list_projects | List indexed documentation projects. Use this first to discover what's available. Supports a forgiving fuzzy `query` over slugs (ranked by relevance) plus `limit` and `skip` for pagination. Inputs: limit, query, skip |
list_versions | List available versions for a project. Call this before resolve_docs or search_docs to see valid version strings. Inputs: project |
resolve_docs | Resolve a project version and get artifact URLs (llms.txt, llms-full.txt, meta.json, dumps). Use list_versions first to discover valid version strings. Inputs: project, version |
search_docs | Semantic search across a project's documentation. Returns chunks ranked by relevance. Requires the server to have semantic search enabled. Inputs: project, query, token_budget, top_k, version |
Every block below points at https://api.llmref.org/v1/mcp. Pick your client and copy.
claude mcp add --transport http llmref https://api.llmref.org/v1/mcp
{
"mcpServers": {
"llmref": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.llmref.org/v1/mcp"]
}
}
}{
"mcpServers": {
"llmref": {
"url": "https://api.llmref.org/v1/mcp"
}
}
}{
"servers": {
"llmref": {
"type": "http",
"url": "https://api.llmref.org/v1/mcp"
}
}
}{
"context_servers": {
"llmref": {
"url": "https://api.llmref.org/v1/mcp"
}
}
}{
"mcpServers": {
"llmref": {
"serverUrl": "https://api.llmref.org/v1/mcp"
}
}
}{
"mcpServers": {
"llmref": {
"url": "https://api.llmref.org/v1/mcp"
}
}
}name: Llmref
version: 0.0.1
schema: v1
mcpServers:
- name: Llmref
type: streamable-http
url: https://api.llmref.org/v1/mcp{
"mcpServers": {
"llmref": {
"httpUrl": "https://api.llmref.org/v1/mcp"
}
}
}{
"mcpServers": {
"llmref": {
"type": "http",
"url": "https://api.llmref.org/v1/mcp"
}
}
}{
"mcpServers": {
"llmref": {
"url": "https://api.llmref.org/v1/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.llmref.org%2Fv1%2Fmcp&type=streamable_http&id=llmref&name=Llmref
It answered our last check on 24 October 2026 in 159 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by llmref.org and served from api.llmref.org, the vendor's own domain: https://api.llmref.org/v1/mcp.
4, as returned by the server's own tools/list on 23 September 2026: list_projects, list_versions, resolve_docs, search_docs.
It answered our last check on 24 October 2026 in 159 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.llmref.org/v1/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: org.llmref. Endpoint host: api.llmref.org. ARD identifier: urn:air:org.llmref:mcp:llmref.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.