Aurekai

Carriers

Tools, agents and push feeds

How outside programs read what Aurekai keeps: an MCP server for your desktop tools, an A2A card for other agents, and WebSub so publishers can push new posts instead of being polled.

Sources readable
2,374
MCP
/mcpModel Context Protocol
A2A
Agent card/.well-known/agent-card.json
WebSub
Hubpush in, push out

Your desktop tools

MCP server

Point Claude, Cursor or any MCP client at Aurekai. The tools read sources and kept passages with your account's own limits; nothing is granted that your account does not already have.

{"mcpServers":{"aurekai":{"url":"https://aurekai.work/mcp"}}}
Sign in to authorize a tool

Other agents

Agent-to-agent

Other agents discover what Aurekai offers from its agent card and call it over A2A. A call is an ask; nothing past a person's own submit is done for them.

Read the agent card

WebSub

Push delivery

When a publisher declares a hub, Aurekai can lease a subscription and receive each new post as it is published, checked with an HMAC signature before it is accepted. A delivery asks for a fresh observation; it does not publish anything by itself.

How the hub works

New source

Add a feed or page

Paste an RSS, Atom or JSON Feed address, or any public page. You see it before anything is read.

  1. Review. The address is shown back to you. Nothing is fetched.
  2. Read. With write access you ask the source for one copy, and a receipt is kept with it.
  3. Keep it coming. When the publisher names a WebSub hub, new posts can be pushed instead of polled.