mathlib-mcp
Related Servers
Alternatives to mathlib-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceProvides AI agents with version-pinned NVIDIA CUDA-Q documentation, API reference, and runnable examples via MCP, using offline SQLite full-text search. It resolves docs to match the installed cudaq package to avoid version skew.527 PyPI1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to access up-to-date library documentation through MCP tools for resolving library IDs and querying docs.55 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to search and retrieve verified, reusable engineering solutions from a shared knowledge network through MCP tools.3Apache 2.0
- AlicenseAqualityCmaintenanceIt enables AI engineers to retrieve real-time official documentation for 45+ libraries, search across frameworks, and extract code examples directly inside MCP-compatible assistants, eliminating stale training data and outdated API usage.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search code by meaning, explore codebase structure, store and query knowledge with temporal facts, and read source code through a set of MCP tools.301 npm7MIT
- AlicenseNot gradedqualityCmaintenanceEnables LLM agents to query a structured knowledge library for search, explanations, related concepts, learning paths, examples, and cross-domain references via MCP.Apache 2.0
TDQS
Scored across 4 tools
Each tool has a fairly distinct role: search_api discovers APIs by task/name, get_api_card details one exact name, get_example returns task-based example code, and check_snippet validates user code. The main overlap is between search_api and get_example, since both accept a task description and surface relevant APIs/examples, but the distinction (discovery vs. runnable example) is workable.
All four tools follow a clean, predictable verb_noun snake_case pattern (search_api, get_api_card, get_example, check_snippet). No mixed conventions or vague verbs; names clearly signal the action.
Four tools is well-scoped for a focused API-assistant server, covering the natural workflow of discover, inspect, exemplify, and validate. Each tool earns its place with no redundant surface.
The surface covers discovery, detail, examples, and static validation, which handles the core code-writing lifecycle for CuPy/nvmath-python. Minor gaps exist, such as no way to browse/list a module's full API set or check multiple snippets, but agents can work around these via search.