Does Cursor support the Fabric MCP server?

Yes. Cursor connects to the Fabric MCP server through its MCP config file, pointed at your Metorial URL. You need Cursor with MCP support.

Do I need an API key to connect Fabric to Cursor?

No. You sign in to Fabric once through Metorial, and Cursor uses that connection. No API keys go into Cursor's settings.

Which Fabric tools can Cursor use?

All 36 Fabric tools your team allows, such as Docs Workload API Spec, Docs Platform API Spec, Docs Workloads. Admins can narrow that list per team.

Can I control which teammates use Fabric in Cursor?

Yes. Role-based access control decides who can use Fabric and which of its tools appear in Cursor, and every call is logged with the person's identity.

What if Cursor doesn't show Fabric tools?

Open the Output panel (Cmd+Shift+U), choose MCP Logs, and look for authentication or connection errors.

Connect Fabric to Cursor (MCP setup guide)

Ask Cursor to use the one lake list table namespaces tool in Fabric
Ask Cursor to use the data factory get pipeline tool in Fabric
Ask Cursor to use the core create item tool in Fabric
Ask Cursor to use the data factory list pipelines tool in Fabric
Ask Cursor to use the one lake create directory tool in Fabric

1. Enable Fabric in Metorial
In your Metorial portal, enable the Fabric MCP server and sign in with the account that owns the data. Access stays governed by your team policies.
2. Add Metorial to your MCP config
Use ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one.
```
{
  "mcpServers": {
    "metorial": {
      "url": "<your-magic-mcp-url>"
    }
  }
}
```
3. Sign in
Open Customize in the sidebar, find Metorial and sign in to load Fabric tools.

Once Fabric is enabled in Metorial, teammates sign in with SSO and get the same connection in Cursor, with only the tools their role allows.

One link covers every app you approve. See how the MCP gateway handles access, roles and audit logs for the whole company.

Docs Workload API Spec: Official upstream MCP name: docs_workload-api-spec.
Docs Platform API Spec: Official upstream MCP name: docs_platform-api-spec.
Docs Workloads: Official upstream MCP name: docs_workloads.
OneLake Download File: Official upstream MCP name: onelake_download_file.
OneLake List Tables: Official upstream MCP name: onelake_list_tables.
Data Factory Create Dataflow: Official upstream MCP name: datafactory_create-dataflow.
OneLake Get Table: Official upstream MCP name: onelake_get_table.
OneLake List Items: Official upstream MCP name: onelake_list_items.
OneLake List Files: Official upstream MCP name: onelake_list_files.
OneLake Delete File: Official upstream MCP name: onelake_delete_file.
OneLake List Table Namespaces: Official upstream MCP name: onelake_list_table_namespaces.
Data Factory Get Pipeline: Official upstream MCP name: datafactory_get-pipeline.
Core Create Item: Official upstream MCP name: core_create-item.
Data Factory List Pipelines: Official upstream MCP name: datafactory_list-pipelines.
OneLake Create Directory: Official upstream MCP name: onelake_create_directory.
And 21 more on the Fabric MCP server page.

Cursor picks MCP tools automatically when they are relevant, including in Plan Mode. Name a Fabric tool to steer it.
Cursor asks for approval before it uses an MCP tool by default. Click the arrow next to the tool name to check the arguments first.
Switch the Metorial server off from Customize in the sidebar without removing it.
Cursor shows each Fabric tool response in chat, with expandable views of the arguments and the result.

Metorial connects but tools are missing or failing: Open the Output panel (Cmd+Shift+U), choose MCP Logs, and look for authentication or connection errors.
Your company blocks the server: Enterprise admins approve remote servers in Team Settings, then MCP Configuration. Ask them to add a URL entry for your Metorial URL.
Cursor asks before every tool call: That is the default. Allowlist the Metorial tools you trust in your Run Mode settings to run them without a prompt.

Based on the Cursor MCP documentation.

Frequently asked questions

Common questions about connecting Fabric to AI agents with Metorial.

Does Cursor support the Fabric MCP server?
Yes. Cursor connects to the Fabric MCP server through its MCP config file, pointed at your Metorial URL. You need Cursor with MCP support.
Do I need an API key to connect Fabric to Cursor?
No. You sign in to Fabric once through Metorial, and Cursor uses that connection. No API keys go into Cursor's settings.
Which Fabric tools can Cursor use?
All 36 Fabric tools your team allows, such as Docs Workload API Spec, Docs Platform API Spec, Docs Workloads. Admins can narrow that list per team.
Can I control which teammates use Fabric in Cursor?
Yes. Role-based access control decides who can use Fabric and which of its tools appear in Cursor, and every call is logged with the person's identity.
What if Cursor doesn't show Fabric tools?
Open the Output panel (Cmd+Shift+U), choose MCP Logs, and look for authentication or connection errors.