Build custom AI on Quanta

There are a couple of requirements you must pass to start with Quanta for Custom AI:

• A Quanta-enabled subscription with the relevant entitlement.
• An AI tool, assistant, or custom agent runtime that supports MCP.
• Supported MCP protocol versions (the default version is bolded): 2024-11-05, 2025-03-26, 2025-06-18, and 2025-11-25.
• Authentication follows the same OAuth/SSO model already used for Quanta in Claude — see Simplify Access with SAML SSO and the sign-in steps on Quanta in Claude. No separate authentication setup is required for this path.

Additional requirements identified during implementation and testing will be added here.

We ran connectivity testing against the Quanta MCP server and can confirm it works with the following tools and systems:

• Google Gemini Enterprise
• Microsoft Copilot (native connector)
• Microsoft Copilot Studio (custom connector)
• Cursor
• GitHub Copilot
• Junie
• Kiro
• OpenAI Codex
• Visual Studio
• Devin/Windsurf
• Amazon Q
• Amazon Q Developer CLI
• Antigravity CLI
• Google ADK
• Langchain
• Python with the MCP SDK

[PLACEHOLDER — this list reflects the clients currently in scope for testing per the PRD; confirm against final QA sign-off before publishing, and update/remove any client that doesn’t pass.]

The Quanta MCP server currently exposes the following tools: search_documents, qda_query, qda_export, get_full_document, lookup_entities.

Three ready-made Skills are available today, each combining an IDC-grounded query with a repeatable output format:

• Cadenced PPT — recurring market-commentary slide decks.
• Competitive Board — vendor and competitive tracking dashboards.
• Automated ICP — ideal-customer-profile fit scoring.

Full descriptions, usage examples, and the complete and growing catalog — including dataset schemas, recipes, and the changelog — are maintained on GitHub: [PLACEHOLDER — link pending, repo not yet public].

This path reuses the support tiers already published on Quanta in Claude: MCP connector issues are handled 24/7 for Priority 1 (complete outage) and Priority 2 (major degradation); setup and installation support runs Monday–Friday, 8:30 AM–5:00 PM ET.

[PLACEHOLDER — explicit uptime target, if any. Ask Jorge or Giorgio what, if anything, we have in place before publishing this section.]

For any technical issues or questions, you can reach out to IDC’s support team via Email at idc_support@idc.com.