Skip to main content
Glama
takeokunn

Slite MCP Server

by takeokunn

Related Servers

Alternatives to Slite MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      F
      maintenance
      A Model Context Protocol server that enables AI assistants to read, write, and manipulate notes in your Obsidian vault through a standardized interface.
      5
      2,545 npm
      4
      ISC
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with Notion's API for reading, creating, and modifying Notion content through natural language interactions.
      -
    • F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server enabling AI assistants to interact with TriliumNext notes, providing tools for creating, searching, reading, and updating notes in your knowledge base.
      4
      2
      -
    • A
      license
      A
      quality
      C
      maintenance
      A server implementing Model Context Protocol that enables AI assistants to interact with Slack API through a standardized interface, providing tools for messaging, channel management, user information retrieval, and more.
      11
      110
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol server implementation that enables AI assistants to interact with Slack workspaces, allowing them to browse channels, send messages, reply to threads, add reactions, and retrieve user information.
      9
      10 npm
      2
      Apache 2.0

    TDQS

    B3.2/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct action on a specific resource (note, user, group, custom content). Tools like archive_note, flag_note_as_outdated, and verify_note have clearly different purposes. The only potential overlap is between list_notes and search_notes, but their descriptions indicate different filtering logic (list vs. search query), and they serve separate use cases.

    Naming Consistency5/5

    Tool names consistently follow a verb_noun pattern (e.g., create_note, get_note, update_note, delete_note, list_notes, search_notes, archive_note, flag_note_as_outdated, verify_note). Even compound names like update_note_owner and update_tile maintain consistency. The deprecated custom content tools also follow the pattern. There is no mixing of conventions or vague verbs.

    Tool Count4/5

    With 21 tools, the server is slightly above the ideal range (3-15) but remains well-scoped for a comprehensive note management platform. Each tool adds clear value for CRUD operations, AI interaction, user/group retrieval, and advanced note actions (e.g., change owner, update tiles). No tool feels redundant, though the deprecated custom content tools could be removed for a leaner set.

    Completeness4/5

    The tool surface covers the full note lifecycle (create, read, update, delete, archive, flag as outdated, verify) and includes useful extras like AI question answering, note owner transfer, and tile editing. However, it lacks tools for creating or managing groups and users (only search/get exist), and there is no tool for bulk operations or note sharing. The deprecated custom content tools are an oddity but do not affect core functionality.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues