Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://strava.run.mcp.com.ai/mcpThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http ai.com.mcp-strava https://strava.run.mcp.com.ai/mcpRun in a terminal.
{ "mcpServers": { "ai.com.mcp-strava": { "command": "npx", "args": [ "-y", "mcp-remote", "https://strava.run.mcp.com.ai/mcp" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
Stop rewriting systems for AI. Instantly turn your APIs into MCP servers.
HAPI MCP lifts your OpenAPI catalog into MCP tools automatically, keeping design (OAS/Arazzo) and runtime (agents/LLMs) cleanly separated. Your existing APIs become AI-ready tools—no new business logic, no sidecar servers, no rework.
Strava MCP tools for AI: athletes, activities, segments, clubs, routes. Powered by HAPI MCP server.
Pick your API spec
Run a single command
Use instantly
API Spec (swagger.json) → HAPI CLI → Usable Tool (AI-ready) ← MCP Clients
[ OpenAPI / Swagger ] [ HAPI CLI ] [ MCP Server ]
(Your API) → (Transform) → (Usable Tool)
↑ ↑
| |
[ ChatGPT ] [ runMCP ]
[ Claude ] [ OrcA ]
[ QBot ] [ chatMCP]
[ Agents ]
Do we need to rewrite our services?
No. HAPI MCP lifts your existing OpenAPI specs directly into MCP tools. Your auth, validation, and business rules remain unchanged.
Is this just another MCP server?
It’s the Headless API model: your API becomes the runtime. HAPI Server reflects it as MCP; runMCP scales it; OrcA orchestrates it. No duplicate logic.
Which clients can consume the tools?
Any MCP client: ChatGPT, Claude, QBot, chatMCP, bespoke orchestrators—vendor-neutral by design.
How do we keep control and compliance?
Your API remains the single source of truth. Policies, RBAC, rate limits, and audit logs flow through automatically; no shadow logic.
What about security and privacy?
Scoped credentials, per-tool permissions, and auditable calls are inherited from your API layer. HAPI adds guardrails and observability for regulated environments.
How fast can we get started?
You can transform your first API into an MCP tool in less than five minutes. The HAPI CLI makes it quick and painless.
Install HAPI CLI from latest release: https://github.com/la-rebelion/hapimcp/releases
Transform your OpenAPI spec into an MCP server with a single command:
hapi serve path/to/your/swagger.json --headless
Start using your MCP tools with any compatible client!
Explore the documentation for advanced usage and best practices.
Contributions are welcome! Open a discussion or submit a pull request on GitHub: https://github.com/la-rebelion/hapimcp
HAPI MCP is licensed under the MIT License. See LICENSE for details.
© 2026 MCP Directory.
Strava MCP tools for AI: athletes, activities, segments, clubs, routes. Powered by HAPI MCP server.
{ "mcpServers": { "ai.com.mcp-strava": { "url": "https://strava.run.mcp.com.ai/mcp", "headers": {} } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
HAPI Strava MCP Server is reached over HTTP.
Last checked 2026-10-21. Strava MCP tools for AI: athletes, activities, segments, clubs, routes. Powered by HAPI MCP server.