Skip to main content
Glama
Sign In
Pylon MCP Server

Pylon MCP Server

by mgmonteleone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Pylon MCP Server

No user-submitted related servers found.

    Related Servers

    • Zendesk MCP Server

      BusyBee3333
      A
      license
      Not graded
      quality
      D
      maintenance
      Comprehensive MCP server providing 89 tools and 13 React UI apps for complete Zendesk Support API integration, enabling ticket, user, organization, and automation management.
      MIT

    • Lodestar MCP Server

      kanlanc
      F
      license
      C
      quality
      D
      maintenance
      This is an MCP server that facilitates building tools for interacting with various APIs and workflows, supporting Python-based development with potential for customizable prompts and user configurations.
      1
      -

    • GLPI MCP Server v2

      Luizcc87
      A
      license
      C
      quality
      B
      maintenance
      MCP server for GLPI integration, providing tools for ITIL management (tickets, problems, changes, knowledge base, stats, assets, and administration) via the GLPI API.
      30
      MIT

    • jira-mcp

      ygrenzinger
      A
      license
      Not graded
      quality
      D
      maintenance
      Comprehensive MCP server for Jira integration, enabling issue management, search, comments, attachments, and project metadata through 16 tools.
      478 npm
      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

    A3.6/5.0

    Scored across 38 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose. Even similar tools like the three find_similar_issues variants are differentiated by scope (account, requestor, global). Descriptions explicitly guide selection between overlapping tools (e.g., get_issue vs get_issue_with_messages, add_tags vs update_issue).

    Naming Consistency5/5

    All 38 tools follow the exact same pattern: snake_case with a 'pylon_' prefix and a verb_noun structure. Verbs are consistently used (create, get, update, delete, search, add, remove, snooze, link, unlink). No mixing of camelCase or other conventions.

    Tool Count3/5

    At 38 tools, this is a large surface area, but each tool serves a specific function for a feature-rich support platform. The count is on the higher end of acceptable; some tools like pylon_get_issue and pylon_get_issue_with_messages could arguably be merged. Overall, it's justified by the breadth of entities managed.

    Completeness4/5

    The tool set provides full CRUD for issues, plus extensive operations for contacts, teams, knowledge bases, tags, attachments, and external integrations. Missing: update/delete for contacts and teams, but these are less critical. The search variants cover filtering needs well. Minor gaps exist but don't severely hinder common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources