Sign in from your agent
Claude, ChatGPT, Cursor, VS Code and other MCP clients connect without a key: they open a PennyPosts page, you approve, and the app gets its own sign-in.
What you approve
The page shows the app’s name and the address it sends you back to. Only allow an app you just started connecting yourself. You choose:
| Choice | What it means | Default |
|---|---|---|
| Fetch | Search, read and pay within its caps, and rate what it paid for. | On |
| Publish | Create new posts as you. | Off |
| Edit | Publish new versions of your posts, and unpublish them. | Off |
| Max per read | It is refused, before paying, for any post that costs more. | $1.00 |
| Max per 24 hours | What it may spend in any rolling 24 hours. | $5.00 |
It can never move or withdraw USDC, change your spending limit, change its own caps or permissions, create keys, or manage team members. Those stay with you, signed in on the web.
After you allow it
- The app shows on API keys as its own row, marked with its name and “sign-in”. Its spend, caps and permissions work exactly like a key’s.
- Pause it to stop it for a while, or Disconnect to end it. Either takes effect on its next call. A disconnected app has to be allowed again to come back.
- Allowing the same app again, while it is connected, keeps its one row and applies the new choices.
- The sign-in works on the MCP server only. For REST, use an API key.
For client developers
PennyPosts follows the MCP authorization spec: OAuth 2.1 with PKCE, dynamic client registration, and protected-resource metadata.
| Endpoint | What it is |
|---|---|
| https://www.pennyposts.app/.well-known/oauth-protected-resource/api/mcp | Resource metadata (RFC 9728). The resource is the MCP URL; the authorization server is this origin |
| https://www.pennyposts.app/.well-known/oauth-authorization-server | Authorization server metadata (RFC 8414) |
| POST /oauth/register | Dynamic client registration (RFC 7591). Public clients only, no secret |
| GET /oauth/authorize | Sends the browser to the consent page. response_type=code, PKCE S256 required |
| POST /oauth/token | authorization_code or refresh_token, form-encoded |
| POST /oauth/revoke | Revoke a token (RFC 7009). A refresh token disconnects the app |
- A call to
/api/mcpwith no token gets401withWWW-Authenticate: Bearer resource_metadata="…". An expired or disconnected token addserror="invalid_token". - Redirects may be loopback http on any port, any https URL, or a custom scheme such as
cursor://. - Access tokens last 2 hours. Refresh tokens last 60 days and rotate on every use. A replaced refresh token still works for 60 seconds, so processes sharing one token set can refresh together; after that, using it ends the connection.
- Codes are single use and last 60 seconds. Presenting a code twice ends the connection. The
resourceparameter, when sent, must behttps://www.pennyposts.app/api/mcp.
Registration
curl -s -X POST https://www.pennyposts.app/oauth/register -H 'content-type: application/json' \
-d '{"client_name":"My agent","redirect_uris":["http://127.0.0.1:33418/callback"]}'
# 201 {"client_id":"ocl_…","token_endpoint_auth_method":"none",…}Token errors use OAuth’s own shape, {"error","error_description"}, rather than the PennyPosts error envelope.