Overview

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

It authenticates using the same API access token you use for the Public APIs, or with a pre-registered OAuth client, and operates against the warehouse configured for your tenant (Snowflake or Databricks).

Prerequisites

• An API access token. Follow the Public APIs setup to generate one. The token must be READ_WRITE.
• Currently only supports Snowflake and Databricks.

Endpoint

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

Client setup

Below are example configurations for common MCP clients. In all cases, paste the access token from the Public APIs setup as the Authorization header value.

Claude Code

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.

Pre-registered OAuth client

As an alternative to the API access token, 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.
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.

In Claude Code, 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.

Security

Treat the access token like a password. It grants the same permissions as the Public APIs (read/write within the tenant).