Skip to main content
Glama
menshikovs

R Knowledge MCP

by menshikovs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to R Knowledge MCP

No user-submitted related servers found.

    Related Servers

    • MCPyDoc

      amit608
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides real-time access to Python package documentation, source code, and symbol search to prevent AI hallucinations.
      55 PyPI
      7
      MIT

    • dev.augments/mcp

      ShreyaMoreno7147
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code and other compatible clients to fetch real-time npm package and framework documentation, TypeScript signatures, code examples, version diffs, migration guides, error diagnoses, package comparisons, and dependency scans. It delivers context-aware, intent-formatted results with caching and multi-source integration from npm and GitHub.
      MIT

    • FreshStack MCP

      Jayesh01323
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to inspect project dependency versions, resolve version constraints, and audit Python code for deprecated or incompatible APIs using authoritative evidence and local AST analysis.
      3
      6 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.8/5.0

    Scored across 32 tools

    Disambiguation3/5

    The set has many narrowly targeted but similar-sounding tools, such as get_function_docs/get_shiny_docs/get_visualization_docs/get_quarto_docs and the several analyze_* static inspectors. Descriptions differentiate them, but overlapping doc-fetching paths like get_package_knowledge vs get_context7_docs vs get_package_agent_guidance create real misselection risk.

    Naming Consistency5/5

    All tool names use snake_case with a consistent verb_noun pattern (get_, check_, analyze_, build_, validate_, list_). The qualifiers are descriptive and predictable despite the length of some names.

    Tool Count2/5

    32 tools is above the rubric's heavy threshold, with several closely related variants for docs, static analysis, and prompt operations. The broad R-knowledge scope partly justifies it, but the surface feels segmented rather than tightly scoped.

    Completeness4/5

    Coverage spans package discovery, metadata, dependencies, version/compatibility checks, docs, agent guidance, Shiny/Quarto/visualization workflows, and prompt lifecycle. Minor gaps remain, such as discovering function aliases or listing package functions, but core knowledge workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources