Skip to main content
OpenCode connects to the Sevalla MCP server at https://mcp.sevalla.com/mcp as a remote server. Once connected, OpenCode can deploy, read logs and metrics, and manage your Sevalla services from the same session.

​
Before you begin

  • A Sevalla account and a company to work in.
  • OpenCode installed. See the OpenCode MCP docs for its own options.

​
Add the server

1

Add Sevalla

Add Sevalla under mcp in ~/.config/opencode/opencode.json (all projects) or in opencode.json at the root of a project (that project only):
~/.config/opencode/opencode.json
OpenCode merges both files. When they set the same key, the project file wins.
2

Sign in

Run:
Your browser opens the Sevalla dashboard: pick the company and the permissions, then click Authorize (what each choice means). OpenCode stores the token in ~/.local/share/opencode/mcp-auth.json.

​
Check the connection

Run opencode mcp list to see sevalla and its status, and opencode mcp auth list to see whether it’s signed in. Start OpenCode and ask “List my Sevalla services”.

​
Use an API key instead

To skip OAuth, turn it off for the server and 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/opencode/opencode.json

​
Remove the server

Sign out, then delete the sevalla entry from opencode.json:
To keep the entry but stop OpenCode from using it, set "enabled": false. Removing the server doesn’t delete the API key that sign-in created. To revoke it, delete the key under Tools > API keys.