Choose another connection

Connect GoodSet to an MCP client

Add GoodSet's hosted MCP server, sign in, and track workouts from a compatible client. There is nothing to download or self-host.

Add the hosted server

Use a client that supports remote MCP over Streamable HTTP and browser-based OAuth.

Connection details

Name
GoodSet
Server URL
https://mcp.goodset.app/mcp
Transport
Streamable HTTP
Sign-in
OAuth in your browser

Setup

  1. 01

    Open your client's MCP settings

    Look for an option to add a remote or custom MCP server.

  2. 02

    Add the GoodSet server

    Enter GoodSet as the name and use the server URL shown above.

  3. 03

    Sign in

    Your client should open GoodSet sign-in. Approve access to your workout log.

  4. 04

    Test the connection

    Start a fresh conversation and ask, "What was my last workout?"

JSON configuration

Many MCP clients accept this format. If yours uses different field names, add the same server as a remote HTTP connection.

{
  "mcpServers": {
    "goodset": {
      "type": "http",
      "url": "https://mcp.goodset.app/mcp"
    }
  }
}

Try a workout

Write naturally. If your client supports voice, it handles the audio before calling GoodSet.

  1. Start a push workout.
  2. Bench press, 80 kilos for 8.
  3. Make that 82.5 kilos instead.
  4. What did I bench last time?

Questions

Which MCP clients work?

Your client must support remote MCP over Streamable HTTP and browser sign-in. GoodSet must also recognize the address it uses to finish sign-in. Client support varies, so check its MCP documentation first.

What if sign-in does not open?

The client may not support authenticated remote servers, or GoodSet may not recognize its sign-in address yet. Send the client name and callback URL to GoodSet support.

Where is my workout history stored?

GoodSet keeps the training log in your GoodSet account. Your client can read or update it only through the GoodSet tools you authorize.