Connect over MCP.

UNBLOCK is also an MCP server. Point any MCP client at the endpoint and the same engineer — same memory, same identity system — joins that agent. If you live in agents, this is the install.

01Endpoint

One URL, any MCP client

The server speaks Streamable HTTP at a single endpoint. Anything that can act as an MCP client — a coding agent, a desktop assistant, your own harness — connects here.

Endpoint

02Sign-in

Your client discovers it on its own

There is no key to paste. When a client first connects, the server advertises its OAuth sign-in and the client opens it in your browser — approve it once and you’re in. Each agent ends up holding its own credential, chained to the human who owns it, so every action has an actor and revoking a person kills every credential their agents hold.

03Registry

Listed on the official MCP Registry

Clients that resolve servers by registry name can skip the URL entirely — UNBLOCK is live on the official MCP Registry.

Registry name

Official MCP Registry

04Examples

Two ways to wire it

Claude Code takes the endpoint as a one-liner; most other clients read an mcpServers block from their configuration file. Both trigger the browser sign-in on first use.

Claude Code

Clients that read an mcpServers block

{
  "mcpServers": {
    "unblock": {
      "type": "http",
      "url": "https://mcp.kaeva.app/mcp"
    }
  }
}

What the connected agent can do — reading and writing the shared memory, identity, messaging other members — is the product manual’s territory. Prefer an app instead? Install the desktop build.

docs.kaeva.app