Does Codex support the Fabric MCP server?

Yes. Codex connects to the Fabric MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.

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

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

Which Fabric tools can Codex 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 Codex?

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

What if Codex doesn't show Fabric tools?

Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.

Connect Fabric to Codex (MCP setup guide)

Ask Codex to use the data factory execute query tool in Fabric
Ask Codex to use the one lake delete directory tool in Fabric
Ask Codex to use the docs api examples tool in Fabric
Ask Codex to use the data factory create pipeline tool in Fabric
Ask Codex to use the one lake list workspaces 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 the server and sign in
The Codex CLI, IDE extension and ChatGPT desktop app share this config.
```
codex mcp add metorial --url <your-magic-mcp-url>
codex mcp login metorial
```
3. Check the connection
Type /mcp in Codex to see Metorial and its Fabric tools.

Once Fabric is enabled in Metorial, teammates sign in with SSO and get the same connection in Codex, 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.

Limit which Fabric tools Codex sees with enabled_tools and disabled_tools on the metorial server in config.toml.
Set default_tools_approval_mode to auto, prompt, writes or approve. writes prompts only for tools that are not marked read-only.
Type /mcp in the composer to see the connected servers.
Override the approval behavior for a single Fabric tool with tools.<tool>.approval_mode.

Metorial is listed but tools are missing: Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.
Metorial times out at startup: Codex waits 10 seconds by default. Raise startup_timeout_sec under [mcp_servers.metorial] in ~/.codex/config.toml.
Long tool calls fail after a minute: The default tool timeout is 60 seconds. Raise tool_timeout_sec for the metorial server in config.toml.

Based on the Codex MCP documentation.

Frequently asked questions

Common questions about connecting Fabric to AI agents with Metorial.

Does Codex support the Fabric MCP server?
Yes. Codex connects to the Fabric MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.
Do I need an API key to connect Fabric to Codex?
No. You sign in to Fabric once through Metorial, and Codex uses that connection. No API keys go into Codex's settings.
Which Fabric tools can Codex 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 Codex?
Yes. Role-based access control decides who can use Fabric and which of its tools appear in Codex, and every call is logged with the person's identity.
What if Codex doesn't show Fabric tools?
Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.