GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者提供的说明(英文原文)
Official Sevalla MCP: deploy, debug and manage apps, static sites and databases.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.sevalla.com/mcp在终端中运行这条命令
claude mcp add --transport http sevalla https://mcp.sevalla.com/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"sevalla": {
"url": "https://mcp.sevalla.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"sevalla": {
"type": "http",
"url": "https://mcp.sevalla.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.sevalla.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 sevalla 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 218 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(2.0.0)于6天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:GitHub, Desktop Commander, Cloudflare MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Deploy, debug and manage Sevalla applications, databases and static sites from any AI agent.
Docs · Sevalla · mcp.sevalla.com
A remote Model Context Protocol (MCP) server for Sevalla, so AI agents like Claude Code, Cursor and Codex can work with the applications, databases and static sites in your Sevalla company. It gives them 27 tools: 22 purpose-built tools for the everyday workflows (deploying, reading logs and metrics, environment variables, scaling, domains, creating services) and 5 generic tools that reach the rest of the Sevalla API by operation ID, split into read, create, update and delete.
Connect your MCP client to the hosted server at https://mcp.sevalla.com/mcp, then sign in with your Sevalla account when the client opens a browser.
claude mcp add --transport http sevalla https://mcp.sevalla.com/mcp
Then type /mcp inside Claude Code and select Authenticate to complete the OAuth flow.
Add via Settings → Connectors → Add Connector and enter https://mcp.sevalla.com/mcp as the URL. Claude Desktop handles OAuth automatically.
Add to .cursor/mcp.json in your project root:
{
"mcpServers": { "sevalla": { "url": "https://mcp.sevalla.com/mcp" } } }
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": { "sevalla": { "serverUrl": "https://mcp.sevalla.com/mcp" } } }
Add to opencode.json in your project root:
{
"$schema": "https://opencode.ai/config.json", "mcp": { "sevalla": { "type": "remote", "url": "https://mcp.sevalla.com/mcp" } } }
Then run opencode mcp auth sevalla to complete the OAuth flow.
Every tool carries a title and explicit readOnlyHint, destructiveHint, idempotentHint and openWorldHint annotations, so clients like Claude run read-only tools without asking and always confirm destructive ones.
| Area | Tools |
|---|---|
| Discovery | list_services, get_application, get_static_site, get_database, get_platform_options, search_sevalla_docs |
| Deployments | list_deployments, get_deployment, get_deployment_logs, trigger_deployment, rollback_deployment |
| Observability | search_runtime_logs, search_access_logs, get_metrics |
| Configuration | list_environment_variables, set_environment_variables, delete_environment_variables, scale_process, add_domain |
| Create | create_application, create_static_site, create_database |
| Rest of the API | sevalla_api_search, sevalla_api_read, sevalla_api_create, sevalla_api_update, sevalla_api_delete |
The generic tools only accept operation IDs from a reviewed table generated from the Sevalla API v3 spec: the server, not the model, picks the HTTP method and path, and each tool only runs operations of its own class.
Environment variable values are withheld: the tools list variable keys and their scoping, and set or delete them without ever returning a value. Everything else the Sevalla API offers is available, including deleting entire services, managing API keys and operations that issue a new secret (rolling a webhook secret, regenerating a deployment hook, rotating storage credentials), which return that secret. Destructive tools are annotated so Claude asks for confirmation before each call. Commands run inside a process (execProcessCommandV3) and application logs can still show secrets.
Clients sign in with OAuth: the client opens a browser, you approve the connection in the Sevalla dashboard, and the approval creates an API key for it. No API key goes in the client's config. Clients without OAuth can send a Sevalla API key as Authorization: Bearer instead.
Every tool is limited by the permissions of the Sevalla API key behind the connection. Sevalla API keys support granular permissions, so a read-only key keeps an agent read-only. Full API reference at api-docs.sevalla.com.
Each request creates a fresh MCP server bound to the caller's API key; nothing is stored between requests. The server speaks MCP 2026-07-28 (server/discover, per-request metadata, cacheable tool lists) and still serves clients on the 2025 revisions (2025-11-25 back to 2024-11-05) over the same URL, with the same tools.
Sign-in is OAuth 2.1 with PKCE. Clients identify themselves with an OAuth Client ID Metadata Document (as Claude, ChatGPT and VS Code do) or, for older clients, Dynamic Client Registration. The flow is stateless too: pending authorizations are HMAC-signed into the callback URL, authorization codes are AES-256-GCM encrypted, and access tokens are encrypted and bound to https://mcp.sevalla.com/mcp.
To fully remove the Sevalla MCP server, delete the server configuration and clear stored OAuth credentials.
Removing the MCP server does not delete your API key on Sevalla. To revoke it, go to app.sevalla.com/api-keys.
claude mcp remove sevalla
Then clear the stored OAuth token: run /mcp inside Claude Code, select sevalla, and choose Clear authentication.
If the server was added at a non-default scope, specify it explicitly:
claude mcp remove --scope user sevalla
claude mcp remove --scope project sevalla
Open Settings → Connectors, find the Sevalla connector, and remove it. Then fully quit and restart Claude Desktop.
OAuth tokens are stored in the operating system keychain (macOS Keychain / Windows Credential Manager). To remove them, delete the Sevalla entry from your keychain manually.
Delete the sevalla entry from .cursor/mcp.json (project) or ~/.cursor/mcp.json (global). Then clear cached OAuth tokens:
rm -rf ~/.mcp-auth
Delete the sevalla entry from ~/.codeium/windsurf/mcp_config.json.
opencode mcp logout sevalla
Then delete the sevalla entry from opencode.json in your project root.
Requirements: Node.js 26 (24 also works) and pnpm 12. TypeScript runs natively, no build step.
git clone https://github.com/sevalla/mcp.git
cd mcp pnpm install pnpm start
Or with Docker:
docker build -t sevalla-mcp .
docker run -p 3000:3000 -e OAUTH_SECRET sevalla-mcp
| Variable | Purpose |
|---|---|
PORT | HTTP port (default 3000) |
OAUTH_SECRET | base64url-encoded 32 bytes; required when NODE_ENV=production |
PUBLIC_URL | Public base URL used in OAuth metadata (default https://mcp.sevalla.com) |
SEVALLA_FRONTEND_URL | Sevalla dashboard URL for the OAuth consent page (default https://app.sevalla.com) |
SEVALLA_API_URL | Sevalla API base URL (default https://api.sevalla.com) |
SEVALLA_DOCS_URL | Documentation site searched by search_sevalla_docs (default https://docs.sevalla.com) |
DEVICE_CODE_TRUSTED_CLIENT_TOKEN | Service token that lets the API rate-limit OAuth sign-ins per end-user IP instead of per server IP |
CLIENT_IP_HEADER | Header carrying the end-user IP, set by your edge (default x-forwarded-for; use cf-connecting-ip behind Cloudflare) |
TRUSTED_PROXY_HOPS | With x-forwarded-for: number of trusted proxies that append to it; the client IP is read that many entries from the right (default 1) |
SEVALLA_API_KEY | --stdio mode: the Sevalla API key |
SHUTDOWN_TIMEOUT_MS | Graceful shutdown deadline (default 30000) |
OPENAI_APPS_CHALLENGE | Domain verification token served at /.well-known/openai-apps-challenge for the OpenAI plugin submission |
Client IP in production. The device-code rate limit is applied per end-user IP, so the server must read that IP from something your edge controls. Behind Cloudflare, set `CLIENT_IP_HEADER=
只显示了开头部分;其余内容请在仓库中阅读