Skip to main content
Glama
willpowell8

Signavio MCP Server

by willpowell8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Signavio MCP Server

No user-submitted related servers found.

    Related Servers

    • Operaton MCP

      operaton
      A
      license
      B
      quality
      B
      maintenance
      Exposes over 300 Operaton BPM REST operations as tools for AI agents to interact with the Operaton engine. It enables managing process deployments, instances, user tasks, and decision tables through natural language commands.
      100
      141 npm
      Apache 2.0

    • bw-modeling-mcp

      dnic-dev
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to read, create, and modify SAP BW/4HANA modeling objects via the internal REST API, including aDSOs, InfoObjects, transformations, DTPs, queries, and more.
      107
      288 npm
      67
      MIT

    • BTP MCP Server

      ABRANJAN07
      A
      license
      A
      quality
      C
      maintenance
      Connects AI agents to SAP BTP platform APIs for service discovery, instance management, and destination queries via natural language.
      5
      32 PyPI
      1
      MIT

    • sap-adt-mcp

      engoetz
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to work with SAP ABAP systems through the ADT REST API, supporting repository search, source code read/write, activation, syntax checks, and transport request management.
      Apache 2.0
    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

    B3.4/5.0

    Scored across 23 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific resources and actions. For example, signavio_create_dictionary_entry, signavio_get_dictionary_entry, signavio_update_dictionary_entry, and signavio_delete_dictionary_entry form a complete CRUD set for dictionary entries, with no overlap in functionality. Tools like signavio_export_model and signavio_publish_model serve unique export and publishing roles, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with the prefix 'signavio_' and snake_case throughout. The naming convention is predictable, using verbs like create, get, update, delete, move, export, publish, and search paired with specific nouns (e.g., dictionary_entry, folder, model). This uniformity enhances readability and usability for agents.

    Tool Count4/5

    With 23 tools, the count is slightly high but reasonable for a comprehensive BPM/process modeling server like Signavio. It covers multiple domains (folders, models, dictionary, search), and each tool appears to earn its place by addressing specific operations. However, it borders on being heavy, which might overwhelm agents if not well-organized.

    Completeness5/5

    The tool surface provides complete CRUD/lifecycle coverage for key domains: folders (create, get, update, move, delete), models (create, get, update, move, export, publish, revisions), and dictionary entries (create, get, update, delete, categories). It includes essential utilities like authentication, search, and root folder access, with no obvious gaps that would cause agent failures in typical workflows.

    Resources