mountainproject
Related Servers
Alternatives to mountainproject
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code and other MCP clients to run live JQL and CQL searches and read Jira Cloud issues, comments, and Confluence Cloud pages on your own machine, with no local index and nothing cached outside those products. Access is read-only and scoped to your own Atlassian account permissions.MIT
- AlicenseAqualityDmaintenanceProvides ripgrep search capabilities to MCP clients like Claude, enabling high-performance text searches across files on your system.56 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables read-only querying of an Obsidian knowledge base through MCP tools and resources, including full-text search, node and link retrieval, related-note traversal, and pathfinding between concepts.1-
- FlicenseNot gradedqualityCmaintenanceEnables full-text search over personal notes, note and tag management, and live weather lookups through MCP tools, resources, and prompts, usable from clients like Claude Desktop or a custom agent loop.-
- AlicenseNot gradedqualityDmaintenanceEnables querying Jira issues using JQL and creating new issues programmatically via natural language.708 npmMIT
- AlicenseBqualityDmaintenanceProvides ripgrep search capabilities to MCP clients like Claude, allowing high-performance text searches across files on your system.53,723 npm79MIT
TDQS
Scored across 10 tools
Most tools are clearly distinguished by resource and action (search, get_route, get_area, find_routes, resolve_id, tick operations). Minor overlap exists between mp_search and mp_find_routes (both find routes, though in different contexts) and between mp_fetch_ticks and mp_list_ticks (list auto-fetches, fetch forces refresh), but descriptions clarify the boundaries.
All tools share the mp_ prefix and most follow verb_noun structure (mp_search, mp_get_route, mp_set_session, mp_fetch_ticks, mp_list_ticks). Two names deviate: mp_auth_status (noun phrase) and mp_tick_stats (noun phrase), which break the pattern slightly but remain predictable and readable.
Ten tools is well-scoped for a climbing data and personal tick-list server. Each tool covers a distinct aspect of the domain—searching, retrieving, resolving IDs, session management, and tick lifecycle—without unnecessary redundancy or bloat.
The tool surface covers the core read-only workflows for Mountain Project: searching and fetching routes/areas, resolving URLs to IDs, and managing personal tick data (auth, session, refresh, list, stats). No obvious dead ends; the main missing operations like creating/deleting ticks or routes are external to the API's likely scope.