Skip to main content
Glama
displague

Linode OAuth MCP Server

by displague
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Linode OAuth MCP Server

No user-submitted related servers found.

    Related Servers

    • yellow-pages

      ethank64
      F
      license
      A
      quality
      D
      maintenance
      Exposes two MCP tools (discover and execute) that enable agents to query an OpenAPI schema via natural language and execute matched API operations.
      2
      -

    • Express REST API and MCP

      rezende64
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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

    • openapi-to-mcp

      The-Swarm-Corporation
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      7
      Apache 2.0
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources