Skip to main content
Glama
GraphiteAI

graphite-mcp

Official
by GraphiteAI
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Python
Remote

Related Servers

Alternatives to graphite-mcp

No user-submitted related servers found.

    Related Servers

    • Neo4j YASS MCP

      hdjebar
      A
      license
      Not graded
      quality
      C
      maintenance
      Production-ready MCP server for Neo4j graph databases, enabling natural language to Cypher query translation with enterprise security and async performance.
      MIT

    • sec-edgar-mcp

      guptaprakhariitr
      A
      license
      Not graded
      quality
      D
      maintenance
      Hosted MCP server that gives AI agents real-time access to SEC EDGAR filings search, 10-K/8-K reading, XBRL financial facts, and insider-trade (Form 4) alerts.
      27 npm
      1
      MIT

    • us-gov-data-mcp

      groundtruthtools
      A
      license
      A
      quality
      C
      maintenance
      MCP server for querying US federal contracts and public company financial data from USAspending and SEC EDGAR. Enables searching expiring contracts, screening companies by metrics, and retrieving financial histories.
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search, detail retrieval, relationship listing, fact retrieval, path finding, exposure analysis, and pairwise comparison. No two tools appear to do the same thing, and descriptions specify unique parameters and outputs. Even the two-entity tools (find_path and compare_entities) are differentiated by their focus on connection chains versus shared relationships.

    Naming Consistency4/5

    Most tools follow a consistent snake_case verb_noun or verb_noun pattern (search_entities, get_entity, get_relationships, get_facts, find_path, compare_entities). The only slight deviation is exposure_analysis, which uses a noun phrase rather than a verb-prefixed form, but this is minor and does not create confusion.

    Tool Count5/5

    Seven tools is an appropriate size for a specialized financial knowledge graph server. Each tool addresses a distinct query need without redundancy or bloat. This falls well within the ideal 3-15 range for a focused domain.

    Completeness5/5

    The tool surface covers the core lifecycle of knowledge graph exploration: search, retrieve entity details, list relationships, retrieve facts, trace paths, analyze exposure, and compare entities. There are no obvious missing operations for a read-only analytical server. All tools can be chained since they accept entity IDs returned by search or get operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources