Skip to main content
Glama
Pd011161

OMOS-MCP

by Pd011161
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to OMOS-MCP

No user-submitted related servers found.

    Related Servers

    • Document QA MCP Server

      parikshith49
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables users to query documents from Google Drive using AI assistance, providing tools for searching vector databases and generating answers based on document content.
      -

    • google-drive-rag-mcp

      asamiile
      A
      license
      A
      quality
      D
      maintenance
      A local MCP server that enables LLMs to securely search and read files within designated Google Drive folders. Supports Google Docs, Google Sheets, PDFs, and plain text with strict folder-scoping via service account authentication.
      4
      MIT

    • mise-en-space

      spm1001
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that enables LLMs to search, fetch, and act on Google Workspace (Drive, Gmail, Docs, Sheets, etc.) with rich, one-call results and file deposits to disk, reducing context usage.
      3
      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

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: omos_index provides the full index, omos_search performs full-text search with optional filters, omos_refresh rebuilds the index, and omos_read reads file content. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tools follow a consistent 'omos_<verb>' pattern (index, search, refresh, read). The naming is predictable and uniform, making it easy for an agent to understand the action each tool performs.

    Tool Count5/5

    With 4 tools, the set is well-scoped for a drive retrieval server. Each tool addresses a necessary function (listing, searching, refreshing, reading) without being too few or excessive. The count matches the domain's core operations.

    Completeness5/5

    The tool surface covers the full read lifecycle for the OMOS drive: obtaining the index, searching, refreshing for updates, and reading file content. No obvious gaps exist for a retrieval-focused server; all necessary operations are present.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources