Overview

Revefi exposes a Model Context Protocol (MCP) HTTP endpoint that lets MCP-compatible clients (Claude Code, Snowflake Cortex Code, Cursor, Claude Desktop, etc.) call Revefi tools — query metadata, operate on warehouse data — directly from the assistant.

It operates against the warehouse configured for your tenant (Snowflake or Databricks).

Prerequisites

• A Revefi account connected to Snowflake or Databricks. Other warehouses are not supported yet.
• One of the authentication methods below.

Endpoint

The MCP server speaks the Streamable HTTP transport. Authentication is Authorization: Bearer <token> on every request.

Authentication

You can connect with either of these methods. Client setup shows how to configure each one in your MCP client.

API access token

Use the same API access token you use for the Public APIs. Follow the Public APIs setup to generate one. The token must be READ_WRITE.

Everyone who uses the token shares the same access.

Pre-registered OAuth client

Revefi can register a dedicated OAuth client for your account. Each user then signs in with their own Revefi login instead of everyone sharing one token.

Revefi creates the client — you do not create it yourself.

1. Contact Revefi support to have an OAuth client registered for your account. Include the callback URL your MCP client will use — Revefi has to register it before sign-in will work, and it has to match exactly.

   MCP client	Callback URL
   Claude Code	http://localhost:8790/callback
   Snowflake Cortex Code	http://localhost:8585/callback

   You can ask for a different port. If you do, use that port in your client configuration.

2. Once it is registered, sign in to Revefi, open the Settings page, and copy the Client ID and Client Secret from the MCP section.

Client setup

Below are example configurations for common MCP clients.

Claude Code

API access token

Add the server to your user-level claude config under mcpServers:

{
  "mcpServers": {
    "revefi": {
      "type": "http",
      "url": "https://gateway.revefi.com/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer <PASTE_YOUR_API_TOKEN_HERE>"
      }
    }
  }
}

Restart Claude Code. The Revefi tools should appear under the revefi MCP server.

OAuth client

Pass your Client ID and the callback port Revefi registered for you:

claude mcp add --transport http revefi https://gateway.revefi.com/api/v1/mcp \
  --client-id <YOUR_CLIENT_ID> \
  --client-secret \
  --callback-port 8790

--client-secret takes no value — Claude Code prompts for the secret and stores it outside the config file. You can also supply it with the MCP_CLIENT_SECRET environment variable.

The first tool call opens your browser to sign in to Revefi and approve access.

Snowflake Cortex Code (CoCo)

API access token

Add the server with the Cortex Code CLI:

cortex mcp add revefi https://gateway.revefi.com/api/v1/mcp \
  --type http \
  -H "Authorization: Bearer <PASTE_YOUR_API_TOKEN_HERE>"

Or add it to ~/.snowflake/cortex/mcp.json under mcpServers:

{
  "mcpServers": {
    "revefi": {
      "type": "http",
      "url": "https://gateway.revefi.com/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer <PASTE_YOUR_API_TOKEN_HERE>"
      }
    }
  }
}

On first connection, Cortex Code moves the Authorization header out of mcp.json and into your OS keychain.

To check the connection, run cortex mcp start. It should report the revefi server as connected. In a Cortex Code session, /mcp shows the server's status and the Revefi tools.

OAuth client

Add the server to ~/.snowflake/cortex/mcp.json with an oauth block instead of the Authorization header. Set redirect_port to the callback port Revefi registered for you:

{
  "mcpServers": {
    "revefi": {
      "type": "http",
      "url": "https://gateway.revefi.com/api/v1/mcp",
      "oauth": {
        "client_id": "<YOUR_CLIENT_ID>",
        "client_secret": "<YOUR_CLIENT_SECRET>",
        "redirect_port": 8585
      }
    }
  }
}

Run cortex mcp start. Your browser opens so you can sign in to Revefi and approve access. Cortex Code then moves the client secret and the sign-in tokens to your OS keychain and refreshes the tokens automatically.

For more options, see Snowflake's Cortex Code MCP documentation.

Security

Treat the access token and the OAuth client secret like passwords. The access token grants the same permissions as the Public APIs (read/write within the tenant).