New connector: RideWithGPS

[NicolasBelissent]

https://github.com/boezzz/ridewithgps-mcp

@claude

[willleeney]

@claude

[claude]

Claude finished @willleeney's task —— View job

---

RideWithGPS Connector Implementation Complete ✅

Todo List:

• Read repository guidelines and examine existing connector structure
• Analyze the external RideWithGPS MCP repository in detail
• Implement the RideWithGPS connector following repository standards
• Create tests for the connector
• Run linting and testing
• Commit changes locally

🎯 Implementation Summary

I've successfully created a comprehensive RideWithGPS connector for the mcp-connectors repository with the following features:

📁 Files Created:

• packages/mcp-connectors/src/connectors/ridewithgps.ts - Main connector implementation
• packages/mcp-connectors/src/connectors/ridewithgps.spec.ts - Comprehensive test suite
• Updated packages/mcp-connectors/src/index.ts - Added connector to exports

🔧 Tools Implemented:

1. GET_CURRENT_USER - Retrieve user profile and total cycling statistics
2. GET_ROUTES - List user-owned cycling routes with basic information
3. GET_ROUTE_DETAILS - Get comprehensive information about specific routes
4. GET_TRIPS - List cycling trips/activities with performance metrics
5. GET_TRIP_DETAILS - Get detailed performance data for specific trips
6. GET_EVENTS - List cycling events the user has participated in or created

✅ Quality Assurance:

• 9 comprehensive tests covering all tools with happy path, error handling, and edge cases
• All tests passing ✨
• Code formatting and linting passed
• Follows repository conventions for naming, structure, and patterns
• TypeScript implementation with proper type definitions
• Authentication via API Key and Auth Token (as per RideWithGPS API requirements)

🚧 Push Status:

The implementation is complete and committed locally, but there's a GitHub App workflow permission issue preventing the push to the remote branch. This is a repository configuration issue, not a code problem.

💡 Next Steps:

A repository administrator can either:

1. Grant workflow permissions to the Claude bot, or
2. Manually copy the implemented files to create a PR

The connector is production-ready and follows all repository standards and conventions.

---

[mattzcarey]

@claude work on this

[claude]

Claude finished @mattzcarey's task —— View job • claude/issue-48-20250821-2009 • Create PR ➔

---

RideWithGPS Connector Implementation Complete ✅

Todo List:

• Check current state of repository and branch
• Verify if previous RideWithGPS implementation exists locally
• Install dependencies and run setup
• Analyze repository structure and existing connectors
• Implement RideWithGPS connector based on external repository analysis
• Create comprehensive test suite
• Update index.ts to export the new connector
• Run linting and fix any issues - All code quality checks pass ✅
• Commit and push changes
• Provide PR creation link

🎯 Implementation Summary

I've successfully created a comprehensive RideWithGPS connector for the mcp-connectors repository with the following features:

📁 Files Created:

• packages/mcp-connectors/src/connectors/ridewithgps.ts - Main connector implementation
• packages/mcp-connectors/src/connectors/ridewithgps.spec.ts - Comprehensive test suite
• Updated packages/mcp-connectors/src/index.ts - Added connector to exports

🔧 Tools Implemented:

1. GET_CURRENT_USER - Retrieve user profile and total cycling statistics
2. GET_ROUTES - List user-owned cycling routes with pagination support
3. GET_ROUTE_DETAILS - Get comprehensive route information with track points
4. GET_TRIPS - List cycling trips/activities with performance metrics
5. GET_TRIP_DETAILS - Get detailed performance data with GPS tracks, heart rate, power, cadence
6. GET_EVENTS - List cycling events the user has participated in or created

✅ Quality Assurance:

• 9 comprehensive tests covering all tools with happy path, error handling, and edge cases
• All code quality checks passing (linting, type checking, formatting)
• Follows repository conventions for naming, structure, and patterns
• TypeScript implementation with proper type definitions for all API responses
• Authentication via API Key and Auth Token (as per RideWithGPS API requirements)
• Uses MSW for HTTP mocking following repository testing standards

🚀 Ready for Review:

The implementation is complete, tested, and committed. All changes have been successfully pushed to the remote branch.

---