Skip to main content
Glama
decode-data

twentycrm-graphql-mcp

by decode-data

Related Servers

Alternatives to twentycrm-graphql-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes GraphQL operations as typed tools for AI models, with schema exploration, validation, execution, hot reload, OAuth, prompts, MCP Apps widgets, and OpenTelemetry support.
      6
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes the Moloni ON GraphQL API to AI clients, providing a curated set of operations as typed and documented tools.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A remote MCP server that connects Claude to a Twenty CRM workspace, enabling users to interact with CRM objects (People, Companies, Opportunities, and custom objects) through schema-driven tools for querying, creating, updating, and deleting records.
      1
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that speaks GraphQL, enabling AI agents to read the schema and compose precise queries with nested relations and field selection.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A standalone MCP server that integrates with Twenty CRM to provide AI-powered CRM capabilities, enabling CRUD operations and real-time synchronization.
      202
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      MCP server for Microsoft Dynamics 365 Business Central, enabling AI assistants to perform CRUD operations, query data, and retrieve schemas via Business Central API v2.0.
      6
      10
      MIT

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clear, distinct role: schema introspection, runtime data queries/mutations, and metadata schema management. Even though execute_graphql could theoretically run introspection, the dedicated inspect_schema tool removes ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: inspect_schema, execute_graphql, execute_metadata. The repeated execute prefix for the two raw query tools also reinforces their similarity without causing confusion.

    Tool Count5/5

    Three tools is appropriately minimal for a GraphQL gateway-style MCP server. Each tool covers a distinct need (schema discovery, data access, metadata management) and none feels redundant or extraneous.

    Completeness5/5

    The combination of raw GraphQL execution for both the standard API and metadata API covers the full CRUD/lifecycle surface of a Twenty CRM workspace, while inspect_schema supports discovery. There are no obvious dead ends because arbitrary queries and mutations can fill any domain-specific gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues