Skip to main content
Glama
xuzhougeng

ScientificFigureLibrary

by xuzhougeng

Related Servers

Alternatives to ScientificFigureLibrary

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for AI-assisted research: paper ingestion, semantic search, citation graph traversal, cross-domain knowledge synthesis, and workflow automation.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      MCP server for searching research grants across NSF (US), ERC (EU), and KRF/NRF (Korea) via a unified interface. NIH excluded—covered by existing connectors.
      3
      7 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Comprehensive MCP server for academic research workflows, enabling paper searching across multiple sources, manuscript processing with citation placeholders, search caching, and citation export.
      11
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A unified MCP server for academic paper discovery, citation exploration, and research intelligence workflows over multiple scientific knowledge sources.
      7
      1
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      MCP server that integrates a 1200-paper RAG database with six tools to support research workflows across stages like hypothesis, experiment, statistics, and writing. It routes requests to specialized skills and real-time frontier searches to provide evidence-grounded research mentoring.
      6
      Apache 2.0

    TDQS

    C2.9/5.0

    Scored across 56 tools

    Disambiguation3/5

    The plan_/apply_ pairs are distinct in intent, but the multiple preview and confirm variants (preview, preiew_exact, preview_exact_headless, preview_working_revision, confirm_selection, confirm_selection_headless) can easily be confused. Several plan tools also share the exact same generic description, leaving the tool name to carry the full disambiguation burden.

    Naming Consistency4/5

    The figure_library_ prefix plus the consistent plan_/apply_ pairing creates a strong naming pattern. A few noun-headed names like template_history, source_status, and github_auth_status, plus bare verbs like open and describe, deviate slightly from strict verb_noun naming but not enough to mislead.

    Tool Count1/5

    With 56 tools, the surface is extremely large. The many plan/apply pairs and App-only/headless variants roughly double the number of operations, making the server far heavier and harder to navigate than is appropriate even for a complex scientific figure workflow.

    Completeness3/5

    The core lifecycle is well represented: binding, search, working revisions, review gates, publishing, restoring, exporting, and GitHub/provider integrations. Notable gaps remain, however: there is no clear unpublish/retract operation for a Published release and no agent-facing way to author or modify review findings.

    Maintenance

    ActivityActive
    ResponsivenessResponsive