SuperAPI AI Directory

mcp

Manage Sevalla cloud infrastructure.

Open website

About this tool

Purpose Sevalla MCP Server is a remote Model Context Protocol (MCP) server that provides AI agents with full access to the Sevalla PaaS API, enabling agents to manage and query Sevalla cloud infrastructure through conversation. It is built on the Code Mode MCP pattern proposed by Cloudflare, which no longer registers one tool for each API endpoint, but instead gives the agent only two tools; as a Cloudflare partner, Sevalla has applied this pattern to the Sevalla PaaS API, and its sandbox architecture and tool design are inspired by the open-source implementation codemode.

Main capabilities The server exposes only 2 tools instead of about 200 tools:

  • search: queries the OpenAPI specification to discover endpoints, parameters, and schemas.
  • execute: runs JavaScript in a sandboxed V8 isolated environment and calls the API through sevalla.request(). The official description states that compared with the traditional "one tool per endpoint" approach, this can reduce context window usage by about 99%. Each request creates an isolated MCP session bound to the caller's API key; the server is completely stateless. Once connected, the AI agent can discover and call the API on your behalf.

How to use The hosted server address is https://mcp.sevalla.com/mcp。认证通过 OAuth handling: the client opens a browser and logs in with a Sevalla account, so no API key is needed in the configuration. The connection methods for different clients are as follows:

  • Claude Code: after connecting, enter /mcp in Claude Code and select Authenticate to complete the OAuth flow.
  • Claude Desktop: add it through Settings → Connectors → Add Connector, and enter the URL https://mcp.sevalla.com/mcp,Claude Desktop will handle OAuth automatically.
  • Cursor: add the configuration in .cursor/mcp.json in the project root directory.
  • Windsurf: add it to ~/.codeium/windsurf/mcp_config.json.
  • OpenCode: add it in opencode.json in the project root directory, then run opencode mcp auth sevalla to complete OAuth. The official documentation also provides the corresponding MCP documentation links for each client.

Permissions and security Sevalla API keys support fine-grained permissions, so you can create read-only keys that let the agent only query infrastructure without making changes. The full API reference is at api-docs.sevalla.com, and the base URL is api.sevalla.com/v3.

Removal and revocation To completely remove the Sevalla MCP server, you need to delete the server configuration and clear the stored OAuth credentials. The official documentation specifically notes that removing the MCP server will not delete your API keys on Sevalla; to revoke them, go to app.sevalla.com/api-keys.

  • Claude Code: run /mcp, select sevalla, then select Clear authentication; if the server was added in a non-default scope, you need to specify it explicitly.
  • Claude Desktop: find the Sevalla connector in Settings → Connectors and remove it, then fully quit and restart Claude Desktop. OAuth tokens are stored in the operating system keychain (macOS Keychain / Windows Credential Manager), and the Sevalla entry must be manually deleted from the keychain.
  • Cursor: delete the sevalla entry from .cursor/mcp.json (project) or ~/.cursor/mcp.json (global), then clear the cached OAuth token.
  • Windsurf: delete the sevalla entry from ~/.codeium/windsurf/mcp_config.json.
  • OpenCode: from the opencode in the project root directoryDelete the sevalla entry in .json.

Local run requirements The official local run requirements are listed as Node.js 24+ (TypeScript runs natively, no build step required); Docker can also be used.

Use cases Suitable for users of any MCP-supporting client to query or manage Sevalla infrastructure through conversation, without using an SDK, without boilerplate code, and without letting the context window be filled by about 200 tools.

Limitations The material does not provide specific pricing, charging model, or billing information; it does not provide a detailed API endpoint list, example invocation code, or complete configuration snippets; it does not explain support for other platforms besides the listed clients.