Skip to main content
Glama
ryaker

day-planner-mcp

by ryaker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to day-planner-mcp

No user-submitted related servers found.

    Related Servers

    • PopUI

      kelnishi
      A
      license
      Not graded
      quality
      C
      maintenance
      A companion desktop app enabling bi-directional interaction between Claude Desktop and visual UI elements, allowing Claude to display, read from, and write to interactive interfaces while processing user events and feedback.
      5 npm
      8
      Apache 2.0

    • agentic-cal

      talalakkari
      A
      license
      Not graded
      quality
      C
      maintenance
      Unified email and calendar management with AI agent, supporting email operations, calendar availability, and time blocking via MCP tools.
      19
      Apache 2.0

    • betterbrain-all-in-summit

      adityamookerjee
      F
      license
      Not graded
      quality
      C
      maintenance
      An OAuth-secured remote MCP server (22 tools) that lets Claude, ChatGPT, and Codex search All-In Summit attendee profiles, explore the live agenda, check sessions and meetings, detect scheduling conflicts, and export a calendar. Account-changing actions are only prepared for review, with the user confirming each request in the browser before any event API call is made.
      -
    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 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: one handles specific user actions in the Day Planner UI, while the other loads the entire interactive dashboard. There is no overlap or ambiguity between them, as they serve different functions in the user workflow.

    Naming Consistency5/5

    Both tools follow a consistent snake_case naming pattern with clear verb_noun structure: 'handle_day_planner_action' and 'load_day_planner'. The naming is predictable and readable, making it easy for an agent to understand their roles.

    Tool Count2/5

    With only 2 tools, the server feels too thin for its stated purpose of day planning, which involves calendar events, emails, documents, and interactive actions. A more comprehensive set would be expected to cover operations like creating events, managing tasks, or updating priorities, rather than just handling actions and loading a dashboard.

    Completeness2/5

    The tool surface is severely incomplete for day planning. While it covers loading a dashboard and handling some UI actions, it lacks core CRUD operations for managing calendar events, emails, or documents. There are significant gaps that would cause agent failures, such as no ability to create or modify events, send emails, or organize tasks beyond the provided actions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources