Skip to main content
Glama
sciple-idp

Sciple Platform MCP Server

Official
by sciple-idp

Related Servers

Alternatives to Sciple Platform MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      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
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to interact with the SCF Controls Platform for security compliance, including browsing controls, tracking implementation, managing evidence, assessing risks, and monitoring vendors via natural language.
      196
      333 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-capable AI agents to safely read and write ServiceNow records via the Table API, including querying, creating, updating records, running server-side scripts, and triggering CI/CD tests and scans.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to fully control a Tracecat SOAR platform instance through natural language, managing workflows, actions, cases, secrets, tables, schedules, graphs, and more.
      94
      13 npm
      4
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage components and pages on the Journey/SameUp CMS through the CMS REST API, including listing, retrieving, and creating components with automatic authentication.
      -

    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 issues