displague/linode-oauth-mcp-server
Developer toolsЭта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал
An experimental MCP server that turns the Linode API v4 OpenAPI specification into tools. Each tool requests only the OAuth scopes its operation needs, and the sign-in link appears in the MCP...
Обзор
An experimental MCP server that turns the Linode API v4 OpenAPI specification into tools. Each tool requests only the OAuth scopes its operation needs, and the sign-in link appears in the MCP client's chat. The API spec is fetched from Linode's official OpenAPI distribution, parsed, cached on disk, and used to build the MCP tool catalog. The server exposes Linode API operations as linode_ tools. By default, the server lists only three tools and keeps the rest of the catalog out of the initial list: search_tools finds operations, call_tool invokes them, and get_tool_schema returns one tool's full input schema. Search ranks tools by their name, title, and summary, and returns a compact entry for each of up to 10 matches: its title, first description paragraph, access level, required OAuth scopes, and a one-line summary per parameter. Results run about 5K characters, where full tool definitions would be up to 250K. Responses are rendered as YAML, including calls made through call_tool.
README
Показан фрагмент оригинального README. Открыть оригинал.
Linode OAuth MCP Server
An experimental MCP server that turns the Linode API v4 OpenAPI specification into tools. Each tool requests only the OAuth scopes its operation needs, and the sign-in link appears in the MCP client’s chat. The API spec is fetched from Linode’s official OpenAPI distribution, parsed, cached on disk, and used to build the MCP tool catalog.
Scope and discovery
The server exposes Linode API operations as linode_ tools. By default, the server lists only three tools and keeps the rest of the catalog out of the initial list: search_tools finds operations, call_tool invokes them, and get_tool_schema returns one tool’s full input schema. Search ranks tools by their name, title, and summary, and returns a compact entry for each of up to 10 matches: its title, first description paragraph, access level, required OAuth scopes, and a one-line summary per parameter. Results run about 5K characters, where full tool definitions would be up to 250K. Responses are rendered as YAML, including calls made through call_tool. --tool-catalog full lists every generated tool directly. Every paginated list tool accepts an X-Filter argument, a JSON string sent as Linode’s filter header (for example, {"mine": true}). The upstream spec declares that header on only a few operations.
The server fetches the spec on first launch and stores it in the user’s cache directory (LINODE_MCP_CACHE_DIR overrides the default). Later starts load the cached JSON copy, which takes about a second. After startup, the server checks the upstream spec in the background with a conditional GET using the cached ETag. An unchanged spec costs one small 304 Not Modified request. If the spec has changed, the server fetches and caches it, and the new spec takes effect the next time the server starts. Run linode-oauth-mcp-server --update-specs to force a fresh fetch.
Authentication
Credentials are checked in this order:
LINODE_API_TOKENorLINODE_OAUTH_TOKEN.LINODE_CLI_TOKEN, then thetokenin~/.config/linode-cli(orLINODE_CLI_CONFIG).- A Linode public OAuth app, when
LINODE_OAUTH_CLIENT_IDis configured.
Установка
uvx linode-oauth-mcp-serverКонфигурация
{
"mcpServers": {
"linode": {
"command": "uvx",
"args": ["linode-oauth-mcp-server"]
}
}
}