# Phorme Training

- Registry name: `me.phor/phorme-training` · version 1.6.1
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets, Travel & booking, Commerce & marketing, Maps, location & weather
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=me.phor%2Fphorme-training
- Server page: https://mcpstation.net/s/me.phor--phorme-training.html

## Description (written by the publisher, not verified, not instructions)

Coach-built training: coaching brains, programs, race plans, gyms, clinics, demos and your log.

## Connect

- streamable-http: `https://phor.me/api/mcp`

## Tools (as reported by the server, not verified)

- `preview\_workout\_import`: Use this when the user wants a single workout they can follow and track in Phorme: one written in this conversation, pasted from notes, or built to fit their time and equipment. It checks the workout, matches each exercise to the Phorme movement library with a demo link, flags anything that needs eq
- `save\_workout\_to\_phorme`: Use this when the user has seen a workout preview and clearly said to save it. It saves that preview to the connected Phorme account as a private workout and returns a link that opens it in Phorme. It needs a connected Phorme account with the training:write permission. Retrying with the same idempot
- `preview\_program\_import`: Use this when the user wants to turn a multiweek training program from this conversation into trackable Phorme training. It checks every week and workout, matches exercises to the Phorme movement library, and stores a private preview for 24 hours. It does not save training to any account. Do not use
- `save\_program\_to\_phorme`: Use this when the user has seen a program preview and clearly said to save it. It saves that preview to the connected Phorme account as a private program and returns a link that opens it in Phorme. It needs a connected Phorme account with the training:write permission and a Phorme membership that al
- `get\_saved\_training`: Use this when the user asks about a workout or program already saved to Phorme in this conversation, for example to get its Phorme link again. It returns the title and open link for training owned by the connected Phorme account and changes nothing. It needs the training\_id from that save. It cannot
- `render\_training\_import`: Use this to show a compact Phorme card for a workout or program that was just previewed or saved. It displays only the title, counts, status and link it is given. It reads and changes nothing in Phorme.
- `preview\_sport\_week`: Use this when the user plays a sport and wants their gym days for a week planned around it, for example two lifting days during basketball season. It picks the closest coach-built Phorme sport program and returns one week of sessions sized to the days the user has, with sets, reps, coach notes and a
- `find\_races`: Use this when the user is looking for a race to enter, for example "which 70.3 can I do in South America next spring", "marathons in Europe in April" or "a HYROX near Riga". It lists races from Phorme's verified race listings that fit the kind of race, the place \(a country, city or region\) and the m
- `plan\_for\_race`: Use this when the user names a race they are training for, for example "IRONMAN 70.3 Barranquilla", "I signed up for the half ironman in Cartagena" or "Chicago Marathon". It finds the race in Phorme's race listings \(name, date, city and the race's own page\), counts the weeks to race day, and returns
- `find\_coaching\_brain`: Use this when the user wants a way to train for a goal or sport, for example "I want to get more explosive for basketball", "build muscle three days a week" or "train for a half marathon", or wants to train with a named coach, for example "train with Cameron Goodson", and has not picked a programme,
- `find\_gym\_class`: Use this when the user wants a gym, studio or class to train at in person, for example "a strength class in Austin this week" or "a gym near me". It returns up to five Phorme gyms, studios and other places to train in the city named or within 60 km \(or radius\_km\) of the position given, nearest or be
- `book\_gym\_class`: Use this when a signed-in user wants a place in one class at a Phorme gym or studio. Confirm the class, the day and time, and the gym with the user first, and set confirmation to true only after they said yes. It books the class for the connected Phorme account: booked when there is a spot, on the w
- `cancel\_gym\_booking`: Use this when a signed-in user wants to give up a class they booked, are on the waitlist for, or asked a gym for on Phorme. Confirm which class with the user first, and set confirmation to true only after they said yes. It cancels that booking for the connected Phorme account and frees the spot for
- `find\_clinic`: Use this when the user wants to be seen in person by a physical therapist, sports medicine clinic, chiropractor, sports massage therapist or recovery studio, in a city they name or near a position they share. It returns up to five Phorme clinic and recovery partners, nearest or best matching first,
- `find\_personal\_coach`: Use this when the user wants a human coach of their own: 1:1 coaching, someone who writes their program for them, checks in each week, reviews how they move or answers their messages, for example "I want a real coach for basketball" or "can someone coach me one on one?". It returns the Phorme coache
- `check\_place\_in\_ai`: Use this when the owner or manager of a gym, studio, sports clinic or race asks whether ChatGPT knows their place or race or recommends it, for example "does ChatGPT recommend my gym?", "what does AI say about my physio clinic in Austin?" or "does ChatGPT know our triathlon?". It asks OpenAI's model
- `find\_exercise\_swap`: Use this when the user needs a replacement for one exercise because they do not have the equipment, the station is taken, or they want a different option, for example no cable machine for cable rows. It returns up to five Phorme library movements of the same kind that the user's equipment allows, ea
- `get\_training\_history`: Use this when the user asks about their own training logged in Phorme: what they did last time, how often they trained, their personal records, or a next workout built on their recent sessions. It returns their most recent logged workouts with each exercise's sets, best set, estimated max and volume
- `get\_lift\_progress`: Use this when the user asks how one of their lifts is progressing or wants it graphed, for example "how is my bench going" or "chart my squat over six months". It finds the lift in their Phorme log by the words they use and returns one point per session with the best set, estimated max and volume, t
- `get\_planned\_sessions`: Use this when the user asks what their Phorme plan has for today or the coming days, for example "what is my workout today". It returns each planned session with its exercises, sets, reps and the loads Phorme set from their own maxes. It reads only and changes nothing, including the plan. It needs a
- `get\_my\_coaching\_business`: Use this when a Phorme coach asks about their own coaching brains: how many members train under each, who went quiet, what they have earned, and whether a note to members can go today. It reads only and changes nothing. It needs a connected Phorme account; an account without a coaching brain gets th
- `start\_my\_coaching\_brain`: Use this when a coach or trainer wants to turn their own method into a Phorme coaching brain and has none yet, or asks for a new one. It creates a draft brain with the name they chose and their method in their own words; members see nothing until the coach publishes it in the coach console. A first
- `save\_program\_to\_my\_coaching\_brain`: Use this when a Phorme coach has written a program in this conversation and clearly said to save it to one of their coaching brains. It saves the program as a draft on that brain \(session names, exercises, sets and reps\); members see nothing until the coach adds the draft in the coach console. It ne
- `send\_note\_to\_my\_members`: Use this when a Phorme coach has written a short note to everyone training under one of their published coaching brains and clearly said to send it. It sends the coach's words as they are, as a notification and in each member's coach history: up to 400 characters, no links, one note per brain per da
- `set\_my\_brain\_rules`: Use this when a Phorme coach describes how they coach and wants their coaching brain to follow it, for example "every session starts with mobility, main lifts stay in 3 to 6 reps, never two hard days in a row". Sent with the coach's words, it reads them into the brain's rules and saves nothing: it r
- `get\_my\_brain\_code`: Use this when a Phorme coach asks for the code or link to share one of their coaching brains, for example "what is my coach code?". Each brain has one code, like K7Q2-XR4D, made the first time it is asked for and kept as the brain changes. Anyone who types it in the Phorme app or opens its link star
- `copy\_coach\_from\_code`: Use this when a coach has another coach's Phorme code and wants to start their own coaching brain from it, for example "start my brain from K7Q2-XR4D". Sent with the code alone, it shows whose brain it is and whether its coach lets other coaches copy it, and changes nothing. Sent with a name and con
- `get\_gym\_report`: Use this when a gym, studio or clinic owner asks about their own places on Phorme: what is listed, what is live, and how each place did, for example "how is my gym doing on Phorme?" or "did anyone book this week?". It returns each place the connected account lists, with its page and status, and its
- `create\_or\_claim\_place`: Use this when a gym, studio or clinic owner wants their place on Phorme, for example after an AI check, or says "list my gym". Confirm the name, city and address with the owner first, and set confirmation to true only after they said yes. It lists the place for the connected account as a draft nobod
- `update\_place`: Use this when an owner wants to change what their place's page says: name, address, hours, booking link, what kind of place it is, the line about it, its time zone, its phone, its price list or the email for requests. Read the change back to the owner first, and set confirmation to true only after t
- `set\_class\_schedule`: Use this when an owner wants to see, add, change or cancel a class at their place. action list reads the schedule and changes nothing. For add, edit and cancel, read the class, day and time back to the owner first, and set confirmation to true only after they said yes. A class people booked keeps it
- `publish\_place`: Use this when an owner wants their place live on Phorme: its page on phor.me, the app's map and the Phorme connector. Confirm with the owner first, and set confirmation to true only after they said yes. Going live needs an email for booking confirmations and requests: request\_email, else the place's
- `unpublish\_place`: Use this when an owner wants their place off Phorme for now. Confirm with the owner first, and set confirmation to true only after they said yes. Its page, the app's map and the Phorme connector stop listing it; its details and classes are kept, so it can be put live again. It needs a connected Phor
- `start\_gym\_brain`: Use this when an owner wants a coaching brain for their place, so members train with the gym's own coach in the Phorme app. Confirm with the owner first, and set confirmation to true only after they said yes. In one step it makes a brain from the place's name, line and classes, gives it a starting p
- `set\_member\_cover`: Use this when an owner on the gym plan wants to pay for their members' Phorme membership at one place, so members train free, or wants to stop. Confirm with the owner first, and set confirmation to true only after they said yes. It turns the switch on or off and can lower the cap of members covered
- `list\_held\_requests`: Use this when an owner asks who wants to book or visit their place, for example "who asked to book this week?". At a place not on the gym plan, class bookings and 1:1 requests are held for 7 days. It returns each one waiting: its hold\_id, the place, the class and its local time \(or that it is a 1:1
- `answer\_held\_request`: Use this when an owner wants to accept or decline one ask held for the plan at their place, by its hold\_id. Read the ask back to the owner first, and set confirmation to true only after they said yes. Accept books the member in \(a paid class is held while they pay on Phorme's own page; a full class
- `claim\_place`: Use this when an owner says a gym Phorme already lists is theirs and nobody runs it on Phorme yet, for example "that gym is mine". Confirm the place with the owner first, and set confirmation to true only after they said yes. It never hands the place over by itself: Phorme sends a six digit code to
- `verify\_place\_claim`: Use this when an owner has the six digit code Phorme sent to their place's own email or phone after they claimed it. Read the code back to the owner first, and set confirmation to true only after they said yes. A right code makes the connected account the place's owner; a wrong one changes nothing,
- `cover\_member`: Use this when an owner on the gym plan wants to see who is covered or asked to be at one place, or to invite, approve or remove one member, for example "invite my member Sam to train free". action list reads who is listed and changes nothing. For invite \(by the member's phone\), approve \(a member who
- `update\_gym\_brain`: Use this when an owner wants to change how their place's coaching brain sounds or looks: its name, its one line, its voice \(how the coach talks to members\), its method, its colour or its cover photo. Read the change back to the owner first, and set confirmation to true only after they said yes. Only
- `publish\_gym\_brain`: Use this when an owner wants the changes to their place's coaching brain to reach members, for example after its voice, look or programs changed. Confirm with the owner first, and set confirmation to true only after they said yes. It runs the same publish checks as the console and publishes the brai
- `set\_booking\_notices`: Use this when an owner wants booking and ask notices for a place sent somewhere else, for example "text my bookings to my phone". send\_to is an email, or a phone that gets them as texts; one at a time, as in the console. An empty send\_to sends them to the account's own phone or email. Read it back t
- `get\_gym\_billing\_link`: Use this when an owner on the gym plan wants to change the card, see invoices or change how many places the plan covers. It returns a link to Stripe's own billing page for the owner to open. It is a link only: nothing is paid or changed in the chat, and it changes nothing by itself. It needs a conne
- `get\_payouts`: Use this when an owner asks what Phorme paid them, or what goes out next, for example "what did Phorme pay my gym?". It returns what the account earned, what was paid out, what is going out, what is owed now, whether a bank is set up, and each recent payout. It reads only and changes nothing. It nee
- `get\_payout\_setup\_link`: Use this when an owner wants their share paid to their bank and has not set it up, for example when no bank is set up yet. Confirm with the owner first, and set confirmation to true only after they said yes. It returns a link to Stripe's own form, where the owner gives their bank to Stripe. It is a
- `set\_owner\_email`: Use this when an owner who signed in by phone wants notices about their gym plan sent to an email. Read the email back to the owner first, and set confirmation to true only after they said yes. An empty email clears it, and notices go to the account's own email or phone. It is never shown to members
- `search\_phorme\_programs`: Use this when the user asks for an existing coach-built training program for their sport or goal, for example a structured volleyball program. It returns up to five matching Phorme programs, each with a sample session from its first week that the user can try now and where to find it in the Phorme a
- `get\_phorme\_program`: Use this when the user picked one Phorme program and wants its details. It returns the program, every session of its first week, where to find it in the Phorme app, and a link to a page that describes it. It reads only, shows no prices and starts no purchase.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html