Skip to main content
Glama
mikko-bautista-113580

Creatio Case Toolkit MCP Server

by mikko-bautista-113580
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Creatio Case Toolkit MCP Server

No user-submitted related servers found.

    Related Servers

    • IFRC GO MCP Server

      jmargutt
      F
      license
      Not graded
      quality
      F
      maintenance
      Read-only MCP server for IFRC GO data, secured with Microsoft Entra ID OAuth/JWT, exposing datasets as MCP tools with rate limiting and PII filtering.
      -

    • servicios-mcp

      dromerotrans
      A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server that exposes SAP Business One Service Layer and Cisco CCWR contract search APIs for querying sales orders, delivery notes, business partners, and service contracts, without modifying data.
      MIT

    • querygate

      Waddles1729
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a read-only SQL MCP server with guard rails including table visibility, column masking, row and time caps, and an audit trail, enabling safe database access for agents without granting full write permissions.
      MIT

    • mcp-sqlserver-readonly

      gbfeliped
      A
      license
      Not graded
      quality
      D
      maintenance
      Read-only SQL Server MCP server enabling safe database queries, table listing, and schema inspection with built-in security protections.
      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.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing allowed entities, querying records, and fetching a single record. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tools follow the same verb_noun pattern with the consistent 'creatio_' prefix: list_allowed_entities, query_records, get_record. The naming is uniform and predictable.

    Tool Count5/5

    With 3 tools, the set is within the typical well-scoped range. Each tool serves a necessary role in the read-only OData use case, with no redundant or missing infrastructure.

    Completeness5/5

    For a read-only OData server, the tool surface is complete: it covers entity discovery, record querying, and single-record retrieval. No obvious gaps exist for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources