telegram-bot-framework-mcp
Related Servers
Alternatives to telegram-bot-framework-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to search pinned robotics code and reusable task findings across frameworks, inspect provenance and requirements, and prepare supported upstream sources via recipes without executing robot code.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query a locally analyzed repository for architecture, symbols, dependencies, impact, data lineage, and code context through read-only tools. It uses a prebuilt index within a fixed repository scope and does not call a model.45 PyPI1Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables clients to retrieve real-time framework documentation for any npm package, returning TypeScript types, prose, and code examples with intent-aware formatting, plus version migration guidance, error diagnosis, package comparison, and dependency scanning.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to fetch current, version-accurate library documentation at request time instead of relying on training memory, with search for answering questions and full-fidelity retrieval of pages or specific declarations. Supports bare or module-path library names, version pinning, and disambiguation when names collide.47 npmMIT
- AlicenseAqualityDmaintenanceProvides AI assistants with up-to-date documentation for popular libraries and frameworks, enabling them to generate more accurate code using less common or newly released libraries.536MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI models to fetch GitHub repository information, read file contents, and search local documentation.-
TDQS
Scored across 17 tools
Most tools target clearly distinct facets (git refs, symbols, files, code search, README, examples, guide, gotchas), so an agent can usually pick correctly. The overlap is mild: `ask` deliberately subsumes `search_guide`, `get_gotchas`, `list_symbols` and README lookup, and `list_doc_sections`/`list_guide_sections` are two similar-looking pairs, but the docs explicitly frame `ask` as an orchestrator so the boundaries are explained.
Names follow a clear verb_noun convention (list_refs, get_symbol, find_subclasses, search_code, get_guide_section) across the whole set. Only two deviations stand out: the noun-only `framework_version` and the verb-only `ask`, which are minor and readable.
17 tools is on the heavy side for what is essentially a read-only repo/docs browser, and several doc-navigation tools (list_doc_sections/get_doc_section, list_guide_sections/get_guide_section, search_guide) could arguably be consolidated. Each still maps to a real facet of the repo, so it is heavy rather than bloated.
The surface covers versioning, API diffs, refs, symbol/subclass lookup, file listing and reading, code search, README, examples, the curated guide and pitfalls, and even an orchestrator entry point — a solid lifecycle for a documentation/reference server. Minor gaps remain: no full-text README search, no example-file search, and no way to enumerate all symbols in one call.