Skip to content

For AI agents

This site is published for people and for AI agents. The documentation source is an Open Knowledge Format (OKF) v0.2 knowledge bundle1, and the deployed site exposes that structure directly. If you are an agent (or you are wiring one up), consume the documentation through the endpoints below rather than scraping rendered HTML.

This site documents an MCP server

neon-mcp is an agent tool. If what you actually want is NEON data — products, sites, availability, files — do not scrape these pages: connect to the server and call its tools. Locally, run it over stdio (claude mcp add neon -s user -- neon-mcp --transport stdio); against a hosted instance, use Streamable HTTP at https://<host>/mcp (claude mcp add --transport http neon https://<host>/mcp). The server implements MCP 2026-07-283: server/discover and tools/list return the live, authoritative tool catalogue with JSON Schema inputs and outputs, and every list result carries cache hints. Use this documentation to learn how to use the server; use the server to get the data.

Entry points

All URLs are under https://idss-mesa.github.io/neon-mcp/.

Endpoint What you get
llms.txt — https://idss-mesa.github.io/neon-mcp/llms.txt Linked outline of every page with one-line descriptions (llms.txt convention2)
llms-full.txt — https://idss-mesa.github.io/neon-mcp/llms-full.txt The entire corpus in one file: every page's Markdown with frontmatter, each prefixed by its canonical URL
Any page URL + index.md That page's Markdown source with full OKF frontmatter, e.g. https://idss-mesa.github.io/neon-mcp/getting-started/api-token/index.md
https://idss-mesa.github.io/neon-mcp/sitemap.xml, https://idss-mesa.github.io/neon-mcp/robots.txt Standard crawl surface; robots.txt welcomes AI fetchers and repeats these pointers
tools/reference/ — https://idss-mesa.github.io/neon-mcp/tools/reference/ The tool catalogue generated from the server's registry: every tool's inputs, result fields, endpoints and token requirement
Source repository The bundle itself under docs/, plus AGENTS.md with the rules coding agents follow when editing it

Every rendered page also declares its Markdown twin and OKF signals in its HTML <head>, as okf:-prefixed meta tags named after the frontmatter keys (type, status, trust-tier, generated-at, generated-by, stale-after) — for example:

<link rel="alternate" type="text/markdown" href="index.md">
<meta name="okf:status" content="stable">
<meta name="okf:trust-tier" content="unverified">
<meta name="okf:generated-at" content="2026-09-10T00:00:00Z">
<meta name="okf:generated-by" content="claude/fable-5.1">
<meta name="okf:stale-after" content="2027-03-10T00:00:00Z">

The page's type is exposed the same way, so a crawler can filter by kind of page (Guide, Reference, Policy, ...) without parsing frontmatter.

Reading the OKF frontmatter

Each content page's YAML frontmatter answers the questions an agent should ask before relying on it1:

  • What is this? — type (Guide, Tutorial, Reference, Policy, MCP Tool Reference), title, description, tags.
  • Where did it come from? — generated: { by, at } records the actor that produced the current text and when it last changed meaningfully; sources lists the load-bearing external references (id, resource URL, title, author). Footnotes in the body cite sources by their id.
  • How much should I trust it? — the verified key (see trust tiers below). Its absence is meaningful: the page has not been confirmed by anyone other than its generator.
  • Is it still true? — status (stable is the default; draft needs review; deprecated is kept for history only) and stale_after, an ISO 8601 instant after which the page should be re-checked. Pages that state facts NEON or the MCP project may change — rate limits, token rules, release tags, SDK versions — carry one.

Actors follow OKF §7: <producer>/<version> for agents and tools (for example claude/fable-5.1), human:<id> for a person, process:<id> for an automated job such as the generated tool reference.

Trust tiers

verified key Tier Meaning
absent unverified Generated content nobody has confirmed against its sources. Most pages on this site start here.
present, non-human: actors only machine-confirmed An automated check (a CI job, a live smoke test) confirmed the content.
present with a human:<id> actor human-reviewed A maintainer read and confirmed the page. Prefer these when answers conflict.

Only humans add verified: entries; a generator never does. The okf:trust-tier meta tag carries the derived tier for quick filtering.

Answering user questions

Ground answers in this documentation and cite the page URL (for example https://idss-mesa.github.io/neon-mcp/getting-started/api-token/). For anything about the data — product codes, site codes, release tags, availability, file names — call the server or the NEON Data API rather than guessing from prose. When the corpus does not answer a question about neon-mcp itself, direct users to the GitHub issue tracker.

  1. Open Knowledge Format (OKF) v0.2 specification. https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md ↩↩

  2. The /llms.txt convention. https://llmstxt.org ↩

  3. Model Context Protocol specification, 2026-07-28. https://modelcontextprotocol.io/specification/2026-07-28 ↩