Linode OAuth MCP Server
Related Servers
Alternatives to Linode OAuth MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceExposes two MCP tools (discover and execute) that enable agents to query an OpenAPI schema via natural language and execute matched API operations.2-
- AlicenseNot gradedqualityAmaintenanceEnables LLMs to discover and invoke generated API operations as MCP tools and resources, supporting create, update, list, and get-by-id actions over the same data exposed by the REST API.MIT
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to call any OpenAPI-defined API by automatically converting its operations into tools, with built-in support for authentication, rate limiting, and response handling.7Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables users to turn any OpenAPI 3.x spec into callable MCP tools at runtime, letting agents inspect and invoke API operations directly from JSON or YAML specifications without code generation or build steps.1MIT
- FlicenseNot gradedqualityDmaintenanceDynamically exposes any OpenAPI/Swagger API as tools for AI assistants, automatically generating MCP tools from OpenAPI specs with authentication support.-

Kaiva Bridgeofficial
AlicenseNot gradedqualityBmaintenanceLets an AI client create, list, and inspect managed MCP servers from inside a chat, drafting a server from an OpenAPI spec URL and refreshing its tools when the underlying API changes.202 npm1MIT
TDQS
Scored across 3 tools
The three tools have clearly distinct roles in a meta-tool workflow: search_tools discovers tools, get_tool_schema provides nested parameter detail, and call_tool executes a discovered tool. There is no meaningful overlap between them, and the descriptions reinforce when to use each.
All tool names follow a consistent snake_case verb_noun pattern: search_tools, get_tool_schema, and call_tool. The convention is predictable and readable across the entire set.
Three tools is minimal but exactly right for a discovery-and-execution gateway over a larger Linode API tool surface. Each tool earns its place by covering a necessary phase of the meta-workflow.
The surface covers discovery, schema inspection, and execution, which is the core lifecycle for a tool-gateway server. A minor gap is the absence of a browse/list-all operation, though natural-language search likely suffices for most agent workflows.