Skip to main content
Glama
amirmcs

Pega MCP Server

by amirmcs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Pega MCP Server

No user-submitted related servers found.

    Related Servers

    • CAP V2 Case MCP

      aryansiddhantsap-ctrl
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage SAP Sales Cloud V2 cases through MCP tools, supporting listing, retrieving, creating, and updating case records.
      -

    • ParcelPilot MCP Server

      PraneethGoud04
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to retrieve customer, order, ticket, policy, and agreement information, and to prepare or execute state-changing support actions like escalations and follow-ups with confirmation and access control.
      -

    • invoiceguard

      JoshilFernandes
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible agents such as Claude Desktop and Cursor to process invoices, list pending reviews, retrieve case details and risk signals, decide approvals or rejections, access masked vendor master data, and view AP dashboard metrics while resuming paused LangGraph workflows.
      MIT

    • MCP Integration Server

      henrymclane09
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables agents to interact with Salesforce, Atlassian (Jira/Confluence), and Supabase through standardized tools and resources. Provides both read-only access for querying data and write operations for managing records across these enterprise platforms.
      1
      -
    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

    A3.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: attaching documents, fetching a single case, discovering actions, listing cases, retrieving view metadata, and submitting actions. The descriptions clearly differentiate between case retrieval, action management, and document handling functions.

    Naming Consistency5/5

    All tools follow a perfect verb_noun pattern with consistent snake_case naming: attach_document_to_case, get_case, get_case_actions, get_cases, get_case_views, and submit_case_action. The naming convention is predictable and follows the same structure throughout.

    Tool Count5/5

    Six tools is well-scoped for a case management system, covering core operations like CRUD for cases, action discovery/execution, document attachment, and view retrieval. Each tool earns its place without being overwhelming or insufficient.

    Completeness4/5

    The toolset provides excellent coverage for case lifecycle management with get/create/update (via submit_action) operations, action discovery/execution, and document attachment. Minor gaps include no explicit case creation tool (though submit_action might cover this) and no case deletion capability, but agents can work around these limitations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources