IDC customers can now use Claude to query IDC’s forecasts, market data and research through the IDC Quanta connector. Anthropic’s October 28, 2026, case study also describes IDC’s company-wide adoption of Claude, including engineering, product, sales and marketing workflows. The customer-facing integration and the internal rollout are distinct developments: one provides access to market intelligence; the other supplies company-reported productivity results. Anthropic’s case study covers both.
October 28 is not the connector’s initial release date. IDC’s accompanying post, published that day, says Quanta has been available in Claude since July 2026, without specifying an exact July launch date.
For existing customers, the useful next step is concrete: check your IDC entitlement, have a Claude administrator enable the integration, and try a research task whose sources you can inspect. The setup documentation offers a firmer basis for that decision than the headline time-saving claims.
What the IDC Quanta Connector Adds
The integration uses the Model Context Protocol, or MCP, to connect Claude to IDC’s research service. IDC describes its connector as a live MCP server that provides access to subscribed research documents and quantitative data.
IDC distributes the integration through a plugin in Claude’s plugin directory. That package contains two parts:
- The IDC connector, which links Claude to IDC’s knowledge base.
- The IDC Quanta skill, invoked with
/idc-quanta, which supplies instructions for research workflows such as market-share analysis, vendor evaluation and total addressable market analysis.
The skill also includes navigation and attribution rules. Available workflows depend on the customer’s entitlements, so installing the package does not unlock every IDC product. IDC’s developer documentation lists Research, Trackers, Spending Guides and Black Book among the subscribed content that can support answers.
This distinction matters in practice. The connector supplies access to evidence; the skill guides how Claude uses it. Neither removes the need to define the market, period, geography and business question clearly.
Who Can Use It, and Where It Works
IDC Quanta customers using Claude are eligible to add the connector. For the organization-wide installation described in IDC’s documentation, the prerequisites are Claude Enterprise Edition or Claude Teams Edition, plus organization-administrator rights.
An administrator enables the plugin, while IDC access controls determine which users can retrieve subscribed content. IDC says group-level access is enforced through OAuth single sign-on. Readers without Quanta access are directed to contact IDC or request a demo. IDC’s setup documentation explains the administrative requirements.
The official sources list slightly different supported surfaces:
| Claude surface | Published support |
|---|---|
| Desktop app | Listed by Anthropic and IDC |
| Mobile app | Listed in Anthropic’s case study and IDC’s announcement |
| Cowork | Listed in Anthropic’s case study |
| Web and Chrome extension | Listed in IDC’s developer documentation |
| Microsoft Office add-ins | Listed in both; IDC’s documentation names Excel, Word and PowerPoint |
These lists come from Anthropic’s announcement and IDC’s developer documentation. Neither explains whether every plugin feature behaves identically across all surfaces.
I’d start an organizational pilot in the desktop app because both sources explicitly list it. Once access and citations work as expected, the team can check the Office or other surface it actually plans to use.
How to Enable IDC Quanta in Claude
IDC documents the following administrator setup:
- Open Organization settings → Libraries → Plugins in Claude.
- Select + Add plugins → Directory.
- Search for IDC Quanta and add the plugin.
- Choose how the plugin will be distributed across the organization.
The distribution setting controls whether users receive the plugin automatically and whether they can disable it:
| Setting | Effect |
|---|---|
| Plugin available for install | Users can install or uninstall it themselves, subject to the administrator’s directory-visibility configuration. |
| Installed by default | The administrator pre-installs it; users can disable it. |
| Not available | The plugin is hidden and cannot be installed. |
| Required | The administrator pre-installs it; users cannot disable it. |
IDC says directory-listed plugins update automatically when it publishes a new version. These steps and settings come from its official installation guide.
For a small pilot, I’d choose Plugin available for install. That lets entitled users opt in without imposing a new integration on everyone. A broader deployment can use Installed by default once the organization has checked access and output quality.
After enablement, an entitled user can invoke the skill by typing /idc-quanta in chat. Administrators should distinguish plugin distribution from research access: making the plugin visible across the organization does not grant everyone the same IDC subscriptions.
Start With a Question You Can Audit
IDC and Anthropic describe three customer workflows: competitor briefs, vendor shortlists and comparisons between a customer’s budget and IDC forecasts. The examples below adapt those documented uses into practical starting points; they are suggested prompts, not tested outputs.
Build a Competitor Brief With Defined Boundaries
A useful request specifies the competitor, market, geography and reporting period. Ask Claude to separate market position, product capabilities and acquisition activity, with sources attached to each section.
For example:
/idc-quanta
Prepare a competitor brief for [company] in [market] and [region].
Use the latest available IDC research and state its publication dates.
Cover market share, product capabilities and recent acquisitions.
Separate sourced findings from your analysis, and cite each section.
The slash command invokes the packaged skill; the remaining text defines the assignment. Anthropic describes competitor briefs covering these topics, supported by IDC research. Its claim that a day’s research can be completed in minutes is a vendor-reported example, not an independently measured turnaround time. The case study provides the underlying scenario.
Turn a Vendor Shortlist Into a Decision Aid
IDC’s procurement example produces an Excel scorecard containing three vendors, drawing on its procurement database and MarketScape research.
The useful input is your actual environment: existing architecture, required integrations, deployment constraints and evaluation criteria. Ask Claude to identify missing evidence alongside strengths and weaknesses.
My view is that the scorecard’s main value is making the evaluation easier to inspect. A shortlist becomes more useful when colleagues can see why a vendor scored well and which requirements still need validation. Three ranked names alone leave too much unexplained.
Compare a Budget on Matching Terms
The documented budget workflow lets a CFO upload next year’s IT budget and compare it with IDC’s forecast.
Before requesting differences, specify the fiscal period, geography, currency and spending categories. An internal software budget and a broad IT-spending forecast may cover different things. Ask Claude to show how it maps categories and to flag anything it cannot align.
That is an analytical precaution, not an additional documented product feature. It follows from the comparison itself: a precise percentage difference is useful only when both sides measure comparable spending. describes the budget workflow.
Frequently Asked Questions
3 questions
1Can Any Claude User Add IDC Quanta?
The integration is for IDC Quanta customers. IDC’s documented organizational setup requires Claude Teams or Enterprise and an administrator to enable the plugin.
