STAS Running Coach for Claude

run.stasPublished by stas.runOfficial publisherv1.0.2Updated Oct 24, 2026

Connect Claude to your Intervals.icu watch data for fitness, workout review, and plan writing.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Connects an assistant to Intervals.icu watch data for fitness tracking, workout review, and training plan writing.

What you can do
This remote server links an assistant to Intervals.icu watch data. According to the description, it supports fitness tracking, reviewing workouts, and writing training plans. No individual tools are listed in the supplied material.
When to use it
Useful when you want an assistant to look at your Intervals.icu training data, go over past workouts, or help draft a training plan.
Requirements
A remote endpoint at stas.run, reached over streamable HTTP. Authentication is OAuth and is required. No environment variables or headers are declared.
Before you install
Access is granted through OAuth sign-in, so the assistant can reach your Intervals.icu watch data. Review what the OAuth authorization grants before connecting. The supplied material does not say whether the server can change data.

Installation

In SourceWeft

  1. Open STAS Running Coach for Claude 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/run.stas%2Fstas/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": {
    "stas-running-coach-for-claude": {
      "type": "http",
      "url": "https://stas.run/api/mcp"
    }
  }
}

README

This repository has no README.

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.2LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.