bike-size-by-rider-height — Tournride — Camino de Santiago bike rental MCP Resource
bike-size-by-rider-height
is one of 6 resources on the
Tournride — Camino de Santiago bike rental
MCP server. Connect the server and your client can attach it as context.
by client
How to attach bike-size-by-rider-height from your client
- Claude Code Tournride — Camino de Santiago bike rental Resource/bike-size-by-rider-height run in your project directory
- Claude Desktop Tournride — Camino de Santiago bike rental Resource/bike-size-by-rider-height ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Tournride — Camino de Santiago bike rental Resource/bike-size-by-rider-height ~/.cursor/mcp.json
- VS Code Tournride — Camino de Santiago bike rental Resource/bike-size-by-rider-height .vscode/mcp.json
- Zed Tournride — Camino de Santiago bike rental Resource/bike-size-by-rider-height ~/.config/zed/settings.json
- Windsurf Tournride — Camino de Santiago bike rental Resource/bike-size-by-rider-height ~/.codeium/windsurf/mcp_config.json
- Cline Tournride — Camino de Santiago bike rental Resource/bike-size-by-rider-height ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Tournride — Camino de Santiago bike rental Resource/bike-size-by-rider-height ~/.gemini/settings.json
- Grok Tournride — Camino de Santiago bike rental Resource/bike-size-by-rider-height .mcp.json (in your project root)
- ChatGPT Tournride — Camino de Santiago bike rental Resource/bike-size-by-rider-height Settings → Connectors → Advanced → Developer mode
- Claude.ai Tournride — Camino de Santiago bike rental Resource/bike-size-by-rider-height Settings → Connectors → Add custom connector
- LangChain Tournride — Camino de Santiago bike rental Resource/bike-size-by-rider-height pip install langchain-mcp-adapters
Other resources on this server
Tournride — Camino de Santiago bike rental also offers 1 prompt — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 3 October 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.