Skip to main content
Glama
Sign In
Sciple Platform MCP Server

Sciple Platform MCP Server

Official
by sciple-idp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Sciple Platform MCP Server

No user-submitted related servers found.

    Related Servers

    • Splunk SOAR MCP Server

      Ewiges-M
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to operate a Splunk SOAR instance headlessly via its REST API, supporting container triage, playbook authoring and execution, and asset management.
      2
      MIT
    • Statuser MCP Server

      Statuser MCP Serverofficial

      statuser-cloud
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to manage a Statuser account directly, including monitoring servers, handling incidents, publishing status page updates, and configuring notifications.
      92
      959 npm
      24
      MIT

    • Octopus Deploy Official MCP

      Ananya0553
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to inspect, query, and diagnose deployments, releases, runbooks, tasks, tenants, and infrastructure inside an Octopus instance through its APIs. Supports read-only and write-gated modes, toolset selection, and structured REST access for both interactive use and automation.
      529 npm
      MIT

    • Octopus Deploy Official MCP

      AnkitMoon886
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to inspect, query, and diagnose problems in a continuous delivery platform, and to perform release, deployment, runbook, task, tenant, and related operational actions with configurable read-only or write access.
      529 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

    B3.4/5.0

    Scored across 60 tools

    Disambiguation4/5

    Most tools are clearly separated by resource and action, and the athena_*/db_* prefixes help partition query tools. The main ambiguity comes from dual ticket paths (create_ticket vs create_project_ticket, get_ticket vs get_project_ticket, list_tickets vs list_project_tickets), but the descriptions are explicit about which to use.

    Naming Consistency3/5

    The dominant pattern is verb_noun (list_dashboards, create_environment, update_service), but several tools put the domain first (athena_run_query, db_query, athena_cancel) or use 'athena_history' without a verb. Add_panel/add_cell also deviate from the create_* convention, making the set readable but inconsistent.

    Tool Count1/5

    60 tools is an extreme count for a single MCP server and bundles many unrelated domains—dashboards, Athena, SQL, AWS resources, projects, tickets, runbooks, and services. Even if each tool is individually useful, the combined surface is too heavy for an agent to navigate efficiently.

    Completeness3/5

    Several domains have solid CRUD coverage, especially tickets, services, dashboards, and runbook cells, but there are notable gaps: no panel update, no runbook update/delete, no project update/delete, no environment group update/delete, and no API to discover datasource_id (needed by add_panel). There is also no user lookup tool, which would help resolve assignee_user_id.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources