Strava MCP Server

# Contributing to Strava MCP Server Thank you for your interest in contributing! ## Getting Started 1. Fork the repository 2. Clone your fork: `git clone https://github.com/YOUR_USERNAME/strava-mcp-server.git` 3. Create a branch: `git checkout -b feature/your-feature-name` 4. Make your changes 5. Test your changes thoroughly 6. Commit with clear messages: `git commit -m "Add feature: description"` 7. Push to your fork: `git push origin feature/your-feature-name` 8. Open a Pull Request ## Development Setup ```bash npm install npm run build npm run watch # For development with auto-rebuild ``` ## Code Style - Use TypeScript for type safety - Follow existing code patterns - Add comments for complex logic - Keep functions focused and single-purpose ## Testing Before submitting a PR: 1. Ensure the code builds without errors: `npm run build` 2. Test with a real Strava account 3. Verify all tools work as expected ## Adding New Tools When adding new Strava API endpoints: 1. Add the tool definition in the `ListToolsRequestSchema` handler 2. Implement the handler in the `CallToolRequestSchema` switch statement 3. Update the README.md with the new tool documentation 4. Test the endpoint thoroughly ## Pull Request Guidelines - Provide a clear description of the changes - Reference any related issues - Ensure code builds successfully - Update documentation as needed ## Questions? Open an issue for discussion before starting major changes.