# How AI recommends MCP and agent-native tools across 911,413 answers

> Across 911,413 organic AI answers recorded September 1 to November 19, 2026, only 18 buyer questions named MCP yet 6,292 answers surfaced MCP anyway (94.96% unprompted), and ChatGPT Search MCP mention share rose +127.12% from 0.660% in September to 1.499% in November. Inside narrow topics containing both traditional and agent/API/CLI prompts, adding developer or agent constraints flips the #1 recommended brand 55.00% of the time as review directories drop 10.67x and GitHub plus documentation take over.

HTML: https://parse.gl/research/how-ai-recommends-mcp-and-agent-native-tools · Site index: https://parse.gl/llms.txt · Published: 2026-11-20

When buyers ask AI search engines to recommend tools for AI agents, headless stacks, or Model Context Protocol (MCP) workflows, how often do engines bring up MCP unprompted, replace legacy category leaders, and change which sources they cite?

We analyzed 130,776 active organic buyer questions and 911,413 answers recorded September 1 through November 19, 2026 across ChatGPT Search (463,371 answers), Google AI Mode (440,174), a Claude (Opus 5) reference cohort (6,780), and Perplexity (1,088), measuring unprompted MCP growth, within-topic and within-market #1 brand flips alongside a 61-market split-half control, 58,092 citation links on MCP answers, and 2,549 AI-visibility answers.

## Key figures

- **of 6,292 MCP mentions occurred unprompted:** 94.96% (5,975 of 6,292 MCP answers surfaced MCP without an MCP prompt)
- **ChatGPT Search MCP mention growth (Sep to Nov):** +127.12% (Rose from 0.660% in Sep to 1.499% in Nov 2026 (2.72x Google AI Mode))
- **Within-topic #1 brand flip rate:** 55.00% (11 of 20 narrow topics flipped #1 under agent, API, or CLI constraints)
- **Collapse in review directory citation share:** 10.67x (Directories drop from 1.28% to 0.12% on agent/MCP/CLI prompts)

## 94.96% of 6,292 MCP mentions across 911,413 answers happened unprompted

Across 130,776 active organic buyer questions in Parse, 3,146 explicitly request agentic or developer integration capabilities (2,614 with 25,765 Sep 1 to Nov 19, 2026 answers across ChatGPT Search, Google AI Mode, and Perplexity). Most ask for APIs, SDKs, or webhooks (2,554 questions, 21,320 answers) or AI agent workflows (478 questions, 3,554 answers), plus 166 headless, 26 CLI, 4 Claude or Cursor, and just 18 explicit MCP questions (17 with 317 Sep-Nov answers).

Yet across 911,413 total answers over the same 80 days, AI engines brought up MCP or the Model Context Protocol 6,292 times. Fully 5,975 of those 6,292 answers (94.96%) surfaced MCP unprompted: 96.39% on ChatGPT Search (4,242 of 4,401; 0.950% of all 463,371 ChatGPT answers), 91.47% on Google AI Mode (1,694 of 1,852; 0.421% of 440,174 answers), 100.00% in the Claude (Opus 5) reference cohort (34 of 34; 0.501% of 6,780 answers), and 100.00% on Perplexity (5 of 5; 0.460% of 1,088 answers). Broader agentic phrasing appeared far wider: 28,750 answers discussed AI agents or agentic workflows, 3,495 named Claude Code, Claude Desktop, or Cursor, and 423 referenced llms.txt.

**Active agentic and developer buyer question demand across 130,776 organic prompts**

| Buyer constraint | Active questions | Questions answered | Sep-Nov answers | ChatGPT Search | Google AI Mode |
| --- | --- | --- | --- | --- | --- |
| MCP protocol (explicit) | 18 | 17 | 317 | 159 | 158 |
| AI agent workflow | 478 | 416 | 3554 | 1826 | 1722 |
| Claude or Cursor coding | 4 | 4 | 63 | 31 | 31 |
| Headless architecture | 166 | 121 | 1092 | 553 | 538 |
| API, SDK, or webhook | 2554 | 2118 | 21320 | 10793 | 10507 |
| CLI or command line | 26 | 18 | 200 | 102 | 98 |
| Any agent or dev constraint (union) | 3146 | 2614 | 25765 | 13069 | 12670 |

_Question counts and Sep 1 to Nov 19, 2026 answer volumes across ChatGPT Search, Google AI Mode, and Perplexity._

> Buyers rarely type MCP into their prompt yet, but AI engines proactively introduce MCP integrations in 95 of every 100 answers where MCP appears.

## ChatGPT Search MCP mention share surged 127.12% from September to November 2026

Month-over-month tracking from September 1 through November 19, 2026 shows MCP spreading fastest inside ChatGPT Search. Its share of organic answers mentioning MCP rose from 0.660% in September (1,063 of 161,053 answers) to 0.865% in October (1,627 of 188,181) and 1.499% in November 1 to 19 (1,711 of 114,137), a +127.12% jump in under three months.

Google AI Mode grew more modestly over the same dates: 0.390% in September (616 of 157,941 answers), 0.367% in October (641 of 174,501), and 0.552% in November 1 to 19 (595 of 107,732). By November 2026, ChatGPT Search named MCP 2.72x as often per answer as Google AI Mode.

**Monthly share of organic answers mentioning MCP by engine (Sep to Nov 2026)**

| month | ChatGPT Search | Google AI Mode |
| --- | --- | --- |
| Sep 2026 | 0.66% | 0.39% |
| Oct 2026 | 0.865% | 0.367% |
| Nov 2026 (1-19) | 1.499% | 0.552% |

_Percentage of all organic answers on ChatGPT Search and Google AI Mode mentioning MCP or Model Context Protocol (Nov covers Nov 1 to Nov 19, 2026)._

> ChatGPT Search crossed 1.5% of all organic answers mentioning MCP in November 2026, pulling 2.72x ahead of Google AI Mode.

Related: [Claude Code and Cursor AI visibility workflows](https://parse.gl/blog/claude-code-and-cursor-ai-visibility-workflows)

## Software, AI, and IT lead unprompted MCP mentions while Commerce and Finance emerge

Combining primary Parse industry groups from markets and questions across all three search engines shows unprompted MCP mentions clustering in software infrastructure while spreading into business operations. Outside the 4,659 unprompted MCP answers (2,216 distinct questions) sitting on questions without a mapped industry group, Software leads with 467 answers across 153 questions (328 ChatGPT Search, 139 Google AI Mode).

Artificial Intelligence follows at 328 answers across 92 questions (201 ChatGPT, 127 Google), ahead of Information Technology (180 answers across 61 questions), Internet Services (99 across 46), and Data and Analytics (72 across 37). Early non-devtools adoption already appears in Commerce and Shopping (32 answers across 7 questions), Professional Services (30), Collaboration (30), Financial Services (23), Apps (15), Science and Engineering (15), and Sales and Marketing (14).

**Top 10 categorized Parse industry groups by unprompted MCP answers**

| Item | Value |
| --- | --- |
| Software | 467 (153 questions) |
| Artificial Intelligence | 328 (92 questions) |
| Information Technology | 180 (61 questions) |
| Internet Services | 99 (46 questions) |
| Data and Analytics | 72 (37 questions) |
| Commerce and Shopping | 32 (7 questions) |
| Professional Services | 30 (10 questions) |
| Collaboration | 30 (9 questions) |
| Financial Services | 23 (10 questions) |
| Apps | 15 (10 questions) |

_Organic Sep 1 to Nov 19, 2026 answers mentioning MCP without an MCP prompt across mapped market/question industry groups (excludes 4,659 uncategorized answers)._

> MCP visibility is still anchored in Software, AI, and IT, yet commerce, finance, and collaboration categories already surface unprompted MCP setups.

## 55.00% of narrow topics flip #1 winners when agent, API, or CLI constraints enter the prompt

To test whether developer and agentic requirements overturn category winners even for the exact same narrow buyer job, we isolated all 20 single-intent Topics that contained both traditional buyer questions and agent, MCP, headless, API, or CLI questions (at least 10 Sep-Nov answers on each side). Exactly 11 of 20 topics (55.00%) replaced their #1 recommended brand.

In Transactional email services, Postmark (43.75% #1 share on standard prompts) lost to Resend (70.37% #1 share on developer/agent prompts). In Usage-based billing platforms, WithOrb (47.62%) lost to Stripe (55.00%). In Autonomous web research agents, Perplexity (86.67%) lost to Tavily (35.14%). In Passwordless authentication APIs, Yubico (34.48%) lost to Stytch (68.75%). In Identity verification APIs, Alloy (24.14%) lost to Sumsub (33.33%), and in PII redaction for LLM pipelines, Presidio (23.53%) lost to OpenAI (17.91%). In the 9 topics that kept their #1 brand (Modal, Checkr, LangChain, Instatus, Ramp, Aidoc, Cohere, Backstage, and Stripo), the incumbent was already built around developer APIs or model tooling.

**Within-topic #1 brand flips: traditional vs agent/API/CLI prompts (20 narrow topics)**

| Topic | Outcome | Standard #1 | Standard #1 (%) | Agent/Dev #1 | Agent/Dev #1 (%) | Leader shift |
| --- | --- | --- | --- | --- | --- | --- |
| PII redaction for LLM pipelines | Flipped | Presidio | 23.53 | OpenAI | 17.91 | -5.62 pts |
| Transactional email services | Flipped | Postmark | 43.75 | Resend | 70.37 | +26.62 pts |
| Invoice data extraction | Flipped | Veryfi | 29.82 | Microsoft | 52.27 | +22.45 pts |
| Autonomous web research agents | Flipped | Perplexity | 86.67 | Tavily | 35.14 | -51.53 pts |
| QR code creation and management | Flipped | Bitly | 45 | QR Code Monkey | 66.67 | +21.67 pts |
| Identity verification APIs | Flipped | Alloy | 24.14 | Sumsub | 33.33 | +9.19 pts |
| Usage-based billing platforms | Flipped | WithOrb | 47.62 | Stripe | 55 | +7.38 pts |
| CRM data enrichment | Flipped | Clay | 47.83 | Apollo | 36.84 | -10.99 pts |
| Crypto tax reporting | Flipped | TaxBit | 76.32 | Koinly | 83.33 | +7.01 pts |
| Crypto trading bot platforms | Flipped | Pionex | 13.33 | Binance | 88.24 | +74.91 pts |
| Passwordless authentication APIs | Flipped | Yubico | 34.48 | Stytch | 68.75 | +34.27 pts |
| Scale-to-zero serverless model inference | Held | Modal | 91.67 | Modal | 93.18 | +1.51 pts |
| Enterprise global background screening | Held | Checkr | 89.13 | Checkr | 85.71 | -3.42 pts |
| Multi-agent orchestration | Held | LangChain | 86 | LangChain | 88.46 | +2.46 pts |
| Hosted status pages | Held | Instatus | 82.35 | Instatus | 61.54 | -20.81 pts |
| Unlimited virtual card issuance via API | Held | Ramp | 95.65 | Ramp | 79.17 | -16.48 pts |
| FDA-cleared AI triage software for medical imaging | Held | Aidoc | 52.38 | Aidoc | 47.06 | -5.32 pts |
| RAG document reranking | Held | Cohere | 80.95 | Cohere | 75 | -5.95 pts |
| Developer documentation portals | Held | Backstage | 44.44 | Backstage | 92.86 | +48.42 pts |
| Transactional email template management | Held | Stripo | 84.62 | Stripo | 38.46 | -46.16 pts |

_Filter between flipped and held topics; every topic required at least 10 answers on both prompt sets (Sep 1 to Nov 19, 2026)._

> Developer-native brands like Resend, Tavily, Stripe, and Stytch take over first place once a prompt names APIs, headless pipelines, or agents.

Related: [AI recommendations by buyer type: enterprise, budget and compliance](https://parse.gl/research/does-adding-a-qualifier-change-ai-recommendations) · [Which prompt constraints unseat the AI leader?](https://parse.gl/research/ai-recommendations-prompt-constraints)

## Market-level flips (66.67%) mirror split-half baseline variance (68.85%), isolating brand-level surges as the cleaner signal

Across 57 broader active Markets meeting our 15-answer floor on both sides, 38 of 57 (66.67%) changed their #1 leader between traditional and developer/agent questions. To test how much of that broad-market turnover reflects sub-topic heterogeneity rather than developer constraints, we ran a split-half baseline control splitting only standard traditional questions in the same qualifying markets into two random halves (at least 15 answers per half). On that baseline control, 42 of 61 markets (68.85%) also flipped #1.

Because broad Parse markets combine multiple distinct buyer jobs (such as enterprise APM vs synthetic checks inside observability), narrow single-Topic flips (55.00%, 11 of 20) and large brand-level share swings inside matched markets provide the cleaner causal evidence. In Application Monitoring and Error Tracking, Sentry plunges -71.22 percentage points in #1 share (71.22% to 0.00%; overall mentions 79.62% to 6.07%) while Datadog surges +65.34 points (16.81% to 82.14%). In Chaos Engineering & API Mocking Tools, Gremlin drops -88.48 points (90.09% to 1.61%) while Mockoon climbs +29.03 points (0.00% to 29.03%). StackHawk jumps +56.82 points (0.00% to 56.82%), Resend jumps +56.72 points (0.00% to 56.72%), Tipalti jumps +63.34 points (1.36% to 64.71% as Wise falls -46.82 points), and Cloudflare jumps +55.42 points (24.58% to 80.00% as Amazon falls -46.18 points).

**Brand-level #1 share swings and 57 matched markets (traditional vs agent/API/CLI)**

| Brand | Market | Standard #1 (%) | Agent/Dev #1 (%) | #1 shift | Std mentioned (%) | Dev mentioned (%) |
| --- | --- | --- | --- | --- | --- | --- |
| Gremlin | Chaos Engineering & API Mocking Tools | 90.09 | 1.61 | -88.48 pts | 94.81 | 16.94 |
| Sentry | Application Monitoring and Error Tracking | 71.22 | 0 | -71.22 pts | 79.62 | 6.07 |
| Datadog | Application Monitoring and Error Tracking | 16.81 | 82.14 | +65.34 pts | 91.81 | 98.21 |
| Tipalti | Multi-Currency Business Accounts | 1.36 | 64.71 | +63.34 pts | 17.73 | 79.41 |
| Planet | Satellite Connectivity and Imaging Solutions | 10.57 | 71.05 | +60.48 pts | 47.99 | 97.37 |
| Datadog | Uptime & Synthetic Monitoring Tools | 24.07 | 84.55 | +60.48 pts | 49.51 | 95.45 |
| StackHawk | Security Validation and Red Teaming Platforms | 0 | 56.82 | +56.82 pts | 0 | 79.55 |
| Resend | Email and Messaging Delivery Platforms | 0 | 56.72 | +56.72 pts | 12.66 | 80.6 |
| Cloudflare | Edge Computing Platform Services | 24.58 | 80 | +55.42 pts | 44.52 | 100 |
| WeWeb | No-Code and Low-Code App Platforms | 0.34 | 55.56 | +55.22 pts | 9.48 | 77.78 |
| Zonos | E-commerce Tax Compliance Platforms | 20.75 | 73.48 | +52.73 pts | 44.59 | 90.91 |
| Amazon | Object Storage & Image CDN Services | 4.8 | 55.56 | +50.76 pts | 52.65 | 98.99 |
| The Odds API | Sports Betting Odds & Tracking Tools | 0 | 47.62 | +47.62 pts | 4.76 | 76.19 |
| Cloudinary | Object Storage & Image CDN Services | 50.35 | 3.03 | -47.32 pts | 87.11 | 42.42 |
| Wise | Multi-Currency Business Accounts | 46.82 | 0 | -46.82 pts | 79.55 | 67.65 |
| Amazon | Edge Computing Platform Services | 46.18 | 0 | -46.18 pts | 93.36 | 86.67 |
| Algolia | Managed Search Engine Platforms | 45.07 | 88.89 | +43.82 pts | 47.89 | 88.89 |
| ZeroBounce | Email Deliverability & Validation Tools | 17.54 | 61.29 | +43.75 pts | 38.6 | 100 |
| Instatus | Incident Management, Status Pages and Postmortems | 11.46 | 53.33 | +41.87 pts | 33.05 | 90 |
| Mux | Cloud Media Processing & Storage | 7.84 | 49.51 | +41.67 pts | 63.78 | 69.18 |

Showing 20 of 25 rows (Top 25 brand swings). Full CSV: /research/how-ai-recommends-mcp-and-agent-native-tools/dataset.csv

_Switch views between top brand-level #1 share swings and all 57 matched markets (66.67% market flip rate vs 68.85% split-half baseline control)._

> Use narrow topics and brand-level swings (such as Sentry to Datadog or Gremlin to Mockoon) rather than broad market rollups to measure agent-prompt competitiveness.

Related: [Research AI visibility across your market in Parse](https://parse.gl/use-cases/research-a-market)

## Review directories collapse 10.67x on agent, MCP, and CLI prompts while GitHub jumps 2.65x

When buyers add developer or agentic constraints inside Software, Information Technology, Artificial Intelligence, Internet Services, Developer Tools, and Data and Analytics markets, AI engines discard software review directories. Moving from standard buyer prompts (518,599 citation links across 80,496 answers) to agent, MCP, headless, and CLI prompts (5,116 links across 811 answers) cuts major review directory share (g2.com, capterra.com, gartner.com, trustradius.com, and softwareadvice.com combined) by 10.67x, from 1.28% down to 0.12% (and down to 0.86% on 32,167 API/SDK citations).

In place of directories, AI engines route straight to code and technical manuals: github.com jumps 2.65x from 1.44% on standard prompts to 3.81% on agent/MCP/CLI prompts, while documentation and developer sites climb from 16.75% on standard prompts to 26.97% on agent/MCP/CLI prompts and 35.55% on API/SDK prompts. Traditional SaaS marketing pages fall from 31.91% on standard prompts to 24.18% on agent/MCP/CLI prompts, while YouTube climbs from 3.20% to 4.53% and Reddit rises from 1.32% to 1.88%.

**Citation source share by prompt tier across technical Parse markets (%)**

| Item | Value |
| --- | --- |
| Standard prompts: Docs & dev sites | 16.75% |
| Standard prompts: SaaS marketing | 31.91% |
| Standard prompts: GitHub | 1.44% |
| Standard prompts: Review directories | 1.28% |
| API & SDK prompts: Docs & dev sites | 35.55% |
| API & SDK prompts: SaaS marketing | 24.74% |
| API & SDK prompts: GitHub | 1.87% |
| API & SDK prompts: Review directories | 0.86% |
| Agent, MCP & CLI: Docs & dev sites | 26.97% |
| Agent, MCP & CLI: SaaS marketing | 24.18% |
| Agent, MCP & CLI: GitHub | 3.81% |
| Agent, MCP & CLI: Review directories | 0.12% |

_518,599 standard citations, 32,167 API/SDK citations, and 5,116 agent/MCP/headless/CLI citations (Sep 1 to Nov 19, 2026)._

> Review sites carry almost zero weight (0.12%) when buyers specify agent, MCP, or CLI requirements; documentation and GitHub replace them.

Related: [GitHub repos, package registries, and docs architecture in AI search](https://parse.gl/research/github-repos-and-docs-architecture-in-ai-search)

## ChatGPT Search backs MCP answers with Docs (30.73%) and GitHub (4.01%), while Google leans on YouTube and Reddit

Across all 58,092 citation links recorded on MCP-mentioning or explicit MCP answers (49,205 on ChatGPT Search, 8,529 on Google AI Mode, 308 in the Claude Opus 5 reference cohort, and 50 on Perplexity), ChatGPT Search and Google AI Mode pull from opposing channels. ChatGPT Search assigns 30.73% of its MCP citations to documentation and developer sites (15,122 links) and 4.01% to github.com (1,971 links), while sending 0.00% to YouTube (0 links), 0.01% to Reddit (3 links), and 0.02% to third-party MCP registries (10 links).

Google AI Mode cites documentation and developer sites at 12.65% (1,079 links, 2.43x lower than ChatGPT) and github.com at 2.40% (205 links), while routing 9.32% of MCP citations to youtube.com (795 links), 3.47% to reddit.com (296 links), and 0.79% to third-party MCP directories (67 links: led by mcpmarket.com with 42 Google citations vs 3 ChatGPT, mcpservers.org with 16 vs 0, glama.ai with 4 vs 6, mcp.so with 4 vs 1, and pulsemcp.com with 1 vs 0). Across the broader agent-plus-MCP citation pool, top Reddit communities on Google AI Mode are r/ai_agents (184 citations), r/aiagents (19), r/geotoolsreview (18), r/devops (17), r/langchain (16), and r/localllama (15). Overall top cited root domains on MCP answers are microsoft.com (2,352 links), github.com (2,185), google.com (1,189), atlassian.com (1,182), amazon.com (1,128), youtube.com (795), github.io (785), and langchain.com (762).

**MCP answer citation breakdown across engines, registries, and technical subreddits**

| Engine | Citation links | Docs/Dev (%) | SaaS (%) | GitHub (%) | YouTube (%) | Reddit (%) | MCP registries (%) |
| --- | --- | --- | --- | --- | --- | --- | --- |
| ChatGPT Search | 49205 | 30.73 | 23 | 4.01 | 0 | 0.01 | 0.02 |
| Google AI Mode | 8529 | 12.65 | 25.17 | 2.4 | 9.32 | 3.47 | 0.79 |
| Claude (Opus 5) | 308 | 6.82 | 10.71 | 1.95 | 0 | 0 | 0 |
| Perplexity | 50 | 18 | 18 | 6 | 0 | 0 | 0 |

_Switch views between engine source mix (58,092 MCP citation links), MCP directories, and top technical subreddits._

> ChatGPT Search discovers MCP tools through product docs and GitHub; Google AI Mode discovers them through YouTube demos, Reddit threads, and MCP directories.

Related: [Perplexity vs ChatGPT Search vs Google AI Mode citations](https://parse.gl/research/perplexity-vs-chatgpt-vs-google-ai-mode-citations) · [Most cited domains in AI answers](https://parse.gl/research/most-cited-domains-ai-answers)

## In AI-visibility tools, MCP prompts flip ChatGPT rankings (Parse jumps 42x to 13.92%) while Google keeps 0%

We also audited our own category across 85 standard AI-visibility, GEO, and AEO buyer questions (2,391 answers) versus 5 explicit MCP AI-visibility prompts (158 answers: 79 on ChatGPT Search and 79 on Google AI Mode). On standard AI-visibility questions, established incumbents lead pooled brand-mention share: Otterly AI (51.07%), Peec AI (49.85%), Semrush (48.68%), TryProfound (40.28%, plus 17.61% #1 share), Ahrefs (36.89%), Scrunch (21.83%), Profound (11.25%), and SE Ranking (10.66%). On standard questions, LLM Pulse appears in 1.21% (29 of 2,391) and Parse appears in just 0.33% (8 of 2,391: 7 of 1,208 on ChatGPT Search and 1 of 1,176 on Google AI Mode).

On the 5 MCP AI-visibility prompts, ChatGPT Search reshuffles dramatically: LLM Pulse jumps from 0.41% to 84.81% (67 of 79 answers, 13.92% #1 share), Peec AI reaches 70.89%, Otterly AI 62.03%, SE Ranking 60.76%, Ahrefs 54.43%, and Cite42 (mcp.cite42.dev) appears in 41.77% (33 of 79). Parse (parse.gl) jumps 42x from 0.33% standard visibility to 13.92% on ChatGPT Search MCP prompts (11 of 79 answers, winning #1 in 7 of 11 mentions at 1.82 average rank, backed directly by parse.gl citations). Yet on Google AI Mode for the same 5 MCP prompts, Parse receives 0 of 79 mentions (0.00%), trailing Peec AI (46.84%), SE Ranking (45.57%), Otterly AI (45.57%), Profound (34.18%), LLM Pulse (27.85%), and Radarkit (18.99%, 11.39% #1). That gap mirrors our source telemetry: ChatGPT Search retrieves Parse via /llms.txt and /docs/mcp.md, whereas Google AI Mode relies on Reddit, YouTube, and external MCP registries where Parse lacked coverage during this window.

**Standard vs MCP AI-visibility tool visibility across 2,549 organic answers**

| Brand | Prompt tier | Domain | Mentioned in (%) | #1 share (%) | Mentions | Answers |
| --- | --- | --- | --- | --- | --- | --- |
| Peec AI | MCP/API prompts | peec.ai | 58.86 | 6.96 | 93 | 158 |
| LLM Pulse | MCP/API prompts | llmpulse.ai | 56.33 | 10.76 | 89 | 158 |
| Otterly AI | MCP/API prompts | otterly.ai | 53.8 | 3.8 | 85 | 158 |
| SE Ranking | MCP/API prompts | seranking.com | 53.16 | 4.43 | 84 | 158 |
| Ahrefs | MCP/API prompts | ahrefs.com | 32.28 | 1.9 | 51 | 158 |
| Profound | MCP/API prompts | profound.com | 25.95 | 0.63 | 41 | 158 |
| TryProfound | MCP/API prompts | tryprofound.com | 22.15 | 1.9 | 35 | 158 |
| Cite42 | MCP/API prompts | mcp.cite42.dev | 21.52 | 2.53 | 34 | 158 |
| Scrunch | MCP/API prompts | scrunch.com | 21.52 | 0 | 34 | 158 |
| Promptwatch | MCP/API prompts | promptwatch.com | 14.56 | 1.9 | 23 | 158 |
| Radarkit | MCP/API prompts | radarkit.ai | 9.49 | 5.7 | 15 | 158 |
| Semrush | MCP/API prompts | semrush.com | 7.59 | 1.9 | 12 | 158 |
| Parse | MCP/API prompts | parse.gl | 6.96 | 4.43 | 11 | 158 |
| Otterly AI | Standard prompts | otterly.ai | 51.07 | 8.62 | 1221 | 2391 |
| Peec AI | Standard prompts | peec.ai | 49.85 | 5.14 | 1192 | 2391 |
| Semrush | Standard prompts | semrush.com | 48.68 | 4.39 | 1164 | 2391 |
| TryProfound | Standard prompts | tryprofound.com | 40.28 | 17.61 | 963 | 2391 |
| Ahrefs | Standard prompts | ahrefs.com | 36.89 | 2.89 | 882 | 2391 |
| Scrunch | Standard prompts | scrunch.com | 21.83 | 0.13 | 522 | 2391 |
| Profound | Standard prompts | profound.com | 11.25 | 4.48 | 269 | 2391 |

Showing 20 of 25 rows (Pooled: MCP vs Standard). Full CSV: /research/how-ai-recommends-mcp-and-agent-native-tools/dataset.csv

_Filter by prompt tier or switch views for engine-level splits across ChatGPT Search and Google AI Mode (Sep 1 to Nov 19, 2026)._

> Technical docs and /llms.txt lift ChatGPT Search visibility on MCP queries immediately, yet Google AI Mode ignores vendors without YouTube, Reddit, and registry coverage.

Related: [Best MCP servers for marketing, SEO, and AI visibility](https://parse.gl/blog/best-mcp-servers-for-marketing-and-seo) · [Inspect Parse MCP tools and public endpoints](https://parse.gl/mcp)

## Study scope, counting rules, and observational boundaries

This study covers 130,776 active non-archived organic buyer questions and 911,413 answers recorded from September 1 through November 19, 2026 across ChatGPT Search (463,371 answers), Google AI Mode (440,174), a Claude (Opus 5) reference cohort (6,780), and Perplexity (1,088). Question buckets classify prompts via keyword matching on question text, while MCP, llms.txt, Claude/Cursor, and AI-agent mention shares count explicit occurrences inside full answer bodies.

Within-topic comparisons cover the 20 narrow Topics with at least 10 Sep-Nov answers in both traditional and agent/API/headless/CLI prompt pools. Within-market comparisons cover 57 qualified active Markets with at least 15 answers per side, paired against a 61-market split-half control on traditional questions alone (68.85% baseline flip rate). Industry totals combine market and question Parse industry groups (leaving 4,659 unprompted MCP answers outside mapped groups). In the AI-visibility cohort, TryProfound (tryprofound.com) and Profound (profound.com) are tracked as separate canonical brand records in Parse, and Parse recorded 40 total organic mentions across 24 prompt-engine combinations over the 90-day window.

## Operator playbook for winning MCP and agent-native recommendations

Treat agent-native buyer questions as a distinct competitive arena rather than assuming broad category winners carry over. In half of narrow topics (55.00%), adding API, headless, agent, or CLI constraints swaps out #1, and review directories lose 90% of their citation weight (1.28% down to 0.12%).

Build dual-channel MCP visibility: publish server-rendered docs, /llms.txt, native Markdown twins, and a public GitHub README for ChatGPT Search (30.73% docs and 4.01% GitHub on MCP citations), while shipping YouTube setup walkthroughs, authentic Reddit engineering answers, and verified listings on mcpmarket.com, mcpservers.org, glama.ai, and pulsemcp.com for Google AI Mode. Use Parse MCP tools (search_answers, search_cited_pages, query_metrics, check_brand, fetch_live_pages) directly inside Claude Code or Cursor to monitor both channels side by side.

**MCP and agent-native AI visibility checklist**

| Channel or workflow | Study benchmark | Team action |
| --- | --- | --- |
| Prompt tracking by topic and constraint | 55.00% #1 flip inside narrow topics | Track agent, MCP, API/SDK, headless, and CLI buyer questions alongside standard category questions inside each topic. |
| ChatGPT Search evidence stack | 30.73% docs/dev; 4.01% GitHub on MCP | Publish clean /docs/mcp guides, /llms.txt, .md twins, and a public GitHub server repo linking straight to your primary domain. |
| Google AI Mode evidence stack | 9.32% YouTube; 3.47% Reddit; 0.79% registries | Publish concise YouTube MCP demos, contribute real solutions in r/ai_agents and r/devops, and register on mcpmarket.com and mcpservers.org. |
| Review directory reallocation | 10.67x directory collapse (1.28% to 0.12%) | Shift technical buyer budget away from generic review directories toward developer documentation, code samples, and live MCP specs. |

> Win ChatGPT Search through clean docs, /llms.txt, and GitHub, and win Google AI Mode through YouTube, technical subreddits, and MCP directories.

Related: [Research AI visibility across your market in Parse](https://parse.gl/use-cases/research-a-market) · [Compare competitors on agent vs standard prompts](https://parse.gl/use-cases/compare-competitors) · [Query MCP and citation metrics via Parse MCP](https://parse.gl/mcp) · [Best MCP servers for marketing and SEO](https://parse.gl/blog/best-mcp-servers-for-marketing-and-seo) · [Claude Code and Cursor AI visibility workflows](https://parse.gl/blog/claude-code-and-cursor-ai-visibility-workflows) · [HTML token bloat vs. Markdown twins and llms.txt](https://parse.gl/research/agent-readability-html-vs-markdown-and-llms-txt)

## Method

We analyzed 130,776 active organic buyer questions (3,146 requesting MCP, AI agents, Claude or Cursor, headless, API/SDK, or CLI capabilities) and 911,413 organic AI answers collected September 1 through November 19, 2026 across ChatGPT Search (463,371), Google AI Mode (440,174), a Claude (Opus 5) reference cohort (6,780), and Perplexity (1,088), alongside 20 matched narrow topics, 57 matched markets (plus a 61-market traditional split-half control), 58,092 citation links from MCP answers, and 2,549 answers across standard and MCP AI-visibility prompts.

## Data

- [Full study dataset (CSV)](https://parse.gl/research/how-ai-recommends-mcp-and-agent-native-tools/dataset.csv): All 282 rows covering prompt demand buckets, monthly MCP growth, 20 topics, 57 markets, 40 brand swings, MCP registries, subreddits, and AI-visibility benchmarks.

## Sources

- [Anthropic: Introducing the Model Context Protocol](https://www.anthropic.com/news/model-context-protocol)
- [Model Context Protocol specification](https://modelcontextprotocol.io/docs/2026-07-28/getting-started/intro)
- [The /llms.txt specification (llmstxt.org)](https://llmstxt.org/)
- [Semrush: How technical SEO factors affect AI citations](https://www.semrush.com/blog/technical-seo-impact-on-ai-search-study/)
- [Ahrefs: 67% of ChatGPT top 1,000 citations are off-limits to marketers](https://ahrefs.com/blog/chatgpts-most-cited-pages/)

## For agents

- [Study dataset (CSV)](https://parse.gl/research/how-ai-recommends-mcp-and-agent-native-tools/dataset.csv)
- Any brand's shares and rivals, with 95% ranges: `https://agent.parse.gl/v1/tools/check_brand?subject=%3Cbrand-domain%3E`
- Third-party cited pages missing a brand: `https://agent.parse.gl/v1/tools/search_cited_pages?args=%7B%22pages%22%3A%22third_party%22%2C%22listsBrand%22%3Afalse%2C%22filter%22%3A%7B%22brand%22%3A%5B%22%3Cbrd_id%3E%22%5D%2C%22brandRule%22%3A%22not_named%22%2C%22market%22%3A%5B%22%3Cmkt_id%3E%22%5D%7D%7D`
- Search the index: `https://parse.gl/api/public/search?q=<words>`

Reuse: Figures and tables on this page are free to republish with attribution: a link to https://parse.gl/research/how-ai-recommends-mcp-and-agent-native-tools beside them. A standard followed link (dofollow) is preferred.

- No account: Public figures and up to 5 examples per list, about 120 brands a day per address.
- Free account: $5 in credit, your brand's first check (20 buyer questions) and a free weekly check.
- After your first top-up: Exports and deeper search results. The first top-up starts at $5.
- Live checks: $0.01 per question per engine ($0.05 on Gemini and Claude).
- Full public answers and pages: 25 free per day, then $0.005 each.
- Public answers older than 90 days: $0.001 each the first time your workspace counts or lists one, then yours.
- An agent can save work before signup: `POST https://agent.parse.gl/v1/workspaces`
- Connect an assistant: `https://agent.parse.gl/mcp`

[Prices](https://parse.gl/pricing.md) · [Map of the site](https://parse.gl/llms.txt)
