Introduction

Foundational runs a hosted Model Context Protocol (MCP) server at https://mcp.foundational.io/mcp. With Foundational connected, Cursor’s agent gets direct access to your end-to-end column-level lineage, table and column definitions, ownership and metadata, usage and cost signals, and the code behind your data assets. Before it suggests a change to a dbt model, Airflow DAG, or Spark job, Cursor can check the upstream sources, downstream dependencies, and existing definitions involved, so it writes safer code and avoids breaking changes.

This article covers two ways to connect Cursor: the install link (recommended), and manual setup in Cursor’s mcp.json file, which some enterprise setups require. Each user connects Cursor themselves.

Looking for a different tool?

See Use Foundational MCP with your AI tools for the full client list, use cases, and machine-to-machine authentication.

Before you begin

You need an active user account in the Foundational app. The MCP server authorizes against your Foundational identity and returns only the assets your account can already see.
Your network must allow outbound HTTPS to mcp.foundational.io.

Connection details

Both setups use the same values:

Server URL: https://mcp.foundational.io/mcp
Transport: Streamable HTTP. Cursor needs only the URL; there is no transport setting.
Authentication: OAuth 2.0 with Dynamic Client Registration. Sign in with your Foundational account. You don't need to create a client ID, secret, or API token.
Suggested name: foundational

Connect with the Install link (recommended)

Copy the link below, paste it into your browser’s address bar, and press Return (⏎) or Enter. When your browser asks to open Cursor, allow it.

cursor://anysphere.cursor-deeplink/mcp/install?name=foundational&config=eyJ1cmwiOiJodHRwczovL21jcC5mb3VuZGF0aW9uYWwuaW8vbWNwIn0=
Cursor opens an Install MCP Server dialog. Click Install.
Foundational now appears in Cursor's MCPs list. Click Authenticate and complete the Foundational sign-in in your browser.
After you sign in, Cursor redirects you back and shows Foundational as connected and ready to use.

Connect manually

Use this setup if your organization blocks install links.

In Cursor’s Agents window, click Customize in the left side panel.
Open the MCPs tab and click New MCP Server (at the bottom of the installed MCP connectors list). Cursor opens its mcp.json config file in the editor.
Add the Foundational server to the file, then save it:
```
{
  "mcpServers": {
    "foundational": {
      "url": "https://mcp.foundational.io/mcp",
      "headers": {}
    }
  }
}
```
If mcp.json already lists other MCP servers, add foundational inside the existing mcpServers object, alongside them.
Foundational now appears in Cursor’s MCPs list. Click Authenticate and complete the Foundational sign-in in your browser.
For more detail, see Model Context Protocol (MCP) in the Cursor documentation.

Verify the connection

In Cursor’s Customize > MCPs, Foundational shows as connected. The most direct check is to ask a question only Foundational can answer, such as:

"Using Foundational, list the downstream consumers of the dim_customers table."

If Cursor answers with real table, column, or dashboard names from your environment, the connection is working.

What to ask Cursor once connected

"Where does the fct_user_sessions table get its data from?"
"Which dashboards use the dim_products table?"
"Before I change this dbt model, which models and dashboards depend on it?"
"Are there any expensive tables that are unused?"
"List all tables containing columns tagged with pii and show their downstream consumers."

Troubleshooting

The install link does nothing

Some browsers and locked-down machines block links that open a desktop app. Use the manual setup above instead.

Foundational fails to load with Node.js or npx errors

These errors come from the npx mcp-remote bridge, not from Foundational. Cursor connects to Foundational directly, so you don't need the bridge. Remove any mcp-remote entry for Foundational from mcp.json and use the configuration above.

The sign-in fails or loops

Confirm you can sign in to the Foundational app (https://app.foundational.io) in the same browser. The MCP server authorizes your Foundational user account, so an expired session or a different single sign-on (SSO) account is the usual cause. If you can't sign in to the Foundational app, ask your IT or data administrator to invite you to Foundational.

Connection fails behind a corporate proxy or firewall

Allow outbound HTTPS to mcp.foundational.io. See Allowing IP access to Foundational.

Connect Foundational MCP to Cursor