Does Codex support the Dataforseo MCP server?

Yes. Codex connects to the Dataforseo 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 Dataforseo to Codex?

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

Which Dataforseo tools can Codex use?

All 20 Dataforseo tools your team allows, such as Get Task Result, SERP Search, On-Page Audit. Admins can narrow that list per team.

Can I control which teammates use Dataforseo in Codex?

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

What if Codex doesn't show Dataforseo tools?

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

Connect Dataforseo to Codex (MCP setup guide)

Ask Codex to use the get task result tool in Dataforseo
Ask Codex to use the serp search tool in Dataforseo
Ask Codex to use the on page audit tool in Dataforseo
Ask Codex to use the keyword research tool in Dataforseo
Ask Codex to use the domain intersection tool in Dataforseo

1. Enable Dataforseo in Metorial
In your Metorial portal, enable the Dataforseo 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 Dataforseo tools.

Once Dataforseo 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.

Get Task Result: Retrieve the results of a previously submitted asynchronous task by its task ID.
SERP Search: Retrieve Google search engine results pages (SERPs) for any keyword.
On-Page Audit: Start a website crawl for technical SEO auditing.
Keyword Research: Get search volume, CPC, competition metrics, and monthly trends for one or more keywords from Google Ads.
Domain Intersection: Find shared keywords between two domains to identify keyword overlap and content gaps.
Domain Analytics: Retrieve comprehensive analytics for a domain including WHOIS registration data and technology stack detection.
Domain Competitors: Discover domains competing for the same keywords in organic search.
Keyword Suggestions: Get keyword suggestions and related keywords based on a seed keyword using DataForSEO Labs.
Content Analysis: Search for and analyze web content mentioning a specific keyword or brand across the web.
Keywords for Site: Discover keywords relevant to a website or webpage using Google Ads keyword data.
Google Shopping Search: Search Google Shopping for product listings by keyword.
Backlinks Analysis: Analyze the backlink profile of any domain, subdomain, or URL.
AI Optimization: Run practical DataForSEO AI Optimization requests: AI keyword search volume, LLM mentions search, and live LLM response benchmarking for ChatGPT, Claude, Gemini, and Perplexity.
On-Page Results: Retrieve OnPage crawl results for a previously created audit task.
App Data: Create Google Play App Data API tasks for app searches, app information, and app reviews.
And 5 more on the Dataforseo MCP server page.

Limit which Dataforseo 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 Dataforseo 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 Dataforseo to AI agents with Metorial.

Does Codex support the Dataforseo MCP server?
Yes. Codex connects to the Dataforseo 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 Dataforseo to Codex?
No. You sign in to Dataforseo once through Metorial, and Codex uses that connection. No API keys go into Codex's settings.
Which Dataforseo tools can Codex use?
All 20 Dataforseo tools your team allows, such as Get Task Result, SERP Search, On-Page Audit. Admins can narrow that list per team.
Can I control which teammates use Dataforseo in Codex?
Yes. Role-based access control decides who can use Dataforseo and which of its tools appear in Codex, and every call is logged with the person's identity.
What if Codex doesn't show Dataforseo tools?
Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.