Skip to main content
Glama
denis-samatov

yandex-workspace-mcp

by denis-samatov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to yandex-workspace-mcp

No user-submitted related servers found.

    Related Servers

    • yandex360-mcp

      pa1ch
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that enables AI assistants to interact with Yandex 360 organization services, currently supporting Yandex Wiki for reading, editing, and searching pages.
      MIT

    • PMCP - Perfect Model Context

      NoobyNull
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      A comprehensive production-ready MCP server with AI integration, plugin management, and web-based administration. Features multi-database support, RAG capabilities, SSH/SFTP access, and a built-in plugin hub for managing the MCP ecosystem.
      -

    • Skills MCP AD

      DevSkillsIT
      A
      license
      Not graded
      quality
      C
      maintenance
      A production-ready MCP server that enables AI assistants to manage enterprise Active Directory environments through 45 specialized tools for users, groups, and GPOs. Its multi-client architecture allows for the secure management of multiple AD domains from a single codebase using natural language commands.
      3
      MIT

    • DevForge-MCP

      Sanket2329
      A
      license
      Not graded
      quality
      A
      maintenance
      A production-ready MCP server that enables AI assistants to intelligently understand, analyze, edit, navigate, and review software projects with multi-workspace support, Git integration, and semantic search.
      1
      MIT

    • serverless-wiki-on-aws MCP

      coni524
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that provides secure access to a serverless Markdown wiki on AWS, enabling AI assistants to read, search, and edit pages with space-level permission checks and Bedrock-powered semantic search.
      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

    B3.2/5.0

    Scored across 8 tools

    Disambiguation3/5

    Search and wiki_search overlap, with wiki_search being a subset of the generic search. Fetch could be confused with the specific getters (disk_get_metadata, wiki_get_page), though its ID-based approach differs slightly. Other tools are clearly distinct.

    Naming Consistency3/5

    The disk_* and wiki_* prefixes create a consistent sub-pattern, but generic tools like search and fetch break the pattern. Naming is readable and mostly predictable, but not fully uniform.

    Tool Count5/5

    With 8 tools covering two domains (Disk and Wiki), the count is well-scoped and appropriate for the server's purpose. Every tool has a clear role, and the number is within the ideal 3-15 range.

    Completeness3/5

    The tools cover search, reading, and retrieval well, but lack any write operations (create, update, delete) for both Disk and Wiki. This is a notable gap if the workspace is meant for more than read-only access, though it may be intentional for a search-focused MCP.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources