Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.sevalla.com/llms.txt

Use this file to discover all available pages before exploring further.

Use this guide to connect Codex to the Sevalla MCP server at https://mcp.sevalla.com/mcp. After setup, Codex can use Sevalla MCP tools such as search and execute.

​
Quick setup (CLI + OAuth)

OAuth is the recommended authentication method.
  1. Add the remote MCP server:
codex mcp add sevalla --url https://mcp.sevalla.com/mcp
  1. Authenticate with OAuth:
codex mcp login sevalla
  1. Verify configuration:
codex mcp list

​
Manual configuration (config.toml)

Codex uses TOML (not JSON) for MCP configuration. You can configure MCP servers in:
  • ~/.codex/config.toml (user scope)
  • .codex/config.toml (project scope, trusted projects only)
[mcp_servers.sevalla]
url = "https://mcp.sevalla.com/mcp"
If you need API key auth instead of OAuth, pass an auth header from an environment variable: 
[mcp_servers.sevalla]
url = "https://mcp.sevalla.com/mcp"
env_http_headers = { Authorization = "SEVALLA_AUTH_HEADER" }

export SEVALLA_AUTH_HEADER="Bearer <your-api-key>"
Do not hardcode secrets in config.toml. Keep API keys in environment variables.

​
Configuration scope

  • User scope: ~/.codex/config.toml, available in all projects.
  • Project scope: .codex/config.toml, loaded only when the project is trusted.
Project settings override user settings for matching keys.

​
Uninstall

Run the following: 
codex mcp remove sevalla

​
Reference