TeamUp MCP server
TeamUp in any MCP client, through Memtro: TeamUp does not publish this server. Memtro's TeamUp connector reads TeamUp through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
TeamUp class and membership booking for gyms and studios: customers by name or email with status, classes by date, venue or instructor with capacity and bookings, a class roster, customers' memberships with dates and status, the membership catalogue, instructors and venues; when you ask, can add a customer (inviting them by email only if you say so), resend an invitation, book a customer into a class or remove the booking, confirm attendance or mark a no-show, give a free membership, cancel a membership, and create a class. TeamUp allows 250 requests a minute.
Reads
teamup_list_customersTeamUp customers: name, email, status, whether a lead, and when added.teamup_get_customerOne TeamUp customer by id: name, email, status, whether a lead and when added.teamup_list_eventsTeamUp classes and appointments in a date window, in start order: name, times, status (active or cancelled), capacity…teamup_event_rosterWho is booked into, or attended, one TeamUp class: each customer's name, id and booking status, plus counts by status.teamup_list_customer_membershipsMemberships held by TeamUp customers: membership name, status (active, hold, complete, cancelled), start, expiry and renewal dates…teamup_list_membershipsThe TeamUp membership catalogue (what customers can hold): name, type, price as shown, whether for sale or a drop-in, and how many active members.teamup_list_instructorsTeamUp instructors: id, name and whether active.teamup_list_venuesTeamUp venues (locations, including online ones): id, name, timezone, whether online or archived.
Acts, when you ask
These change something in TeamUp. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
teamup_create_customerAdds a customer to the TeamUp business, visible to staff.teamup_resend_inviteEmails a TeamUp customer who has not claimed their profile a fresh invitation.teamup_book_customerBooks a TeamUp customer into a class, using one of their memberships (or their best one when none is named); comped books it free.teamup_remove_bookingRemoves a TeamUp customer's booking from a class (their place is freed and may go to the waitlist).teamup_confirm_attendanceRecords that a TeamUp customer attended a class.teamup_mark_no_showMarks a TeamUp customer as a no-show for a class, which can cost them a session or a penalty under the studio's rules.teamup_give_membershipGives a TeamUp customer a membership from the catalogue, starting today or on start_date.teamup_cancel_membershipCancels a TeamUp customer's membership, ending it on expiration_date if given or as the membership's cancellation rules say; renewals stop.teamup_create_classCreates a class in TeamUp at a venue with its instructors; it appears on the schedule customers book from.
Connect it
First connect TeamUp on Dashboard → Connections, then add Memtro to your client once. The TeamUp tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared TeamUp connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Who is booked into tomorrow's 7am yoga?
- › Which classes this week are full?
- › Which memberships expire this month?
- › How many active members does the Unlimited membership have?
- › Book Sarah Chen into Thursday's 6pm spin class.
Questions
- Is this an official TeamUp MCP server?
- No. It is Memtro's MCP server with Memtro's TeamUp connector behind it: the connector reads TeamUp through its API with the credentials you connect on Dashboard → Connections, and TeamUp publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in TeamUp?
- Only when you ask, and only what it has been granted: add a customer, optionally emailing them an invitation; resend a customer's invitation email; book a customer into a class; remove a customer's booking from a class; confirm a customer attended a class; mark a customer as a no-show for a class; give a customer a free membership; cancel a customer's membership; create a class. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.