Linode OAuth MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINODE_API_TOKEN | No | Linode API token for authentication. Checked first. | |
| LINODE_CLI_TOKEN | No | Token from Linode CLI configuration. Checked second. | |
| LINODE_CLI_CONFIG | No | Path to the linode-cli configuration file (default: ~/.config/linode-cli). | |
| LINODE_OAUTH_TOKEN | No | Linode OAuth token for authentication. Checked first (alternative to LINODE_API_TOKEN). | |
| LINODE_OAUTH_SCOPES | No | Comma- or space-separated list of OAuth scopes to request initially. Use '*' to grant everything up front. | |
| LINODE_MCP_CACHE_DIR | No | Override the default cache directory for the OpenAPI spec. | |
| LINODE_OAUTH_CLIENT_ID | No | Public OAuth client ID for Linode sign-in. Used when no token is available. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_tool_schemaA | Return a Linode API tool's full description and input schema. Search results summarize parameters in one line each. Use this before calling a tool whose nested parameters need more detail. |
| search_toolsA | Search the Linode API tools in natural language. Returns a compact summary of each match: title, purpose, access level, required OAuth scopes, and parameters. |
| call_toolB | Call a tool by name with the given arguments. Use this to execute tools discovered via search_tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.