AI builders guide · Last updated November 18, 2026

Best MCP servers for Codex in 2026: 8 founder picks, ranked, with the config that works

Most Codex MCP lists rank developer tools. This one ranks eight servers for a founder: research first, then the servers that ship and check what Codex builds, with the config format taken from OpenAI's docs.

8
Servers ranked
360+
Tools in the #1 server (BigIdeasDB Desktop)
93.5%
Of 40+ tool connectors can write or change things
11
Median tools per connector in the directories

What are the best MCP servers for Codex?

Short answer

BigIdeasDB Desktop is the best MCP server for Codex if you are deciding what to build: one click connects it, and Codex gets 360+ local research tools. The hosted BigIdeasDB MCP is #2. Then GitHub, Context7, Playwright, Stripe, Supabase and Filesystem for building and shipping.

An MCP server is a program that gives an AI agent tools and data through the Model Context Protocol. In Codex you add one with codex mcp add or a [mcp_servers.name] table in config.toml, then run /mcp to confirm it loaded.

Codex is OpenAI’s agent. It is included on the ChatGPT Free plan, and most people use it only to write code. It also works as a research and planning agent when you give it the right tools. The pages that rank today for this query are server directories, a Reddit list and two developer roundups that rank GitHub, Context7 and Playwright. None of them says which plans OpenAI lists MCP for, none counts the tools each server adds, and none covers research data for a founder. This page does, and it ties to our guide on whether Codex is free. For the same ranking on the ChatGPT side, see best MCP servers for ChatGPT, and for every client at once see best MCP servers for founders.

The 8 best MCP servers for Codex, ranked

#ServerWhat it doesInstallCostBest for
1BigIdeasDB DesktopLocal research data: Reddit, Trends, app stores, YouTube, businesses for saleOne-click Connect in Desktop settingsOne-time purchase, no AI billFinding and validating what to build
2BigIdeasDB hosted MCP50 tools across 13 data sources, 1M+ complaintsURL plus two credential headersPro planDocumented demand, revenue, funding
3GitHubRepos, issues, pull requests, Actionscodex mcp add github --url ...Needs a GitHub account and tokenShipping the code Codex writes
4Context7Current library documentationcodex mcp add context7 -- npx ...Free key recommendedFewer wrong API calls
5PlaywrightDrives a real browsercodex mcp add playwright npx ...Open source, needs Node.js 20+Testing the app Codex built
6StripeYour Stripe account, docs and Atlascodex mcp add stripe --url ...Uses your Stripe accountPrices, customers, revenue questions
7SupabaseYour Supabase projectscodex mcp add supabase --url ...Needs a Supabase accountDatabase work, read-only first
8FilesystemFiles in folders you allowcodex mcp add filesystem -- npx ...Free, MIT licenceA folder outside the project
Ranked for a founder who uses Codex to decide what to build, build it and check it. Source: each vendor's official documentation and OpenAI's MCP page, read November 18, 2026. Cost describes the MCP connection, the account behind it may charge separately.

How did we rank these MCP servers?

We ranked them on November 18, 2026 from official docs only: OpenAI’s Model Context Protocol page, each vendor’s own README or docs, and OpenAI’s pricing page. The author builds BigIdeasDB, so read the top two slots with that in mind. The logic is below and every claim is checkable.

  • Job for a founder (heaviest weight). Does the server help you decide what to build, build it, or check it? Research data ranks first because a wrong idea wastes every later hour.
  • Data Codex cannot get alone. Codex already edits files in your project inside its sandbox. Servers that bring outside evidence or reach another system rank above servers that repeat what Codex does.
  • Documented Codex setup. A server with an install line in the vendor’s own docs ranks higher than one we had to assemble.
  • Blast radius. Servers that can write, delete or move money rank lower than read-first ones, because a wrong call costs more.

What we verified: the config format, the codex mcp commands and the plan wording from OpenAI, and the install lines, costs and tool counts from the vendors. What we did not do: run every server inside every Codex version.

The 8 servers, one by one

#1Research, local

1. BigIdeasDB Desktop: local research data for Codex

BigIdeasDB Desktop is a local research app that collects evidence from Reddit, Google Trends, app stores, search suggestions, YouTube, developer forums, marketplaces and businesses for sale on your own computer. Codex does the thinking on your own plan, so BigIdeasDB adds no AI bill. In Settings, press Connect on the Codex row and Desktop writes a [mcp_servers.bigideasdb-desktop] entry into Codex’s config.toml, so Codex used anywhere can call its tools. It also finds the codex CLI on your machine and runs it in its own chat with the tools attached. It ranks first because it answers the question that decides everything else: should this be built. See Connect your AI and the tools reference.

The catch: it is the biggest tool list on this page, so enable it for research sessions and switch it off when you build. Desktop is a one-time purchase that started at $9 and rises $1 with every sale (live price on the pricing page), and it is included with the Basic and Pro plans. It is not free. Keep it open, because the tools run inside it. Read Codex market research for the workflow.

Tools
360+
Install
One click in Settings
Runs on
Your Mac or Windows PC
Cost
One-time, no AI bill
#2Research, hosted

2. BigIdeasDB hosted MCP: documented demand and revenue

The hosted BigIdeasDB MCP gives an agent outside research data: 50 tools across 13 data sources, including Capterra and G2 complaints, live Reddit, app reviews, Upwork demand, SaaS revenue benchmarks, funded companies, the Stripe Index and businesses for sale. It is a Pro feature with limits of 1,000 requests a day and 100 a minute across all your clients. It uses a remote URL and two credential headers, so the Codex entry in the next section uses the documented env_http_headers field to keep your secret out of the file. See the MCP feature page and tools reference.

How it differs from Desktop: Desktop collects fresh evidence locally and serves none of our database. The hosted MCP serves the database and collects nothing. Pro users can connect both. Desktop does not proxy the hosted server.

Tools
50
Data sources
13
Complaint corpus
1M+
Cost
Pro: $349 lifetime or $49/mo
#3Code

3. GitHub: ship what Codex writes

GitHub’s own Codex guide gives this line: codex mcp add github --url https://api.githubcopilot.com/mcp/ --bearer-token-env-var GITHUB_PAT_TOKEN. It reads repos, issues, pull requests and Actions. The README says the default toolsets are context, repos, issues, pull requests and users, and it has a --read-only flag that skips every write tool. GitHub tells you to scope the token to least privilege and never commit it. It ranks third because shipping comes after deciding. Best for a founder who already has a repo.

Documented tools
93 in 22 toolsets
Default toolsets
45 tools
Auth
Token or OAuth
#4Docs

4. Context7: current library docs, two tools

OpenAI’s own MCP page uses Context7 as its example and calls it “a free MCP server for developer documentation”: codex mcp add context7 -- npx -y @upstash/context7-mcp. Its README lists two MCP tools, resolve-library-id and query-docs, and recommends a free API key for higher rate limits. It is the cheapest server on this page in tool count. Best for a builder who is not a developer by trade and cannot spot a stale API call.

Tools
2
Install
npx, STDIO
Cost
Free key recommended
#5Browser

5. Playwright: let Codex test the app it built

The Playwright MCP README gives a Codex line: codex mcp add playwright npx "@playwright/mcp@latest", and the matching [mcp_servers.playwright] table with command = "npx". It lists 72 tools, but 47 sit behind opt-in capability flags (network, storage, devtools, vision, PDF, testing), so the default is 25. Leave the flags off. Best for clicking through your own checkout or sign-up page and catching what broke. A browser can also open pages you did not write, so keep approvals on.

Documented tools
72
Default
25
Needs
Node.js 20+
#6Payments

6. Stripe: ask questions about your own revenue

Stripe’s docs give a Codex line: codex mcp add stripe --url https://mcp.stripe.com. Fifteen tools, but stripe_api_read and stripe_api_write reach most of the Stripe API, so the surface is wider than the count. Stripe marks some actions “Human confirmation” (refunds, sending money), says to turn on your client’s tool approval, and warns about prompt injection when you combine it with other servers. From December 2026 Stripe MCP stops accepting full-access secret keys, so use OAuth or an agent API key. Best once you have customers.

Documented tools
15
Install
codex mcp add stripe --url
Auth
OAuth or agent key
#7Database

7. Supabase: database work, read-only first

Supabase’s docs show Claude Code steps, not Codex, so the line below combines OpenAI’s --url option with Supabase’s documented URL parameters: codex mcp add supabase --url "https://mcp.supabase.com/mcp?project_ref=<project-ref>&read_only=true&features=database,docs". We have not run that exact line. Supabase’s page says to scope to one project, turn on read-only mode, restrict feature groups, and never give the server to customers. It also warns that elicitation prompts are a guardrail, not a guarantee. Best once you have a live database, and never pointed at production for a first test.

Documented tools
40
Scope
project_ref
Safety
read_only=true
#8Files

8. Filesystem: a folder outside your project

The reference Filesystem server reads and writes only the directories you list. Its --read-only flag registers only the tools that cannot change files, and the server enforces that whatever the client allows. We use codex mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem --read-only /path/to/folder, built from the README’s flag and OpenAI’s command. It ranks last because OpenAI’s sandbox already lets Codex read and edit the project folder, so add this only for a folder outside it, such as a folder of interview notes.

Tools
15
Safety
--read-only flag
Licence
MIT

How do you add an MCP server to Codex?

Run codex mcp add, or edit the config file by hand, then restart Codex and type /mcp to see what loaded. Per OpenAI’s MCP docs, the ChatGPT desktop app, Codex CLI and IDE extension share one config, by default ~/.codex/config.toml, so you set it up once.

  1. Add it from the command line. For a local server, put the launch command after --. For a remote one, use --url.
  2. Or edit config.toml. Each server is a [mcp_servers.<name>] table. A local (STDIO) server needs command and optionally args, env and cwd. A remote (Streamable HTTP) server needs url.
  3. Sign in if it needs OAuth. Run codex mcp login <name>.
  4. Restart Codex, then check. In the terminal UI run /mcp. Outside it run codex mcp list.

The command form, from OpenAI’s docs:

codex mcp add context7 -- npx -y @upstash/context7-mcp
codex mcp list

The same server as a config.toml entry, also from OpenAI’s docs:

[mcp_servers.context7]
command = "npx"
args = ["-y", "@upstash/context7-mcp"]

A remote server with a token kept in an environment variable, using the same table format. This one is GitHub’s own Codex example:

[mcp_servers.github]
url = "https://api.githubcopilot.com/mcp/"
bearer_token_env_var = "GITHUB_PAT_TOKEN"

The hosted BigIdeasDB MCP uses two credential headers, X-Client-Id and X-Client-Secret. OpenAI documents env_http_headers as a map of header names to environment variable names, so this keeps the secret out of the file. We built it from those two documents and have not tested every Codex version:

[mcp_servers.bigideasdb]
url = "https://bigideasdb.com/api/mcp/bigideasdb-mcp"
env_http_headers = { "X-Client-Id" = "BIGIDEASDB_CLIENT_ID", "X-Client-Secret" = "BIGIDEASDB_CLIENT_SECRET" }

Two options matter later. enabled = false turns a server off without deleting it, and enabled_tools limits which of its tools Codex sees. Both are in the OpenAI docs and both help with the usage limit below. You can scope a server to one project with a .codex/config.toml inside a trusted project. The longer how-to for the research servers is in Connect your AI and Connect the MCP to Claude and other clients.

Does Codex have MCP support on the Free plan?

Codex supports MCP, and OpenAI does not say either way for Free. Its plan table lists MCP for Plus, Pro, Business, Enterprise and API key, and has no column for Free or Go (OpenAI pricing page, November 18, 2026). Codex itself is included on Free and Go per OpenAI’s help center, so the honest instruction is: add the server, restart, run /mcp, and see whether it loaded on your plan.

Free is $0 and limited to quick tasks, and OpenAI publishes no message number for it. Plus is $20 a month and lists 350 to 3,000 GPT-6 Luna local messages per five-hour window. If a server will not load on your plan, nothing else here breaks: Desktop also runs Codex inside its own chat with its tools attached. One r/ClaudeCode thread on Codex Free put the risk plainly, with top comments warning that free access is probably heavily subsidized and limits can change. The full plan table is in Is Codex free?

Why do fewer MCP servers stretch your Codex limit?

Every MCP server adds context to your messages and uses more of your limit. That is OpenAI’s own wording in its tips for making usage last: “Limit the number of MCP servers you use. Every MCP server adds more context to your messages and uses more of your limit. Disable MCP servers when you don’t need them” (OpenAI pricing page, November 18, 2026).

Tools documented per MCP server: BigIdeasDB Desktop 360+, GitHub 93, Playwright 72, BigIdeasDB hosted 50, Supabase 40, Filesystem 15, Stripe 15 and Context7 2.BigIdeasDB Desktop360+GitHub93Playwright72BigIdeasDB hosted50Supabase40Filesystem15Stripe15Context72
Tools each server documents, from each vendor's own docs, November 18, 2026. Default sets are smaller for GitHub (45) and Playwright (25). OpenAI publishes no per-tool token cost, so this counts tools, not tokens.
ServerDocumented toolsOn by defaultSource
BigIdeasDB Desktop360+All of themDesktop MCP tools reference
GitHub93 in 22 toolsets45 in the default toolsetsGitHub MCP server README
Playwright7225 (24 core, 1 tab)Playwright MCP README
BigIdeasDB hosted50All of themBigIdeasDB MCP tools reference
Supabase40Storage group off by defaultSupabase MCP docs
Filesystem15All, fewer in read-only modeFilesystem server README
Stripe15All of themStripe MCP docs
Context72All of themContext7 README
The same counts with what is switched on by default. Verified November 18, 2026.

We do not know how many tokens a tool costs, and OpenAI does not say. What we can count is how big real tool lists get. In BigIdeasDB’s Agent Index, a census of the ChatGPT and Claude connector directories, the median connector that publishes a tool list has 11 tools, and 13.5% have 40 or more.

MeasureValueNote
Connectors that publish a tool list3,315Of 7,065 in the ChatGPT and Claude directories
Median tools per connector11Half publish 11 or fewer
Connectors with 40+ tools447 (13.5%)The 90th percentile is 49 tools
Include a write, admin or transactional tool, all59.2%1,961 of 3,315
Include a write, admin or transactional tool, 40+ tools93.5%Bigger servers can change more things
Agent Index, 7,065 connectors, 68,000+ declared tools. Tool-declaring means the connector publishes a tool list. Verified November 18, 2026.

Two habits follow. First, run the smallest set that does the job. A research session needs Desktop. A build session needs GitHub and maybe Context7. Switch the rest off with enabled = false, or trim a big server with enabled_tools. Second, check your usage: the usage dashboard shows current limits, and /status in the CLI shows what remains during a session. Plus counts are estimates, not fixed limits, and Pro has no five-hour limit.

Are MCP servers safe to use with Codex?

An MCP server is a set of actions you hand to an agent, so treat it like giving a new contractor your accounts. The safe default is read-only access, a narrow scope and approvals on. The directory data above shows why: of connectors with 40 or more tools, 93.5% include a tool that writes, administers or moves money.

  • Start read-only where the server has a switch. Filesystem has --read-only, GitHub has --read-only, and Supabase has read_only=true with project scoping. Stripe marks some actions as needing human confirmation in your Dashboard, and tells you to turn on your client’s tool approval.
  • Use the Codex sandbox and approvals. OpenAI’s sandbox page defines read-only (inspect files, no edits or commands without approval), workspace-write (the default for local work) and danger-full-access, which removes the boundaries. Keep the first two. Run /permissions in the CLI to change mode.
  • Set approvals per server. OpenAI documents default_tools_approval_mode with writes, which prompts for tools that are not marked read-only, and per-tool approval_mode overrides. A tool’s read-only mark is whatever the server author declared, so for broad grants go by what the token can do.
  • Keep secrets out of the file. Use bearer_token_env_var or env_http_headers. Never commit config.toml with a token in it.
  • Beware prompt injection. Text inside a ticket, page or database row can tell an agent to act. Stripe and Supabase both warn about it. Do not combine a server that reads untrusted pages with one that can send money or change data.
  • Test on a copy. Use a Stripe sandbox, a Supabase branch or a throwaway repo before you point an agent at live data.

Can Codex connect to Claude Code?

Not as an MCP server. OpenAI’s docs say the codex mcp-server command and the standalone codex-mcp-server binary have been removed, and that the experimental app server is not an MCP server. Roundups that still tell you to run codex mcp-server are out of date. Codex does keep supporting external MCP servers, which is what this page covers.

What does work is giving both agents the same tools. MCP servers are separate from the agent, so a server you add to Codex can also be added to Claude Code. BigIdeasDB Desktop is built that way: one local connection serves Claude Code, Codex, Cursor and others, and your research stays in the same project whichever agent you use. For the agent comparison, read Codex vs Claude Code.

Are MCP servers free to use?

The protocol is open and many servers carry no fee, but the account behind a server decides your bill. From the docs: Context7 recommends a free API key, Playwright needs only Node.js 20 or newer, Filesystem is MIT licensed, and GitHub, Stripe and Supabase act on your own accounts. Supabase says branching needs a paid plan and project creation can cost money, which is why it asks for confirmation first.

For the research servers, the honest line is this: Codex is $0 on the Free plan, BigIdeasDB Desktop is one small one-time payment with no monthly AI bill, and the hosted BigIdeasDB MCP is part of Pro at $349 lifetime or $49 a month. If you want the idea side first, run the free niche scan. If you are choosing what to do with the build, see how to make money with Codex and use Codex to find business ideas.

What do Codex users say about MCP servers?

They like a few servers and worry about the weight of many. In a popular r/codex thread listing favourite MCP servers (300+ upvotes, 60+ comments), the replies split between praise for Context7 and Chrome DevTools and two recurring worries (r/codex thread, verified November 18, 2026).

“Doesn’t enabling MCPs use up more tokens?”via r/codex, 3 upvotes
“I stopped using context7 because it was bloating up token usage.”via r/codex
“Keep the server list per project, not global. An agent working on one project only sees the tools that project needs.”via r/mcp

Those match OpenAI’s tip. The r/mcp thread behind the third quote is about a person who counted the servers their agent could reach and found more than they expected, and the replies agree that servers added for one task tend to stay. Prune on a schedule.

What this cannot tell you

  • No token cost per server. OpenAI does not publish one, so the chart counts documented tools, not tokens. More tools is a proxy for more context, not a measurement.
  • Tool counts move. Vendors add tools often. Counts are from each README or docs page on November 18, 2026. Playwright and GitHub counts include opt-in groups unless marked default.
  • The Agent Index is hosted directories. It covers ChatGPT and Claude connectors, not local servers, and 98.6% of Claude connectors publish a tool list against 12.7% of ChatGPT apps, so tool figures lean Claude. Verbs are classified automatically and 16.7% of tools are unknown.
  • We did not test every line. The Supabase and Filesystem install lines and the hosted BigIdeasDB entry are built from OpenAI’s documented fields and each vendor’s parameters. The GitHub, Context7, Playwright and Stripe lines are the vendors’ own.
  • Free-plan MCP is unconfirmed. OpenAI lists MCP for paid plans and API key and is silent on Free and Go. Run /mcp on your plan.
  • Ranking reflects a founder use case and our own product sits at the top. A developer maintaining a large codebase may reasonably rank GitHub first.

Methodology and data sources

Population. Eight servers chosen for a founder who uses Codex to research, build and check a product. Facts come from official pages read on November 18, 2026. The census counts rows in the Agent Index (7,065 connectors, 3,315 that publish a tool list). Counts are rounded down with a plus sign where the corpus is large.

SourceWhat it givesSizeLimitation
OpenAI, Model Context Protocolconfig.toml format, codex mcp commands, /mcp, approvals1 pageDoes not state Free-plan MCP support
OpenAI, pricingPlans, Plus estimates, limit tips, plan feature table1 pageNo Free message number; estimates change
OpenAI, sandboxSandbox modes and approval policies1 pageDescribes Codex, not third-party servers
Vendor docs (GitHub, Context7, Playwright, Stripe, Supabase, Filesystem)Install lines, tools, auth, safety flags6 sourcesCounts change; Supabase shows no Codex line
Agent IndexTools per connector, write share7,065 connectors, 68,000+ toolsHosted directories, Claude-heavy disclosure, auto-classified verbs
BigIdeasDB MCP docs and Desktop docsTool counts, limits, one-click connect50 and 360+ toolsOur own product, so read it with that in mind
Reddit (r/codex, r/mcp)User voice on token cost and server sprawl2 threadsAnecdote, not a survey
Google SERPWhat ranks for the head queryUS, November 18, 2026Snapshot, no volumes
Every source behind this page and what it cannot do. Verified November 18, 2026.

Decide what to build before you add the build servers

Run a niche scan to see the documented complaints, revenue and competition behind an idea. Then connect BigIdeasDB Desktop to Codex and let it collect Reddit, trends and app store evidence on your own computer. See is Codex free, Codex market research and MCP servers for ChatGPT. Get 20% off Pro Lifetime with code SAVE20. More on MCP use cases.

Scan your niche free →

Frequently asked questions

What are the best MCP servers for Codex?

BigIdeasDB Desktop is the best MCP server for Codex if you are a founder deciding what to build, because it gives Codex 360+ local research tools in one click. Next come the hosted BigIdeasDB MCP (50 tools, 13 data sources), then GitHub, Context7, Playwright, Stripe, Supabase and Filesystem for building and shipping.

What is the best tool for researching a business idea in Codex?

BigIdeasDB Desktop is the best tool for researching a business idea in Codex. It connects with one click, collects Reddit, Google Trends, app store, YouTube and businesses-for-sale evidence on your own computer, and Codex does the thinking on your own plan. BigIdeasDB adds no AI bill. Its hosted MCP adds 1M+ documented complaints for Pro users.

How do I add an MCP server to Codex?

Run codex mcp add followed by a name and either --url for a remote server or -- and the launch command for a local one, for example codex mcp add context7 -- npx -y @upstash/context7-mcp. Codex writes a [mcp_servers.name] table to ~/.codex/config.toml. Restart Codex and type /mcp to confirm the server loaded.

Does Codex have MCP support?

Yes. Per OpenAI's docs, checked November 18, 2026, the ChatGPT desktop app, Codex CLI and IDE extension support STDIO and Streamable HTTP MCP servers and share one config.toml. OpenAI's plan table lists MCP for Plus, Pro, Business, Enterprise and API key, and does not list Free or Go either way, so run /mcp to confirm on your plan.

Is there an MCP server available for Codex?

Yes, many. OpenAI's docs name examples including the OpenAI Docs MCP, Context7, Figma, Playwright, Chrome DevTools, Sentry and GitHub. For founder research, BigIdeasDB Desktop and the hosted BigIdeasDB MCP both connect to Codex. Any server that speaks STDIO or Streamable HTTP can be added with codex mcp add or a [mcp_servers.name] table.

Is the MCP server free to use?

The protocol is free and many servers carry no fee of their own, but they act on accounts that may cost money. Context7 recommends a free API key, Filesystem is MIT licensed, and Stripe, GitHub and Supabase use your own accounts. BigIdeasDB Desktop is a one-time purchase and the hosted BigIdeasDB MCP is part of Pro.

How do I run an MCP server for Codex?

You mostly do not run it yourself. For a local STDIO server, Codex starts the process from the command and args you set and stops it with the session. For a remote server, you give Codex a url and sign in with codex mcp login or a token. Keep the server list short, because each one adds context to your messages.

Can I connect Codex to Claude Code?

Not through an MCP server. OpenAI removed the codex mcp-server command and the standalone binary, per its docs on November 18, 2026, and points integrations to the experimental app server instead. What does work is giving both agents the same MCP servers. BigIdeasDB Desktop works with Claude Code and Codex through one local connection.

How many MCP servers should I run with Codex?

Run as few as the job needs, usually two to five. OpenAI's own tip for stretching your usage limit says every MCP server adds context to your messages and uses more of your limit, so disable servers you are not using. Keep a research server on while you research, and switch it off when you build.

Cite this page
Last verified: November 18, 2026
BigIdeasDB Research. (2026). Best MCP servers for Codex in 2026: 8 founder picks, ranked, with the config that works. BigIdeasDB. Retrieved from https://bigideasdb.com/best-mcp-servers-for-codex
Related research