Breaknorm
Sign inStart free

Product

SignalsPeopleCompaniesLocal businessesMCP and API

Plays

Post engagersTeam build-outChampion movedHiring surgeNewly fundedLookalikesAll plays

Data

Coverage by countryHiring dataJob changesEmail verificationCompanies by toolWho is hiringMarket mapsOutboundCompany profilesCompare
PricingDatasetsDocsSign in
Compare · api specs data formats

Model Context Protocol VS SAP IDoc

As of 30 October 2026, SAP IDoc is named by 523 companies and Model Context Protocol by 3,710; Model Context Protocol skews to companies under 200 people (42% vs 26%), SAP IDoc to companies over 1,000 (56% vs 31%).

As of 30 October 2026 · refreshed daily · counts move as websites, DNS and career sites are re-read.

The website-and-DNS footprint is not comparable between a marketing suite and a CRM: Model Context Protocol's script and mail records show on hundreds of thousands of small sites, SAP IDoc rarely leaves a trace outside its own apps. Compare on the job-posting numbers; use the footprint for reach.

Model Context Protocol: 2–200 employees
42%
SAP IDoc: 2–200 employees
26%
Model Context Protocol: 1,000+ employees
31%
SAP IDoc: 1,000+ employees
56%
Postings per company, 90 days
3.2 · 4.2
Website or DNS footprint
0 · 0
3,710companies name Model Context Protocol
523companies name SAP IDoc
0name both
11,870 · 2,172postings in 90 days, Model Context Protocol · SAP IDoc
02Side by side

Who chooses which

Share of each tool's companies in every segment. "Leans" marks a gap of more than two points.

By company size
SegmentModel Context ProtocolshareSAP IDocshareLeans
Self-employed642%51%even
2-10 employees2527%234%Model Context Protocol
11-50 employees49013%5210%Model Context Protocol
51-200 employees80022%6112%Model Context Protocol
201-500 employees54815%5110%Model Context Protocol
501-1000 employees40811%408%Model Context Protocol
1001-5000 employees61216%9518%even
5001-10000 employees1604%438%SAP IDoc
10,001+ employees37610%15329%SAP IDoc
By industry
SegmentModel Context ProtocolshareSAP IDocshareLeans
Technology & software1,93152%17834%Model Context Protocol
Business & finance services78121%479%Model Context Protocol
Manufacturing & industry2767%15630%SAP IDoc
Media & content1454%163%even
Commerce & trade993%387%SAP IDoc
Consumer services & leisure852%51%even
Utilities & infrastructure852%204%even
Public, community & associations822%31%even
Health care672%122%even
Transport, logistics & rental501%102%even
Property & construction481%122%even
Automotive301%214%SAP IDoc
By country
SegmentModel Context ProtocolshareSAP IDocshareLeans
United States2,39164%24547%Model Context Protocol
United Kingdom2858%316%even
Germany2126%10119%SAP IDoc
Canada1063%153%even
France1033%143%even
India521%194%SAP IDoc
Netherlands521%102%even
Sweden421%––outside top 12
Australia411%71%even
Spain331%––outside top 12
Brazil321%51%even
Poland321%71%even
Switzerland––122%outside top 12
Belgium––51%outside top 12
Postings by team (share of each tool's postings)
SegmentModel Context ProtocolshareSAP IDocshareLeans
Data & AI4,80533%311%Model Context Protocol
Software engineering4,10128%38514%Model Context Protocol
IT operations & business systems1,44010%1,84266%SAP IDoc
Product, program & project management6595%241%Model Context Protocol
Sales4613%50%Model Context Protocol
Engineering (non-software)2051%60%even
Marketing & communications1711%––outside top 12
Customer service & success1461%120%even
Design & UX1091%––outside top 12
General management & consulting761%231%even
Finance & accounting630%271%even
Business development & strategy620%––outside top 12
Logistics warehouse and transport––492%outside top 12
Research and science––90%outside top 12
Administration & office––60%outside top 12
Cite this

Quote the sentence with the date and the link. The numbers change daily; the link always shows the current ones.

SAP IDoc is named by 523 companies in job postings and Model Context Protocol by 3,710; 0 name both. (Breaknorm, 30 October 2026, https://breaknorm.co/compare/model-context-protocol-vs-sap-idoc)
How we know

Read from the source, not self-reported

Every number on this page can be traced to a page we crawled or a posting we read. Full methodology →

  • Job postingsRead hourly from career sites. A tool counts when the employer's own text names it as the team's system; both tools can count for one company.
  • Website and DNSScripts and embeds on the company's pages, plus SPF, DKIM, MX and CNAME records of its domain that point at the vendor.
  • SegmentsCountry, size and industry from the company profile built from its website.
  • Not a reviewNo ratings, prices or feature claims. For those, read the vendors.
FAQ

Model Context Protocol vs SAP IDoc: questions

Which is more used, Model Context Protocol or SAP IDoc?

By companies naming it in their own job postings, Model Context Protocol (3,710) over SAP IDoc (523). By website-and-DNS footprint, SAP IDoc (0 vs 0), because its scripts and mail records sit on many small company sites.

Who chooses Model Context Protocol?

42% of Model Context Protocol companies have 2 to 200 employees, against 26% for SAP IDoc. 31% of Model Context Protocol companies have over 1,000 employees, against 56% for SAP IDoc.

Do companies run both?

0 companies name both in their postings, usually Model Context Protocol in marketing and SAP IDoc in sales, or during a migration.

Where do these numbers come from?

From the employer's own text in job postings read hourly from career sites, and from scripts found on company websites in our crawl. No vendor data, no surveys.

Companies and people

Get either list your way

The same data as a search, over MCP and the API, as bulk files, or pushed to you as it changes.

Every company on either tool,
with the person who owns it

Filter on Model Context Protocol or SAP IDoc. Start free, no card.

  1. 01Sign up, no card
  2. 02Connect Claude, ChatGPT or an API key
  3. 03Ask for your market