---
title: "For agents: semver.xyz without a browser · semver.xyz"
description: "How to read and use semver.xyz without a browser: llms.txt, every page as Markdown, the Affordances graph with actions that run the reference parser, and MCP."
url: "https://semver.xyz/agents/"
lang: "en"
---

For agents

# Readable without a browser.

Everything on this site answers in text. Start from [llms.txt](https://www.semver.xyz/llms.txt), read any page as Markdown, or ask a page for its graph: what it shows, what can be done there, and where to go next. The graph is [Affordances](https://www.affordances.sh/), and its actions run the same reference parser the [range selector](https://www.semver.xyz/selector.md) does, so an agent can test a range, desugar it or order versions by precedence with one request.

[INDEX](https://www.semver.xyz/llms.txt)

### [llms.txt](https://www.semver.xyz/llms.txt)

[The normative Markdown first (the specification, the extensions, the grammars), then every page. Read it before anything else. `llms-full.txt` is the core text in one file.](https://www.semver.xyz/llms.txt)

[Open →](https://www.semver.xyz/llms.txt)

[MARKDOWN](https://www.semver.xyz/spec/SPEC.md)

### [Every page as Markdown](https://www.semver.xyz/spec/SPEC.md)

[Add `.md` to any page’s path (`/faq.md`), or request it with `Accept: text/markdown`. The specification itself is served as written at `/spec/SPEC.md`.](https://www.semver.xyz/spec/SPEC.md)

[Read the spec →](https://www.semver.xyz/spec/SPEC.md)

[GRAPH](https://www.semver.xyz/.well-known/affordances.json)

### [The Affordances graph](https://www.semver.xyz/.well-known/affordances.json)

[Ask any page with `Accept: application/vnd.affordances+json`. The selector’s graph has `select`, `desugar`, `parse`, `compare` and `bump`; the spec’s has `readSection`; the grammars’ has `readGrammar`.](https://www.semver.xyz/.well-known/affordances.json)

[Site index →](https://www.semver.xyz/.well-known/affordances.json)

[MCP](https://www.semver.xyz/mcp)

### [Connect an MCP client](https://www.semver.xyz/mcp)

[The site is an MCP server at `/mcp` (streamable HTTP, no auth) with two tools: open a page, call an action. Add it to Claude, Cursor or any client by URL, or run `@affordances/mcp` locally for the same tools.](https://www.semver.xyz/mcp)

[Endpoint →](https://www.semver.xyz/mcp)

Try it

## Three requests.

The graph of the range selector, one call to its `select` action, and the MCP server added to Claude Code. Each answers with JSON; the Markdown twins answer with text.

read a page's graph

```
curl -H 'Accept: application/vnd.affordances+json' https://semver.xyz/selector/
```

call an action

```
curl https://semver.xyz/selector/ \
  -H 'Content-Type: application/vnd.affordances+json' \
  -d '{"action":"select","input":{"range":"^1.0.0-rc","versions":["1.0.0-beta.2","1.0.0-rc.1","1.0.0","1.0.0+build.7"]}}'
```

connect an MCP client

```
claude mcp add --transport http semver https://semver.xyz/mcp
```

What an agent can rely on

Every action is `public` and `readOnly`: nothing here changes state, needs a session or asks for confirmation. The graphs and the Markdown are generated from the same sources as the pages (`spec/SPEC.md`, the extension Markdown, `benchmarks/results`), so they never disagree with what a person sees. Where a page and its Markdown could differ, the Markdown governs; the specification’s text is normative.
