Paradime MCP server: connect AI clients to your data

The Paradime MCP Server is a single, authenticated remote endpoint that brings DinoAI’s full context graph (your warehouse, repositories, dbt™ catalog, lineage, and Bolt orchestration) to any MCP-compatible AI client. Connecting uses OAuth: add the server URL to your client, sign in to Paradime in the browser, and approve the connection. No long-lived tokens to generate or paste.

Setup takes about a minute. If you already have a Paradime account, you can be connected and running queries in your AI client before this page finishes loading.

Before you start

You need:

A Paradime account. Business and read-only seats are free. If you don’t have access, ask your data team to invite you to your workspace.
An MCP-compatible client. Claude (Desktop or web), Claude Code, ChatGPT, GitHub Copilot, Cursor, Kiro, and OpenCode are all supported. See Client setup below.
Your data team has configured the workspace integrations the MCP should expose (warehouse, code repository, BI tools). The MCP inherits your workspace’s existing connections; there’s nothing extra to configure on the MCP side.

The MCP server uses the same access boundaries as the rest of Paradime. A connected client can only reach the integrations your workspace has connected, and only with the permissions your role allows.

Step 1: Copy your MCP server URL

Log in to Paradime at app.paradime.io.
Open Settings → MCP Access (direct link).
Copy the MCP server URL. It is specific to your Paradime instance and looks like:

https://mcp-<region>.paradime.io/company/<company-token>/mcp

If you belong to multiple Paradime workspaces - for example, separate workspaces for finance, marketing, and engineering, that’s not a problem. One single MCP endpoint allows you to access across workspaces you have access to.

Step 2: Add Paradime to your client

The flow is the same in every client: add a remote MCP server with the URL from Step 1, and complete the sign-in when your browser opens. You’ll be asked for your organization name, then to authenticate as your Paradime user and approve the connection on a consent screen that shows the name of the client requesting access and the host it redirects back to. Approve it and the client is connected. Pick your client for the exact steps:

Claude Desktop & claude.ai

Claude Code

Cursor

GitHub Copilot

OpenCode

Kiro

Amazon Quick

Other clients

Only approve consent screens you triggered yourself. The consent screen names the client asking for access and the host it redirects to. If either looks unfamiliar, or you weren’t in the middle of connecting a client, deny the request.

Step 3: Verify the connection

To confirm your connection is healthy, ask your AI client a simple question that requires Paradime context. For example:

“Use Paradime to list my Bolt schedules.”

“Use Paradime to search the catalog for models that touch the orders table.”

If your client returns real data from your workspace, you’re connected. If you get an error, jump to Troubleshooting below.

Manage connected clients

Settings → MCP Access lists every client connected to your account, so you always know what has access. Click Disconnect on any of them to revoke it immediately; the client will fail on its next call until you reconnect it. Every tool call runs with your own role and workspace permissions and is logged against your user account, the same way warehouse queries and Bolt runs are.

Legacy tokens

Before OAuth, clients connected with a generated MCP token. New tokens can’t be generated anymore; browser sign-in is the path for every new setup. Existing personal access tokens keep working as Bearer tokens on the MCP endpoint until they expire or you delete them:

Authorization: Bearer <your-legacy-token>

Review or revoke your remaining tokens on the Legacy tokens tab of Settings → MCP Access, which also shows the legacy endpoint older configs may still point at.

Treat a legacy token like a password. It carries your full Paradime permissions. Never commit it to a repository, paste it into a shared document, or share it with teammates. If you suspect a token is compromised, delete it on the Legacy tokens tab and reconnect the client through the browser sign-in.

Available tools

Once connected, your client has access to all 26 tools below.

Code & repository

Tool	What it does
`read_file`	Read any file in your connected code repository (SQL, Python, YAML, etc.).
`rename_file`	Rename a file in the repo. Parent directories are created automatically.
`search_files_and_directories`	Find files and folders by glob pattern (`*/.sql`, `models/staging/**`).
`ripgrep_search`	High-speed regex search across the entire repo with context lines.
`create_pull_request`	Open a new PR (including drafts) using the connected user’s GitHub account.
`read_pull_request`	Pull PR metadata, the full code diff, CI status, or review and inline comments.
`list_pull_requests`	List PRs by state, branch, sort order, or popularity.

Data warehouse & catalog

Tool	What it does
`run_sql_query`	Execute SQL against your warehouse and return results as CSV (Snowflake, BigQuery, Databricks, Redshift).
`search_catalog`	Search the unified catalog: dbt™ models, sources, tests, macros, plus Looker, Tableau, Fivetran assets.
`get_column_level_lineage`	Trace upstream and downstream dependencies for any column in any model.

dbt Discovery

Read-only dbt™ project metadata from your Bolt runs’ artifacts, mirroring the dbt-mcp Discovery toolset. See dbt Discovery Tools.

Tool	What it does
`get_all_models`	List every model with its name, unique ID, and description.
`get_mart_models`	List mart models only (`fct_`/`dim_` prefixes or a `marts/` path).
`get_all_sources`	List sources with their freshness status, filterable by source name.
`get_all_macros`	List macros, with dbt Labs builtin packages excluded by default.
`get_exposures`	List downstream dashboards, apps, and analyses.
`get_lineage`	Return the lineage graph around a node, filterable by type, depth, and direction.
`get_model_health`	Report a model’s last run status, test statuses, and upstream parents’ health.
`get_model_performance`	Return historical run timings for a model, newest first.
`get_node_details`	Full details for any model, source, exposure, test, seed, snapshot, or macro.

Bolt orchestration

Tool	What it does
`list_bolt_schedules`	List every active Bolt schedule with name, UUID, cron, owner, and configured commands.
`get_bolt_run_logs`	Pull AI-generated failure summaries for a specific run or the most recent run.
`trigger_bolt_schedule_run`	Kick off a new run of a Bolt schedule by `slug` (required, get it from `list_bolt_schedules`). Optional `branch` to run against a different git branch or commit, and optional `commands` (array of strings) to override the schedule’s configured commands. Omit both to run with defaults. Returns the new `run_id`.

Workspace management

Tool	What it does
`list_workspaces`	List every Paradime workspace your account has access to.
`switch_workspace`	Switch the active workspace, useful when you have multiple workspaces connected.

Web & research

Tool	What it does
`execute_web_search`	General-purpose web search, with optional domain restrictions (e.g. limit to docs sites).
`perplexity_search`	Real-time web search via the Perplexity API for up-to-date documentation and references.
`extract_url_content`	Pull clean text content from any HTTP/HTTPS URL.

Troubleshooting

'Authentication failed' or '401 Unauthorized'

The connection was disconnected, expired, or (for token-based setups) the token is no longer valid.

Check Settings → MCP Access to see whether the client is still listed. If not, reconnect it from the client and complete the browser sign-in again.
Most clients have a reconnect or reauthenticate action on the server entry; use it to restart the sign-in.
If the client authenticates with a legacy token, check the Legacy tokens tab in Settings → MCP Access to confirm the token still exists and hasn’t expired. New tokens can’t be generated; reconnect through the browser sign-in instead.

'Connection failed' or the connector won't authorize

Confirm the MCP server URL is correct; it is unique to your Paradime instance. Re-copy it from Settings → MCP Access.
Check that your network or VPN isn’t blocking outbound HTTPS to *.paradime.io.
Make sure your client supports remote MCP servers (over HTTP/SSE), not just local stdio servers.
If the browser sign-in never appears, check for a blocked pop-up and retry from the client.

The MCP is connected but tools return empty results

The connection is working, but the underlying integration may not be configured.

For warehouse tools (run_sql_query), confirm your data team has connected a warehouse to your workspace.
For repo tools (read_file, ripgrep_search, create_pull_request), confirm a code repository is connected and the connected user has access to it.
For catalog/lineage tools, your dbt™ project needs to have been parsed at least once in Paradime.

'Tool not found' or the AI client doesn't see Paradime tools

Some clients cache the MCP tool list at startup; try restarting the client after adding the connector.
In Claude and ChatGPT, ensure Paradime is enabled in the connectors menu of your current chat.
If you’ve recently disconnected and reconnected, the old connection may still be cached. Remove and re-add the server in the client.

I'm in multiple workspaces and the agent uses the wrong one

Use the switch_workspace tool: ask the agent to switch context: “Switch to the marketing workspace before continuing.”

The agent is making too many tool calls / responses are slow

This is usually a sign the underlying client is sending the wrong context to the model. A few things to try:

Be specific in your prompt: “In the dbt catalog, find models that ref stg_orders” routes more efficiently than “find anything related to orders”.
On large monorepos, prefer search_catalog over ripgrep_search for catalog-aware queries.
If using a smaller model, switch to a larger context model (Claude Sonnet/Opus, GPT-5) for complex multi-step tasks.

FAQ

What happens when I leave my organisation?

When your Paradime account is deactivated, every MCP connection and token tied to it stops authenticating automatically. Any AI client still configured will fail on its next call. There are no leftover credentials to chase down.

How do I revoke a client's access?

Open Settings → MCP Access and click Disconnect on the client. It loses access immediately; reconnecting requires going through the browser sign-in again. Legacy tokens are deleted from the Legacy tokens tab on the same page.

Does connecting a client give it elevated access?

No. A connected client inherits exactly the permissions of your Paradime user. If you can’t see the marketing workspace in Paradime, the MCP can’t either. If you’re a read-only user, the MCP can read but not write.

Are MCP requests audited?

Yes. All MCP tool calls are logged against your user account in Paradime, the same way warehouse queries and Bolt runs are.

How much does this cost?

The Paradime MCP Server is included with all paid Paradime plans, and free for business and read-only seats. Token consumption on the AI side (Claude, ChatGPT, etc.) is billed by your AI provider, not by Paradime.

Can I restrict which tools an MCP client can use?

You can use the configure page to set which tools are allowed, denied, and need permission before executing.

Slack Bot Agent

Programmable Agent

Bolt Pipeline Agent

Copilot

MCP Server

Context & Customization

DinoAI Tools

Settings & Credits

Paradime MCP server: connect AI clients to your data

Before you start

Step 1: Copy your MCP server URL

Step 2: Add Paradime to your client

Claude Desktop & claude.ai

Claude Code

Cursor

GitHub Copilot

OpenCode

Kiro

Amazon Quick

Other clients

Step 3: Verify the connection

Manage connected clients

Legacy tokens

Available tools

Code & repository

Data warehouse & catalog

dbt Discovery

Bolt orchestration

Workspace management

Web & research

Troubleshooting

FAQ

​Before you start

​Step 1: Copy your MCP server URL

​Step 2: Add Paradime to your client

Claude Desktop & claude.ai

Claude Code

Cursor

GitHub Copilot

OpenCode

Kiro

Amazon Quick

Other clients

​Step 3: Verify the connection

​Manage connected clients

​Legacy tokens

​Available tools

​Code & repository

​Data warehouse & catalog

​dbt Discovery

​Bolt orchestration

​Workspace management

​Web & research

​Troubleshooting

​FAQ

​Related

Before you start

Step 1: Copy your MCP server URL

Step 2: Add Paradime to your client

Step 3: Verify the connection

Manage connected clients

Legacy tokens

Available tools

Code & repository

Data warehouse & catalog

dbt Discovery

Bolt orchestration

Workspace management

Web & research

Troubleshooting

FAQ

Related