MCP server

The GymUp MCP server lets an AI assistant read and change your training: search exercises, generate a program, edit a day or a single session, move sessions on the calendar, log sets, and keep your profile and memories up to date. It acts on your own account, with the same data you see in the app.

Before you start

• A GymUp account with an active subscription, bought in the mobile app. Without one, the server still connects and lists its tools, but every call answers with a subscription error.
• An MCP client that supports Streamable HTTP and OAuth, such as Claude Code, Claude Desktop, Cursor or Windsurf.

Connect

claude mcp add --transport http gymup https://gymup.ai/api/mcp

{
  "mcpServers": {
    "gymup": {
      "type": "http",
      "url": "https://gymup.ai/api/mcp"
    }
  }
}

On the first call, the client opens a browser window: sign in with the account you use in the app. See Authentication.

How changes reach your program

• A generated or imported program is saved as a draft. It goes on your calendar when you activate it from the in-app preview, or when your assistant calls commit_program_draft once you agree.
• The server instructs your assistant to wait for your confirmation before every change to a program, a session or the calendar. Clients that honour destructiveHint also ask before the calls that rewrite, move or delete programs, sessions and logs (annotations).
• Every write to a program, a session, the calendar or a log reports what it changed in written: { program_ids, dates }, and the app shows the change on the next refresh.

Server facts