MCP Server

The Komodo MCP (Model Context Protocol) server connects AI assistants — Cursor, VS Code Copilot, Claude Desktop, and similar clients — to your Komodo Snowflake warehouse so they can explore schemas and help you write SQL.

Prerequisites

1. Install the Komodo SDK
2. Authenticate:

   uv run komodo login

3. Set your account:

   uv run komodo account set

Usage

Configuration JSON

Run:

uv run komodo mcp show-config

The CLI prints (and copies) the right JSON for your environment. The snippets below show the same inner komodo server definition; only the outer wrapper changes per client.

Replace /path/to/your/connector/project with the directory that contains your pyproject.toml where komodo is installed.

Shared server definition

Every client uses this object under its own key (see tabs).

"komodo": {
  "command": "uv",
  "args": ["run", "komodo", "mcp", "run"],
  "cwd": "/path/to/your/connector/project"
}

Environment selection

All tools default to production. To use the integration environment you can either:

1. Tell the agent — mention the environment in your prompt (e.g. “deploy to integration”). The agent passes use_integration: true to each tool call. No config changes needed.
2. Set KOMODO_ENVIRONMENT in the config — add a sibling env object to set the default for every call in that server session:

"env": {
  "KOMODO_ENVIRONMENT": "integration"
}

The MCP process is started by the editor and does not inherit your shell, so KOMODO_ENVIRONMENT must be set here if you choose this approach.

Cursor

File: ~/.cursor/mcp.json

{
  "mcpServers": {
    "komodo": {
      "command": "uv",
      "args": ["run", "komodo", "mcp", "run"],
      "cwd": "/path/to/your/connector/project"
    }
  }
}

With integration environment:

{
  "mcpServers": {
    "komodo": {
      "command": "uv",
      "args": ["run", "komodo", "mcp", "run"],
      "cwd": "/path/to/your/connector/project",
      "env": {
        "KOMODO_ENVIRONMENT": "integration"
      }
    }
  }
}

VS Code

User or workspace settings.json — server lives under mcp.servers:

{
  "mcp": {
    "servers": {
      "komodo": {
        "command": "uv",
        "args": ["run", "komodo", "mcp", "run"],
        "cwd": "/path/to/your/connector/project"
      }
    }
  }
}

Add "env": { "KOMODO_ENVIRONMENT": "integration" } inside the komodo object when needed.

Claude Desktop

Same top-level shape as Cursor (mcpServers):

{
  "mcpServers": {
    "komodo": {
      "command": "uv",
      "args": ["run", "komodo", "mcp", "run"],
      "cwd": "/path/to/your/connector/project"
    }
  }
}

Add "env": { "KOMODO_ENVIRONMENT": "integration" } inside komodo when needed.

Variable	Required	Description
KOMODO_ENVIRONMENT	No	production (default) or integration

Run the server manually

uv run komodo mcp run

Clients normally start this command using the configuration above.

Tip

In Komodo internal environments, installing komodo-internal-tools adds MCP tools for scaffolding, building, and deploying apps. The default remote build path uses Komodo OAuth only (no AWS credentials or local BuildKit). Documentation for those tools is published on the internal documentation site.

Try it out

After configuring your client, try:

“What are my Komodo databases?”

Capabilities

list_snowflake list_type	Description	Required parameters
database	List accessible databases	—
schema	Schemas in a database	database
table	Tables in a schema (metadata / row counts)	database, schema
column	Column definitions	database, schema, table

In internal Komodo environments, komodo-internal-tools registers additional MCP tools; see internal documentation for the full list.