MCP server ideas: 20 gaps in the Claude connector directory

Search for MCP server ideas and you get project lists: a weather server, a notes server, a database wrapper. They teach the protocol. They do not tell you whether anyone needs the thing you build, or whether it already exists.

We checked the other side. BigIdeasDB's Agent Index is a census of the Claude and ChatGPT connector directories: 7,000+ connectors, 68,000+ declared tools and 22,000+ software vendors from Capterra and G2, matched against 1M+ complaints. This article uses the Claude side, since that is where MCP servers are listed with tool detail. It turns the gaps into 20 ranked ideas, each with the evidence row behind it. Servers to use instead of build are in the best MCP servers for founders.

• Best evidence-stacked idea: an HR and recruiting action server. Whitespace 100.0, 36 Claude connectors, 6.9% vendor reachability.
• Biggest untouched pool: camp management, 69 vendor listings, none matched.
• Only flagged write gap: real estate, 678 read-tool declarations against 89 write-tool declarations.
• Money: builders say the server is the distribution layer, not the product. See can an MCP server earn.

An MCP server is a small program that exposes tools, data or prompts to an AI assistant through the Model Context Protocol. The assistant calls a tool, such as list_invoices or create_task, and the server talks to the underlying system. Tools fall into classes: read (look something up), write (change something), transactional (book, pay, order) and admin. In the Claude directory 95.3% of connectors run as remote servers and 4.7% run locally. If you want to connect one to your own work first, our guide to using MCP with Claude covers setup, and MCP servers for AI research shows a working example.

Filter by the type of gap, or sort by the signal you trust most. Click an idea to jump to its evidence card. Systemic complaints are Capterra pain points flagged as systemic in the matching software category.

Ranking is rule-based, so you can check it. Ideas fall into four tiers. Within a tier, the order is stated below.

1. Demand gap (ideas 1-3). Capability clusters where complaint demand per connector is highest. The whitespace score counts complaints matching the cluster per connector in it. Ranked by whitespace score.
2. Zero-connector category (4-15). Software categories with 30 or more vendor listings and no matched connector. Ranked by systemic Capterra complaints, then vendor listings.
3. Action gap (16-17). Places where agents can read but few connectors can change anything.
4. Structural bet (18-20). Ideas supported by the shape of the directory but not by a complaint signal. Highest risk, listed last on purpose.

This is a different cut from our vertical readiness study, which rates 54 industries on whether agents can run them end to end. Here the unit is the tool you could ship. For ideas that are products on top of connectors rather than the connector itself, see SaaS ideas for AI agents.

The cluster table shows connector supply against complaint demand. The top three are the clearest demand-side gaps. Compare them with the bottom rows, where connectors are plentiful and demand is thin.

This is the largest block and the most buildable. Of the 22,000+ vendor listings in our reference set, only 6.4% are matched to a connector, which leaves 21,000+ without one. Look at categories rather than vendors: 258 categories have 30 or more listings, and 45 of them have none matched. Each card below is one of those categories, ranked by how many companies report systemic complaints about the incumbent software. If a vendor has no connector, its buyers cannot ask an assistant about their own data. That is the opening.

One caution applies to every card here. Matching is by name and conservative, so a connector may exist under a name we did not match. Search the directory by hand before you commit a week to any of these. The Agent Index lets you do that in a minute.

A pattern runs through the complaint side of these cards: reporting. Certification tracking, EHS, florist and construction bid software all list inadequate or inflexible reporting among their top complaints. That is why most of these ideas start read-only. A read tool that answers a reporting question in plain language is the cheapest way into a category. Our B2B SaaS ideas study found the same thing from the product side: 21 of 70 complaint-ranked ideas were reporting layers.

What an agent can do matters as much as what it can see. Across all declared tools, 53.2% are read, 26.7% write, 1.9% admin and only 0.8% transactional. A further 16.7% we could not classify, and 0.7% are meta tools. The gap matrix compares reads against writes by data domain.

Healthcare, travel and search also read far more than they write, though the gap matrix does not flag them. Do not read the unflagged rows as proof of a gap. They are a reason to look closer.

These three rest on how the directory is built, not on a measured complaint. They carry the most risk. We list them because the structure is unusual enough to be worth a look.

The missing system of record deserves a second look, because it explains the rest. For all 18 wide-open verticals, the blocking slot is the system of record, and the gap is rated durable. Most of the other software slots in those verticals already have a connector. The full breakdown by industry is in AI agent whitespace by vertical.

The bottom of the cluster table is the warning list. Docs and knowledge bases score 0.5 with 368 Claude connectors. AI models and agents score 0.2 with 238. Web search and research score 0.1 with 312. Finance and markets has 125 Claude connectors and a 0.5 score, and only 23 of them can write.

These are not dead categories. They are categories where supply already exceeds the complaints we can match, so a new entrant needs a better data source, not a better wrapper. The same logic applies to any generic note, file or search server. The most common tool names are search (270 servers), list_projects (153) and whoami (123). If your server's main tool has one of those names, you are entering the most crowded part of the directory.

Competition is not the same as a bad idea. A crowded accounting cluster still showed a gap in bookkeeper-practice software. The test is whether you have a wedge, not whether anyone else is there. To validate a wedge before you build, use the checklist in how to validate a startup idea.

Search for cool MCP server ideas on Reddit and the threads look nothing like our table. In two r/mcp threads about creative use cases, people describe a turkey-smoker controller, a smart wardrobe that checks your calendar, a dice-and-encounter server for tabletop role-play, and an Apple Health explorer. They are fun and several are clever. None names a buyer.

The business-shaped answers are quieter. One commenter built a server for their company's ERP system and used OCR to automate job and part entry. Another summarized and indexed internal infrastructure modules for agents. Both are internal tools for a known user with a known cost of doing it by hand. That matches a published survey of 46 engineers who build MCP servers at work, which found internal usage well ahead of public usage.

“I created a MCP for our ERP system and have started to create applications and use OCR to import and automate a lot of the job and part entry.”r/mcp

“I just really suck at marketing to get it out there. I already have a few testimonials that it's helped others' workflow.”r/mcp

The second quote is the other half of the story. Building is not the bottleneck. Finding the buyer is. That is why this list starts from vendor categories and complaint volume rather than from what is fun to wire up. If you want to add Reddit research to your own server, our guide to MCP servers for Reddit market research shows the pattern.

Once you have an idea, the directory also tells you how big to make it. Of the 2,700+ Claude connectors that declare tools, the median has 13 tools and the 90th percentile has 53. 1,200+ declare ten or fewer. Only 303 declare more than 50.

Rank matters here, with a caveat. Directory rank is an ordering, not an install count, because no usage data exists in either directory. Still, among the 300 highest-ranked Claude connectors with tools, the median is 10 tools and just 15 exceed 50. Small servers sit near the top.

• Ship 5 to 15 tools. The median server is in that band. Past 50, you are in the top 11% by size and the minority among popular servers.
• Name tools for the job, not the API. 46,000+ of 51,000+ distinct tool names appear on one server only. Generic names like search collide with 270 other servers. Specific names such as list_expiring_certifications do not.
• Go remote unless you must stay local. 95.3% of Claude connectors are remote. Local servers (132) suit files and desktop apps, not business software.
• Add one write at a time. 62.7% of connectors already write, but only 0.8% of tools are transactional. Anything that moves money or books a job should confirm first.

Before you build, check what you can already connect: our MCP server for market research shows a working read-first design, and the BigIdeasDB MCP exposes the same data you see here, so an assistant can run these lookups for you.

Often not directly. In a r/mcp thread on monetization, the top answers agree:

“Most MCP servers aren't really standalone paid products. They're usually just part of a bigger service you're already paying for.”r/mcp

“Simple. You dont. You monetize the value around the painpoint/workflow that the MCP solves.”r/mcp

“The actual MCP server isn't the valuable thing. The valuable thing I've built is the data ingestion and a custom search index. MCP is just the distribution vehicle.”r/mcp

Our revenue data is consistent but thin. In the TrustMRR set, 34 startups mention MCP in their name or description. 15 report revenue above zero, which is below our 30-row floor for publishing a median, so we do not publish one. The best sits in the $10K-$15K MRR band. Treat that as proof of possibility, not a benchmark.

What does this mean for the ideas above? The zero-connector ideas are strongest as the front end of a product, not as a paid server. Sell the reconciled report, the booked appointment or the tracked certification. Use MCP so the buyer reaches it from the assistant they already use. Price the outcome, then check demand for it the same way you would for any micro product, as in our micro SaaS ideas study. If you are building for the ChatGPT side instead, see ChatGPT app ideas and the ChatGPT apps directory map.

Supply is accelerating, which shortens the window on any open slot. Monthly additions to the Claude directory ran between 37 and 79 from January to May 2026, then jumped to 310 in June and 766 in each of July and August. June to August added 1,800+ connectors, against 300+ in the five months before.

Read this as Claude directory additions only. ChatGPT publishes no date, so there is no matching series. The identical July and August counts may reflect batch listing rather than organic growth. Either way, a category with no connector today is unlikely to stay that way for long.

Methodology and data sources

Every figure comes from a live read-only query run on October 20, 2026, unless marked as quoted.

Limitations: read these before you build

• Zero matched is not zero exists. Name matching is conservative. Search the directory by hand before building any zero-connector idea.
• A missing connector may mean a closed API. Some vendors offer no public interface. A connector you cannot build is not an opportunity.
• Complaints are a demand signal, not a buyer. Interview five people in the category before you build.
• Whitespace is relative. A score of 100.0 means the match cap was hit, not that demand is unbounded.
• Idea cards describe patterns, not build plans. The Agent Index holds 1,700+ agent-product ideas with sources. We do not reproduce their scores or plans here.
• Directory rank is not popularity. There are no install counts. Our “small servers rank higher” finding is an ordering, not usage.
• Security and compliance sit with you. Healthcare, payroll and payment tools carry legal duties this article does not cover.

For deeper research on a single idea, try the business idea evaluator, read the complaint analysis guide or learn how the idea validation tool works.

FAQ

BigIdeasDB is an AI research suite that finds, validates and sizes product opportunities from 1M+ real complaints and data points. Start with a free scan of your own niche, or see how to find SaaS ideas.