Skip to main content
Glama
inboxd
by 47star

Related Servers

Alternatives to inboxd

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to search a shared local archive of selected sessions, notes, and connected sources, returning source-backed context and citations through read-only MCP access.
      7
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI assistants to securely search multiple mailboxes, reconstruct email threads, and inspect attachments through read-only tools without altering mailbox state.
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to query a personal message archive via MCP tools, including searching messages, resolving people, and retrieving conversation context.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search and read archived Telegram and WhatsApp messages and attachments through a Streamable HTTP MCP endpoint, with scoped credentials, per-account/chat permissions, full-text search, and extracted file text.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query your complete local conversation history and knowledge graph over MCP, including full-fidelity transcripts, search, and typed, dated entity relationships.
      AGPL 3.0

    TDQS

    B3.4/5.0

    Scored across 11 tools

    Disambiguation3/5

    The core read path (search_messages, get_message, get_recent_records, get_changes) is well separated and descriptions even cross-reference each other to steer selection. However, sync_status and list_sources both return collector health/coverage counts, get_attachments and get_attachment_text are two ends of one workflow with the latter's description giving no hint of where its input comes from, and the Slack-specific get_slack_thread overlaps conceptually with the generic get_conversation.

    Naming Consistency4/5

    Nearly all tools follow a clear verb_noun snake_case pattern (search_messages, get_message, list_sources, get_slack_thread). The only deviation is sync_status, a noun phrase with no verb, plus get_changes which is mildly vague but consistent in style.

    Tool Count5/5

    11 tools is well within a healthy range for a multi-source archive covering mail, calendar, tasks, notes, reminders, Slack and work items. Each tool maps to a distinct retrieval need rather than padding the surface.

    Completeness4/5

    Read coverage is strong: search, single-record read, conversation browsing, change feed, source discovery, Slack channels/threads, and attachment text. Gaps are the near-absence of write/lifecycle operations (compose, mark read, update) and no attachment binary/download retrieval, though the descriptions imply a deliberately read-only local archive.