Skip to main content
Glama
SkyPorch

Daykeeper MCP

Official
by SkyPorch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Daykeeper MCP

No user-submitted related servers found.

    Related Servers

    • xmatters-mcp

      robertsmieja
      A
      license
      C
      quality
      B
      maintenance
      Enables MCP clients to interact with the current xMatters REST API over stdio, covering people, devices, groups, on-call schedules, events, incidents, workflows, services, integrations, and subscriptions. It is read-only by default and requires explicit operator opt-in plus per-call confirmation for mutations.
      179
      Apache 2.0

    • waylucid-agent-mcp

      brendendearie
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables role-gated management of ops desk contacts, cases, and tasks via MCP, with tool schemas and availability filtered per role to enforce permission boundaries, over stdio or Streamable HTTP.
      MIT

    • MAGDA-MCP

      DionysusDWI
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to connect to a running MAGDA instance over stdio and access its native composition tools, resources, and resource templates, while providing instance discovery, fixed-instance connection, credential recovery, diagnostics, and compatibility checks.
      MIT

    • mcp-gateway

      KaryawanSurga
      A
      license
      Not graded
      quality
      B
      maintenance
      Aggregates many MCP servers behind one local endpoint with namespaced tools, profiles, policy, budgets, audit logs, and a dashboard over stdio or HTTP.
      33 npm
      1
      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.7/5.0

    Scored across 8 tools

    Disambiguation4/5

    The tools are mostly distinct: tenants_list vs tenants_get, and the flows cluster (flows_list, flows_get, flow_versions_get) are separated by descriptions noting revision vs exact immutable version. The flows_get/flow_versions_get pair is the only possible confusion point, but the descriptions clarify the boundary.

    Naming Consistency4/5

    Almost all tools follow a consistent daykeeper_<resource>_<action> snake_case pattern (tenants_list, tenants_get, flows_list, operations_get, etc.). The lone outlier is daykeeper_capabilities, which is a noun without an action verb, a minor deviation.

    Tool Count5/5

    Eight tools is a well-scoped size for an inspection/management surface. Each tool maps to a specific resource read and there is no obvious redundancy or bloat.

    Completeness3/5

    The surface is entirely read-only: there is no create/update/delete/execute tool despite capabilities referencing execution gates, and operations only has a get (no list/cancel), email channels only a get. Core inspection is covered but the lifecycle is one-sided with notable gaps.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources