Skip to main content

Release context for your agents

Let coding agents read what shipped, prepare release updates, and help review them. Public reading and authenticated actions stay separate; publishing requires your approval.

Agents are an audience too

Give coding agents context about what a dependency shipped. Published public stories are available as markdown and through JSON and MCP tools. Private release content does not become public by enabling an agent integration.

Read the MCP docsSee /llms.txtWhy agents are a channel
agent session

$ curl https://yanib.dev/llms.txt

# the broadcasting layer, indexed for agents

/llms.txt → product + endpoint index

/stories/{slug}/llms.txt → stories as clean markdown

/api/v1/releases/latest → latest release, JSON

/api/mcp/public → read only MCP, no account

Agent callable, end to end

  • A real MCP server

    Agents in Claude Code, Claude Desktop, or Cursor query, draft, QA, and, with your approval, publish releases. OAuth on first connect. Nothing to copy and paste. Manage tokens and connections in Settings → Agents.

    Agents get tools including yanib_draft_release, yanib_review_release, and yanib_publish_release, publish requires explicit human approval.

    Read the MCP docs

  • Readable by any agent

    Published public stories are readable through the public MCP endpoint and llms.txt without authentication. Private content keeps its access controls.

  • Scoped & safe

    OAuth 2.1 with PKCE, per scope consent, and human approval publish. Agents never ship without you.