Pawsitive Future Pawsitive FutureDeveloper docs

Quickstart

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.

Add the server

In Claude Code:

bash
# add the server (once per machine)
claude mcp add --transport http pawsitive-future https://api.pawsitivefuture.org/mcp

# sign in — opens your browser; or type /mcp in a session and choose Authenticate
claude mcp login pawsitive-future

In Claude Desktop or claude.ai: Settings → Connectors → Add custom connector, paste https://api.pawsitivefuture.org/mcp, then Connect. The same sign-in page opens.

What happens the first time

  1. The client knocks. It calls /mcp and is told where to sign in: a 401 naming this server's sign-in page.
  2. You sign in. Your browser opens on api.pawsitivefuture.org. Enter your work email, then the 6-digit code that is sent to it.
  3. You allow it. A consent screen names the app asking. Allow it, and the browser hands the client a token.
  4. It works as you. The token lasts an hour and renews itself for 90 days. You will not see the browser again until then.

The handshake behind these steps is in Signing in.

Try it

Ask in plain language. The agent picks the tools.

  • 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.

The first two only read. The third and fourth change data, so your client stops and shows you the request first — see Reading and changing.

Check the connection

In Claude Code, /mcp lists the servers and whether each is connected. To see what the agent can call, browse the tool reference — it is the same list the server returns for tools/list.