Connect Claude or another MCP client

United Pet Club runs a Model Context Protocol (MCP) server so AI assistants can use United Pet Club for the people who connect them. An assistant can find pet pros and their services, check open times, browse adoptable animals, and — once the person signs in — read that person’s own pets, appointments, orders and notifications, or a business’s schedule, services, clients, sales and reviews.

Server URL: https://mcp.unitedpetclub.com
Transport: Streamable HTTP (MCP revisions 2025-03-26 to 2026-07-28; stateless)
Access: read-only. No tool books, buys, sends or changes anything.
Price: free for every signed-in member, with rate limits only.

Add it to your client

Client	How
Claude (claude.ai, Desktop, mobile)	Customize → Connectors → Add custom connector, URL `https://mcp.unitedpetclub.com`. Leave the OAuth client ID and secret empty.
Claude Code	`claude mcp add --transport http upc https://mcp.unitedpetclub.com`, then `/mcp` to sign in when a tool needs it.
ChatGPT and other clients	Add a remote MCP server with the URL above. Any client that follows the MCP authorization spec signs in by itself.

Nothing to register first: the public tools work at once, and the client signs in the first time the assistant calls a tool that needs an account.

United Pet Club’s authorization server is https://auth.unitedpetclub.com. Everything follows the MCP authorization specification:

A tool that needs an account, called without a token, answers 401 with WWW-Authenticate: Bearer resource_metadata="https://mcp.unitedpetclub.com/.well-known/oauth-protected-resource", scope="upc:read".
The RFC 9728 document names the resource (https://mcp.unitedpetclub.com) and the authorization server.
The authorization server’s RFC 8414 metadata (https://auth.unitedpetclub.com/.well-known/oauth-authorization-server) names the endpoints.
The client identifies itself with a client ID metadata document (its client_id is an https URL; Claude does this) or registers through dynamic client registration (POST /connect/register, RFC 7591).
The person signs in on United Pet Club and approves the connection on the consent page. They choose which profile the assistant acts as: their own, or a business they run. One connection is one profile; to use another, connect again.
The client sends resource=https://mcp.unitedpetclub.com (RFC 8707) with PKCE S256, and gets an access token bound to the MCP server and a rotating refresh token.

Rules your client must meet:

PKCE S256 on every authorization request.
The resource parameter on the authorization and token requests. A token issued for the REST Partner API does not work here, and an MCP token does not work there.
Redirect URIs are https, or a loopback address (http://127.0.0.1/…, http://localhost/…) on any port.
A refresh token that stopped working answers invalid_grant: send the person through sign-in again.

Scopes

Scope	What it allows
(none)	The public tools, without signing in.
`upc:read`	Read the chosen profile’s own data: a member’s pets, appointments, orders, notifications and plan; a business’s schedule, services, clients, sales and reviews.
`upc:admin.read`	United Pet Club staff only: platform reports and admin lookups. Never granted to anyone else.

What the assistant sees

Every signed-in tool reads exactly what the chosen profile sees on www.unitedpetclub.com or in the Dashboard — the same privacy settings, ownership rules and plan limits. Nothing is widened for AI clients. A call that a member would be refused on the website is refused here too, with the same reason.

Public tools

Tool	What it does
`find_pros`	Pet pros and businesses by service or kind and place, with profile and booking links.
`search_services`	Kinds of services by name, with the businesses that offer them.
`get_business`	A business’s public profile by handle and the services it takes bookings for, each with a `bookUrl`.
`get_service_availability`	Open times for one service, read only, plus its `bookUrl`.
`search_animal_listings`	Adoption and sale listings, with a link to each on www.

A member’s own profile

Tool	What it does
`whoami`	The profile the connection acts as.
`list_my_pets`, `get_pet`	The profile’s pets.
`get_pet_health_records`, `get_pet_vaccinations`	A pet’s health records and vaccinations.
`my_appointments`	Appointments the member booked (personal profiles).
`my_orders`, `get_order`	Orders placed.
`my_notifications`	The notification inbox.
`my_plan_and_usage`	The plan, what it includes and what has been used.

A business

Tool	What it does
`business_appointments`	The business’s appointments in a date range.
`business_services`	Its bookable services, with its customers’ booking links.
`business_clients`	Its clients and their pets; contact details only when asked.
`business_sales`	Store and marketplace sales.
`business_reviews`	Reviews received and the rating summary.

tools/list shows a signed-in client only the tools for its profile.

Rate limits

Caller	Limit
Signed in	120 requests a minute and 5,000 tool calls a day per connection
Signed out	60 requests a minute per address (an AI platform’s published egress range shares a larger bucket)

Over the limit: 429 with Retry-After. The gateway’s own limits apply too.

Errors

HTTP	Meaning	What to do
`401` + `WWW-Authenticate`	No token for a protected tool, or the token is no longer valid (expired, disconnected).	Sign in, or refresh.
`429`	Rate limited.	Wait `Retry-After` seconds.
`503` + `Retry-After`	United Pet Club could not check the connection.	Retry shortly.
`200`, `isError: true`	The tool ran and United Pet Club refused or could not find something (another profile’s data, a feature the plan does not include, a private item). The text gives the reason and the platform response code.	Tell the person; do not retry as someone else.

Disconnecting

The person disconnects the assistant under Account → Connected apps. The connection stops working at once. United Pet Club may suspend any client.

WordPress plugins and AI agents — the REST Partner API for businesses.
Authentication — tokens for the REST API.