Swole.fit

fit.swolePublished by swole.fitOfficial publisherv1.0.0Updated Oct 29, 2026

Swole.fit: your training plan, workout history and food log for your AI assistant (read-only).

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Swole.fit connects an AI assistant to your training plan, workout history and food log, read-only, over a remote OAuth-protected endpoint.

What you can do
  • Read the user's training plan.
  • Review workout history.
  • Look up food log entries.
  • All access is read-only, so the assistant can summarize and discuss fitness data but not change it.
When to use it
Useful when you want an assistant to review your workouts, plan or nutrition alongside other questions, for example to summarize recent training or discuss how your food log lines up with your plan.
Requirements
A remote MCP endpoint at the provider's site; no local package or runtime. An OAuth sign-in with a Swole.fit account is required. Network access to the provider is needed.
Before you install
The connection exposes personal fitness and nutrition data to the assistant and to the model provider behind it. Access is granted through OAuth, so review the scopes requested at sign-in. The server is described as read-only, so it should not modify your data.

Installation

In SourceWeft

  1. Open Swole.fit in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/fit.swole%2Fswole/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "swole-fit": {
      "type": "http",
      "url": "https://www.swole.fit/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.