openserverless-mcp
OfficialRelated Servers
Alternatives to openserverless-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityFmaintenanceAn MCP server that enables dynamic tool registration and execution based on API definitions, providing seamless integration with services like Claude.ai and Cursor.ai.23MIT- AlicenseNot gradedqualityDmaintenanceA universal MCP server that connects any REST API to AI assistants via OpenAPI or Postman specifications. It enables dynamic tool creation with GraphQL-style field selection and automatic schema inference for efficient data retrieval.31 npm6-
- AlicenseAqualityBmaintenanceAn MCP server that exposes deterministic workflows as tools, allowing small models to reliably orchestrate APIs and other MCP servers with minimal parameters.212 npm2MIT
- AlicenseNot gradedqualityDmaintenanceA production-grade MCP server designed for multi-tenant, authenticated, and observable AI agent systems, enabling secure tool execution across heterogeneous data sources.62MIT
- FlicenseNot gradedqualityCmaintenanceMulti-cloud MCP server that exposes cloud AI models as tools for AI CLI agents, supporting streaming, conversation history, parallel multi-model queries, and dynamic model discovery.2-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to discover and execute tools via a secure MCP server with JWT authentication, RBAC, rate limiting, and audit logging.1MIT
TDQS
Scored across 8 tools
Each tool targets a unique purpose: adding specific connection types (Milvus, PostgreSQL, Redis, S3, secret), creating a new action, invoking an action, or adding a library requirement. There is no overlap in functionality, and the descriptions clearly distinguish each tool's role.
All tools use a consistent 'action_' prefix and snake_case, but the verb structure varies: some include a noun after 'add' (e.g., action_add_milvus), while others lack a noun (action_invoke, action_new, action_requirements). This minor inconsistency prevents a perfect score, but the pattern is still predictable.
With 8 tools, the set is well-scoped for a server focused on managing OpenServerless actions. It covers creation, invocation, dependency management, and integration with external services without being overwhelming or too sparse.
The tool surface covers core action creation and invocation, along with adding various connections and dependencies. However, it lacks tools for deleting, updating, or listing actions, as well as removing connections or secrets. These gaps could hinder agents needing full lifecycle management.