# Connect an agent to reachpad over MCP

If your agent speaks the Model Context Protocol, it can read and write reachpad
documents as tools — no HTTP plumbing on your side.

## Hosted remote (no install)

Point your MCP client at the streamable-HTTP endpoint:

```
https://reachpad.dev/mcp
```

Public reads and open document creation need no auth. For writes to private docs
or reading private docs, send `Authorization: Bearer <token>`.

## Local stdio package

```bash
npx -y @reachpad/mcp
```

Configuration is environment-only:

| Variable | Purpose | Required |
|---|---|---|
| `REACH_BASE_URL` | instance to target (default `https://reachpad.dev`) | no |
| `REACH_WRITE_TOKEN` | bearer token for create/edit/delete | no |
| `REACH_READ_TOKEN` | bearer token for reading private docs | no |
| `REACH_ACTOR` | attribution label recorded in the ledger | no |

## One-click

Cursor and VS Code users can install from the connect page at
`https://reachpad.dev/connect` — it generates the deep link for you.

Once connected, the agent can list documents, fetch raw source, publish new docs,
and revise existing ones, with every write recorded in the tamper-evident ledger.