Skip to main content
Glama
PhilflowIO

dav-mcp

by PhilflowIO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to dav-mcp

No user-submitted related servers found.

    Related Servers

    • razberri MCP Server

      nathanasbury
      F
      license
      Not graded
      quality
      D
      maintenance
      A privacy-first, local-first MCP server that provides 15 ADHD/second-brain tools for capturing, prioritizing, and resurfacing tasks with context from calendar, mail, and messages.
      1
      -

    • calendar-mcp

      p-w-4-z
      A
      license
      Not graded
      quality
      F
      maintenance
      Provider-agnostic CalDAV calendar MCP server that connects any CalDAV calendar to AI assistants, enabling calendar operations like listing, creating, updating, and deleting events.
      AGPL 3.0

    • Anneal MCP Server

      imsovikde
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants such as Claude, ChatGPT, Gemini, and Cursor to a unified personal operating system, enabling them to track habits and streaks, manage task lifecycles and deadlines, and build syllabi and flashcard decks with FSRS-5 spaced-repetition scheduling through 102 typed tools. All reads and writes run against a single append-only event ledger over an OAuth 2.1-secured Streamable HTTP endpoint.
      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.9/5.0

    Scored across 27 tools

    Disambiguation5/5

    Each tool targets a distinct operation: list vs query vs multi-get vs create/update/delete, and raw update variants are explicitly differentiated from their field-based counterparts. Even overlapping tools like list_events and calendar_query are clearly scoped with warnings and usage guidance.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (list_, create_, update_, delete_, *_query, *_multi_get). The lone exception is make_calendar instead of create_calendar, which breaks the otherwise uniform create_* convention.

    Tool Count3/5

    At 27 tools, the surface is heavy but defends its size by covering three distinct resource domains (calendars, todos, contacts) with full CRUD plus query and batch operations. It sits just above the 16-25 'heavy' band, yet all tools serve a concrete purpose rather than being redundant.

    Completeness4/5

    The calendar, event, todo, and contact domains have strong lifecycle coverage (list/query/get/create/update/delete), plus freebusy and raw updates. The main gap is the lack of addressbook creation/update/deletion—only list_addressbooks exists—but this is a minor limitation for the core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources