Skip to main content
Glama
cmsappian123-bit

Appian MCP Server

by cmsappian123-bit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Appian MCP Server

No user-submitted related servers found.

    Related Servers

    • arcpro-mcp

      qiobn
      A
      license
      A
      quality
      D
      maintenance
      Enables natural language control of live ArcGIS Pro sessions through the Model Context Protocol, allowing inspection of projects, layers, and attributes, and execution of geoprocessing tasks.
      25
      2
      MIT

    • Pega DX MCP Server

      marco-looy
      A
      license
      B
      quality
      C
      maintenance
      Transforms complex Pega Platform interactions into intuitive, conversational experiences by exposing Pega DX APIs through the standardized Model Context Protocol, enabling AI applications to interact with Pega through natural language.
      67
      20
      21
      Apache 2.0

    • spark-mcp

      feamster
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables users to access, search, and analyze Spark Desktop meeting transcripts and emails through natural language via the Model Context Protocol.
      11
      -

    • aha-mcp

      sergiolopezgsiot
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language interaction with Home Assistant for managing entities, automations, services, and dashboards via the Model Context Protocol.
      189
      MIT

    • New Relic MCP Server

      thrashy
      A
      license
      B
      quality
      B
      maintenance
      Enables natural language access to New Relic for monitoring, querying, and managing dashboards, entities, alerts, and deployments via the Model Context Protocol.
      52
      8
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct action: two creation operations for different request types and two retrieval operations for different data sources. Descriptions clearly differentiate their purposes, leaving no ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: create_labelling_request, create_procurement_request, get_appian_suppliers, get_records. No mixing of conventions.

    Tool Count5/5

    Four tools is well-scoped for an Appian integration server, covering essential creation and retrieval operations without unnecessary bloat or deficiency.

    Completeness4/5

    The tool set covers the primary actions of submitting requests and fetching data, but lacks update/delete capabilities or status tracking for submitted requests, which could be considered minor gaps for full workflow coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources