home / mcp / ridewithgps mcp server
MCP Server for Ride With GPS
Configuration
View docs{
"mcpServers": {
"boezzz-ridewithgps-mcp": {
"command": "node",
"args": [
"/absolute/path/to/ridewithgps-mcp/build/index.js"
],
"env": {
"RWGPS_API_KEY": "your_api_key_here",
"RWGPS_AUTH_TOKEN": "your_auth_token_here"
}
}
}
}RideWithGPS MCP Server is an AI-assisted bridge that gives you programmatic access to your RideWithGPS data through an MCP client. It lets you retrieve and inspect your routes, trips, events, and user profile, enabling automation and conversational queries over your cycling data.
Use an MCP client to connect to the RideWithGPS MCP Server and perform actions such as listing your routes, viewing route details, listing trips, and syncing your data. You can ask for things like showing your recent routes, getting details for a specific route, listing trips from a time period, or retrieving your user profile. To work with this server, you need to configure an MCP client with the server command and required credentials. The server exposes endpoints for routes, trips, events, and user data via MCP calls.
Prerequisites: Node.js 18.0.0 or higher. Node 20.0.0 or newer is recommended.
Clone the MCP server repository and install dependencies, then build the project.
git clone https://github.com/boezzz/ridewithgps-mcp.git
cd ridewithgps-mcp
npm install
npm run buildInstall the Claude Desktop app (or another MCP client) and prepare to run the local server with your RideWithGPS credentials.
{
"mcpServers": {
"ridewithgps-mcp": {
"command": "node",
"args": ["/absolute/path/to/ridewithgps-mcp/build/index.js"],
"env": {
"RWGPS_API_KEY": "your_api_key_here",
"RWGPS_AUTH_TOKEN": "your_auth_token_here"
}
}
}
}Retrieve a list of routes owned by the user on RideWithGPS, ordered by updated_at descending. Note: only routes owned by you are returned.
Retrieve full details for a specific route including track points, course points, and points of interest.
Retrieve a list of trips/activities owned by the user on RideWithGPS, ordered by updated_at descending.
Retrieve full details for a specific trip including track points and performance data.
Retrieve profile information for the user.
Retrieve a paginated list of events owned by the user, ordered by created_at descending.
Retrieve full details for a specific event including associated routes.
Retrieve items (routes and/or trips) that the user has interacted with since a given datetime.