Connected Apps (MCP)
Connect Claude, ChatGPT, Zapier or any MCP-compatible assistant to your Connected Performance data using the MCP server and OAuth sign-in, and manage or revoke those connections.
Overview
Connected Performance exposes an MCP server (Model Context Protocol). MCP is the standard AI assistants use to call an outside system's tools. Once connected, an assistant can ask questions about your data and, if you allow it, make changes: look up athletes, read the schedule, build workouts, check bookings, send messages, run reports.
Two things make this safe:
- You sign in with OAuth. The assistant never sees your password. It receives a token tied to your account.
- The token inherits your account. It never reaches another organization, and it cannot take actions your role can't take. A coach's token cannot do admin-only things.
Read access is broader than write access. Most read tools return organization-wide data to any account that holds the scope, so treat a connection as able to read anything in your organization that its scopes cover. Grant only the scopes an assistant actually needs.
Connections are listed under Settings > Connected Apps, and you can revoke any of them at any time.
How To
Find your server URL
The server URL is the same for every organization:
You can also copy it from inside the app: open Settings in the sidebar, select the Connected Apps tab, and click Copy URL.
That single URL is all any client needs. Discovery, sign-in and tool listing all happen automatically from it.
Connect Claude
Who adds the connector depends on your Claude plan.
- Individual (Free, Pro, Max): open Customize > Connectors, click +, then Add custom connector, and paste the server URL.
- Team and Enterprise: an owner or admin adds it once for everyone under Organization settings > Connectors > Add > Custom > Web, using the same URL.
Then each person connects their own account:
- Go to Customize > Connectors and click Connect next to Connected Performance.
- Sign in, review the permissions listed on the consent screen, and click Approve.
- In a conversation, click + > Connectors and enable Connected Performance.
Ask something like "list the athletes scheduled with me tomorrow" to confirm it works.
Connect ChatGPT
Custom MCP apps are a web-only feature on ChatGPT Business, Enterprise and Education workspaces. They aren't available on Free, Plus or Pro personal accounts. Your workspace owner may also restrict who can create them.
- A workspace owner enables Developer mode under Workspace Settings > Permissions & Roles.
- In developer mode, create a new app, paste the server URL, and choose OAuth as the authentication method.
- Save, then connect and complete the Connected Performance sign-in and consent screen.
- Test the app in a conversation. Once it works, an owner can publish it to the workspace from Workspace Settings > Apps so other members can connect their own accounts.
Connect Zapier
Zapier connects through its MCP Client app, which lets a Zap or a Zapier agent call the tools on your server.
- In Zapier, go to Apps and click + Add connection.
- Search for MCP Client and add it.
- Enter the server URL and select Streamable HTTP as the transport.
- When asked whether the server requires OAuth, choose Yes. Leave the bearer token field empty.
- Complete the Connected Performance sign-in and consent screen.
You can then use the MCP Client action inside a Zap and pick a Connected Performance tool to run. Typical use: a form submission triggers the Zap, which creates the athlete and sends a welcome message.
Zapier's MCP Client is a beta feature. Connected Performance also has a separate, older Zapier app that uses an API token instead of OAuth; the two are independent and you can use either.
Connect any other client
Any client that speaks MCP over streamable HTTP works the same way. The server supports:
- OAuth 2.1 authorization code flow with PKCE (S256), no client secret,
- dynamic client registration, so clients configure themselves from the URL alone,
- discovery at
/.well-known/oauth-authorization-serverand/.well-known/oauth-protected-resource.
Understand the permissions you're granting
The consent screen lists the exact scopes the client asked for. Scopes come in :read and :write pairs per area:
| Area | Scopes | What it covers |
|---|---|---|
| Athletes | athletes:read, athletes:write | Athlete profiles, notes, groups, custom profile fields, parent links, user accounts (staff and parents), locking and deleting accounts |
| Schedule | schedule:read, schedule:write | Scheduled events for one athlete or across the organization, group schedules, templates, rest days, shifting plans, progressions |
| Workouts | workouts:read, workouts:write | Workouts, exercises, folders, workout types, athlete libraries, logged workouts and exercise history |
| Assessments | assessments:read, assessments:write | Assessments and results, questionnaires and answers |
| Performance | performance:read | Rapsodo, Trackman, Blast, ArmCare, Pocket Radar, VALD data |
| Bookings | bookings:read, bookings:write | Bookings, check-in, sessions and availability, coach time off |
| Facility | facility:read, facility:write | Locations, spaces, activities, booking rules, levels, coach settings, facility stats, organization name and time zone |
| Messaging | messaging:read, messaging:write | Chats, group chats, and the SMS inbox where texting is enabled |
| Payments | payments:read, payments:write | Read: invoices, transactions, enrollments, credits, plans, discount codes. Write: plans, enrollments, credits, discount codes, recording a payment taken elsewhere |
| Reporting | reporting:read | Dashboard summary, exercise report, leaderboards and standings |
| Reference | reference:read | Lookup lists: coaches, levels, locations, workout types, exercise types, schedule templates, the organization profile |
Performance data is read-only. No tool charges, refunds or voids a card: payments:write lets an assistant set up plans, enrol athletes, grant credits and record that someone paid at the desk, but every real charge still happens in the app. There is also an orgstats:read scope, used only by service tokens Connected Performance issues for cross-organization reporting; a normal sign-in never grants it.
Three limits apply on top of scopes:
- Your role still decides writes. Write tools require a coach or admin account, and some (payments, user accounts, deleting an athlete) an admin. Granting
athletes:writeto an athlete's connection does not let it edit anyone. - Athletes and parents see their own athletes only. Organization-wide lists (every booking, every assessment result) answer only for staff accounts. An athlete's connection can log their own workouts, and nothing else that writes.
- Read is the safe default. A client that requests nothing specific gets the read-only scopes only.
What an assistant can do once connected
With the right scopes and a coach or admin account, the assistant can handle most day-to-day work in the app: add and edit athletes (one at a time or from a pasted roster), keep notes on them, chase missing profile info, build and edit workouts and assessments, put workouts on an athlete's or a group's schedule, apply templates, log results and test scores, read exercise history, book athletes into sessions, check them in, block out coach time off, run the dashboard and reports, message athletes and parents in chat or by text, and manage plans, enrollments, credits and discount codes.
Two tools are worth asking for first: the organization profile (it carries your time zone, so "book Jane at 3pm" lands on the right hour) and the athlete overview (profile, this week's schedule, last month's training, latest test results, upcoming bookings and credits in one call).
Some things stay in the app on purpose: charging or refunding a card, sending invoices, uploading videos and files, building automations, and anything a super admin does across organizations.
Review and revoke connections
Settings > Connected Apps lists each connection with its client name, the scopes it holds, when it was last used, and when it expires. Click Revoke to end it; the client's next request is rejected and it must be reconnected.
Revoke a connection when someone leaves, when you stop using an assistant, or any time a connection looks unfamiliar.
Know when a connection expires
Connections last 90 days, and the exact expiry date is shown in Connected Apps. After that the client stops working until you reconnect, which is the same short flow as the first time. Nothing is lost; the old token is simply dead.
Separately, an unfinished sign-in expires after 10 minutes. If you leave the consent screen open too long, start again from the client.
Tips
- Start read-only. Connect, ask questions for a week, and only add write access once you trust the results.
- Say which organization you mean if you are a super admin. Those connections start with no organization selected and the assistant will ask.
- Ask for the athlete overview before asking detailed questions about someone; it answers most of them in one go.
- Connect with the account whose access you actually want. A connection made by an admin can do everything an admin can do.
- Review destructive actions yourself. Tools that cancel bookings or delete schedule events are labelled as destructive, but that label is only a hint: whether the assistant stops to ask is up to the client. Don't assume you'll be prompted.
- One connection per assistant per person. Shared logins make the Connected Apps list impossible to audit.
Troubleshooting
The sign-in page opens but comes back to an error. The authorization request expires after 10 minutes. Start the connection again from the client.
"This connection is missing the required scope(s): …" The client asked for fewer permissions than the tool needs. Reconnect and make sure the scope is requested and approved.
"Your account role is not permitted to use this tool." The tool is restricted to a role your account doesn't have. Writes need a coach or admin account; payments and user accounts need an admin.
The assistant says a tool "failed" and repeats the reason. That is the tool refusing the request, not the connection breaking: a missing id, a date in the wrong format, an athlete outside your organization. The reason it quotes is the one to fix. If it says the tool failed unexpectedly, try again and contact support if it keeps happening.
The assistant says it isn't authorized, or everything suddenly fails. The connection expired or was revoked. Check Settings > Connected Apps and reconnect.
The assistant can't see another organization's data. That's by design. A connection is bound to the organization of the account that approved it.
The client can't find the server.
Paste the URL exactly as shown in Connected Apps, including /api/mcp, with no trailing slash.
Related
- Manage Your Settings
- User Roles & Permissions
- Import Third-Party Data
Referenced by
- 'API Access for Developers'integrations
- 'Athlete Custom Fields & Info Requests'user management
- 'Discount Codes'payments
- 'Organization Settings'getting started
- 'Parents & Guardians'user management
- 'Resources'communication
- 'REST API Endpoints'integrations
- 'Schedule Editor'scheduling
- 'Zapier & Webhooks'integrations