The same API that runs the donor and clinic portals: a full REST reference, and the subset of it exposed as MCP tools so an agent like Claude can read what you can read and change what you can change — asking you first, every time, before it changes anything.
No service account. Every call — REST or MCP — reaches the API with your own token and
passes the same permission checks as the portal. A read or change you hold no grant for
comes back as 403, same as it would in the browser.
Reads run straight away on either surface. Through MCP, anything that creates, updates or deletes shows you exactly what it will do first, and runs only when you tick confirm — Claude cannot answer that dialog for you.
Both references below are generated straight from the API's own specification, not hand-written. A new endpoint appears here — and becomes an MCP tool unless it is deliberately excluded — the next time the API deploys.
There is no token to copy. Add the server, sign in once in your browser, and the client keeps itself signed in for 90 days.
It calls /mcp and is told where to sign in: a 401 naming this server's sign-in page.
Your browser opens on api.pawsitivefuture.org. Enter your work email, then the 6-digit code we send.
A consent screen names the app asking. Allow it, and the browser hands Claude a token.
An hour-long token that renews itself for 90 days. You won't see the browser again until then.
# 1 · add the server (once per machine) claude mcp add --transport http pawsitive-future https://api.pawsitivefuture.org/mcp # 2 · sign in — opens your browser; or type /mcp in a session and choose Authenticate claude mcp login pawsitive-future
Claude Desktop or claude.ai: Settings → Connectors → Add custom connector, paste the URL above, then Connect. The same sign-in page opens either way.
Which vouchers are waiting for PFF approval?
What does the voucher pool have left to give?
Approve the claim on that voucher.
Open a support case: batch 7 stopped printing.
Your client shows you exactly what will be sent. Tick "Make this change" and confirm to go ahead. Decline, close it, or wait 90 seconds, and nothing happens.
Confirm a change to Pawsitive Future Approve a claimed voucher and credit the clinic (deferred EFT) POST /api/claims/c-4471/approve Runs as you@yourorg.org, with your own permissions.
Every documented endpoint on api.pawsitivefuture.org — vouchers, claims,
organizations, people, money and payouts, donations, support — with real request and
response schemas, generated from the API's own OpenAPI document.
The subset of the same API exposed as tools at POST /mcp: a quickstart, how
tools are named and confirmed, then one page per tool with the arguments it takes and what
comes back. A short list of operations that make no sense from a conversation is left out,
each with its reason.