Strava MCP server
{
"mcpServers": {
"mcp-strava": {
"type": "http",
"url": "https://strava.run.mcp.com.ai/mcp"
}
}
}{
"mcpServers": {
"mcp-strava": {
"type": "http",
"url": "https://strava.run.mcp.com.ai/mcp"
}
}
}{
"mcpServers": {
"mcp-strava": {
"type": "http",
"url": "https://strava.run.mcp.com.ai/mcp"
}
}
}{
"servers": {
"mcp-strava": {
"type": "http",
"url": "https://strava.run.mcp.com.ai/mcp"
}
}
}{
"mcpServers": {
"mcp-strava": {
"type": "http",
"url": "https://strava.run.mcp.com.ai/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 3.0.0+0.7.1
What it does
HAPI MCP is a framework that converts OpenAPI specifications into MCP tools automatically, without rewriting existing API logic. It enables developers to expose any REST API as MCP-compatible tools for use with AI agents and language models.
- Transform existing REST APIs into MCP tools using OpenAPI specs, making them available to AI agents and chat interfaces without additional backend work.
- Build agentic systems that interact with multiple APIs through MCP clients like ChatGPT or Claude, with authentication and rate limits inherited from the original API.
- Orchestrate multi-step workflows across API-backed tools using deterministic planning, avoiding fragile prompt-based chaining.
This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.