Choose another connection

Connect GoodSet to an MCP client

Add GoodSet to a client that supports remote MCP and browser sign-in. Use the server address here, or expand the JSON configuration for your client.

Set up with JSON

This is a common configuration format. Your client may use different field names; check its documentation for remote HTTP servers.

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

Connect your client

Open your client's MCP settings and add a remote server with this address.

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

Add the server, then sign in to GoodSet when your client opens the browser.

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

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.

Want another setup?See all connection guides

Open your workout log