Skip to main content
Glama
openserverless-mcp

openserverless-mcp

Official

Related Servers

Alternatives to openserverless-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables autonomous agents to securely access and manage virtual file systems, records, schemas, SQL and Mongo queries, and RAG search through scoped MCP tools, while supporting binary transfers via presigned S3 recipes.
      PolyForm Noncommercial 1.0.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP-capable agents to manage Meshive GPU Cloud resources, including account, workspaces, pods, storage, GPUs, templates, serverless deployments, tasks, assets, machines, and billing history.
      44
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to access connected services and accounts through one MCP/REST interface, run scheduled or event-triggered plain-English jobs, and securely manage notifications, approvals, credentials, and model routing.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides one self-hosted MCP endpoint that lets agents call tools drawn from many integrations — remote MCP servers, OpenAPI or GraphQL APIs, published skill packs, and uploaded scripts — with per-user sign-in, tool allow/block filtering, and optional code mode. Agents can also manage the integrations themselves, while secrets stay with Cloudflare and never reach the model.
      MIT

    TDQS

    A3.7/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools are clearly separated by integration target or resource: Milvus, S3, Postgres, Redis, MongoDB, secret status/bind/unbind, invoke, and auth setup. The main overlap is between action_add_secret and secret_bind, which both attach existing .env secrets to endpoint contexts; their descriptions clarify single vs. multi-endpoint scope, but the boundary could still cause misselection.

    Naming Consistency3/5

    The action_ and secret_ prefixes create a readable grouping, and action_add_* is used consistently for integration setup. However, action_new and action_requirements break the verb_noun pattern, and action_add_secret sits awkwardly alongside the secret_* family, making the naming somewhat mixed though still understandable.

    Tool Count5/5

    With 13 tools, the server is well scoped for an OpenServerless configuration platform. Each tool covers a distinct setup, invocation, secret-management, or auth task, and there are no obvious filler or redundant tools.

    Completeness3/5

    The set covers creating and invoking endpoints, adding dependencies and data connections, managing secret bindings, and setting up auth. However, there are notable gaps: no way to list, update, or delete endpoints, and no way to remove an added integration or connection, which can leave agents in dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues