Skip to main content
Glama
Sign In
oase-mcp

oase-mcp

Official
by oase-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to oase-mcp

No user-submitted related servers found.

    Related Servers

    • OpenClaw MCP Server

      anderslaurent
      A
      license
      Not graded
      quality
      A
      maintenance
      Bridges Claude.ai and Claude Desktop to self-hosted OpenClaw AI assistants through an OAuth 2.1-secured HTTP endpoint. Enables sending chat messages, tracking long-running tasks, checking gateway health, and routing requests across multiple isolated instances from a single connection.
      1,169 npm
      MIT

    • OpenClaw MCP Server

      PabloBerger857
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude clients to securely connect to self-hosted OpenClaw assistants over OAuth 2.1, sending chat messages, checking gateway health, and queuing or monitoring long-running tasks across multiple named instances with per-instance authentication and isolation.
      1,169 npm
      MIT

    • OpenClaw MCP Server

      hannahito
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude.ai and Claude Desktop to securely connect to self-hosted OpenClaw AI assistants via OAuth 2.1, sending chat messages, checking gateway health, and queuing, polling, or cancelling long-running tasks. Supports orchestrating multiple OpenClaw gateway instances (such as prod, staging, and dev) from a single authenticated bridge.
      1,169 npm
      MIT

    • OpenClaw MCP Server

      daikiishii96
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude clients to securely connect to self-hosted OpenClaw assistants via OAuth 2.1, send synchronous or asynchronous chat messages, check gateway health, and manage long-running tasks. It also supports routing requests across multiple isolated gateway instances.
      1,169 npm
      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.2/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: login steps are separated (start/finish vs. direct token exchange), messaging vs. posts are explicit (send_message vs. send_post), and read/update/delete operations are mapped to specific resources (messages, posts, media). There is no ambiguity between tools.

    Naming Consistency4/5

    Tool names mostly follow a verb_noun pattern (send_message, update_post, read_media), with consistent prefixes for CRUD operations. Minor deviations exist like promise_login_start/finish and login_with_promise, but they are still intuitive and do not break the overall consistency.

    Tool Count5/5

    16 tools is well-scoped for a chat/oase platform covering authentication, messaging, posts, reactions, media retrieval, and profile management. Each tool has a clear role and none feel redundant; the count is appropriate for the domain.

    Completeness4/5

    The tool set covers the primary workflows: messaging (send, read, update, delete), posts (publish, read, update, delete), reactions, media download, and authentication. Minor gaps exist, such as no explicit 'leave oase' tool and no direct attachment uploading (only media download), but these are not critical to core agent tasks and can be worked around.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Resources