https://mcp.sevalla.com/mcp as a remote HTTP server. Its agents read MCP servers from mcp_config.json.
Before you begin
- A Sevalla account and a company to work in.
- Devin Desktop (or Windsurf) installed. See the Devin MCP configuration docs for its own options.
Add the server
1
Add Sevalla
Open To share the server with a project’s team instead, put the same entry in
~/.config/devin/mcp_config.json (on Windows, %APPDATA%\devin\mcp_config.json), create it if it doesn’t exist, and add Sevalla under mcpServers:~/.config/devin/mcp_config.json
.devin/mcp_config.json in the repository.2
Sign in
The first time the agent uses Sevalla, Devin Desktop asks you to authenticate. If the server shows Needs auth in the MCP list, click Authenticate. Your browser opens the Sevalla dashboard: pick the company and the permissions, then click Authorize (what each choice means).
Windsurf versions from before the rename read
~/.codeium/windsurf/mcp_config.json and take the URL as serverUrl instead of url: {"mcpServers": {"sevalla": {"serverUrl": "https://mcp.sevalla.com/mcp"}}}.Check the connection
Open the MCP list in Devin Desktop: sevalla is listed with its tools and no Needs auth state. Ask the agent “List my Sevalla services”. The Devin Local agent asks for approval before each MCP tool call; you can allow a tool, or every Sevalla tool, for the session or permanently.Use an API key instead
To skip OAuth, send an API key in a header.${env:SEVALLA_API_KEY} reads the key from an environment variable, so the file holds no secret:
~/.config/devin/mcp_config.json
mcp_config.json (sevalla) exactly.
Remove the server
Delete thesevalla entry from mcp_config.json. To keep it but stop the agent from using it, turn it off with its toggle in the MCP list.
Removing the server doesn’t delete the API key that sign-in created. To revoke it, delete the key under Tools > API keys.