Skip to main content
Glama

HAPI Strava MCP Server

Server Details

Strava MCP tools for AI: athletes, activities, segments, clubs, routes. Powered by HAPI MCP server.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL
Repository
la-rebelion/hapimcp
GitHub Stars
7

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsC

Average 3.1/5 across 13 of 13 tools scored. Lowest: 1.9/5.

Server CoherenceA
Disambiguation4/5

Most tools have distinct purposes targeting specific Strava resources like clubs, segments, athletes, and gear, with clear boundaries. However, 'getEffortsBySegmentId' and 'getSegmentEffortById' could cause confusion as both involve segment efforts, though one lists efforts for a segment and the other retrieves a specific effort by ID, which descriptions help clarify.

Naming Consistency4/5

Tool names follow a consistent 'verbNoun' pattern (e.g., getClubById, exploreSegments) with clear action-resource pairs, making them predictable and readable. There are minor deviations like 'exploreSegments' using 'explore' instead of 'get' or 'list', but overall the naming is coherent and follows a standard convention.

Tool Count5/5

With 13 tools, the server is well-scoped for a Strava API integration, covering key areas such as clubs, segments, athletes, and gear. Each tool serves a specific function without redundancy, and the count is appropriate for the domain, allowing comprehensive access without being overwhelming.

Completeness4/5

The tool set provides good coverage for reading and listing operations across Strava resources like clubs, segments, and athlete data, with no major gaps for core querying tasks. However, it lacks write operations (e.g., create/update clubs or segments) and some advanced features like activity management, which are minor gaps that agents might work around but don't hinder basic functionality.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.