Integrations
Sculptor is not a chat box with a copy button. Import what you already have, connect the tools that hold evidence and delivery, and serve board-approved strategy to every AI assistant your team uses — with governance and audit trails.
Integrations follow the same loop as your strategy work — not a pile of disconnected OAuth tiles. Bring in context, ground it with evidence, govern what you approve, track whether delivery matches the plan, and serve only signed-off priorities to the AI tools your team already uses.
Library uploads, G-IMPORT review, public URL fetch (web research), and drive bridges.
Analytics, search, repos, and social connectors ground CEP and capture-gap assumptions.
Humans approve artefacts and authority ranks before anything is shared outward.
Execution scorecards and work tools — Jira, Linear, Azure DevOps — hold the delivery thread.
Strategy Context MCP and org MCP servers query governed priorities with audit logs.
Files, pasted text, public URLs (when web research is on), and linked drives — into a governed graph, not a one-shot chat paste.
Upload PDF, Word, Excel, Markdown, HTML, CSV, JSON, or images to Source documents. Corpus import (G-IMPORT) proposes artefact mappings from extracted text for human review before anything enters the library. During coached and agentic runs, public http(s) URLs can be fetched when your organisation enables web research (SerpAPI). Google Search Console and Bing Webmaster link verified site properties for search evidence; Google Drive and OneDrive bridges bring file context from your storage.
Ground Category Entry Points and capture-gap analysis with live search and traffic data.
Google Search Console powers capture-gap evidence today. Other analytics connectors store encrypted credentials for expanding CEP evidence — behaviour, document, and social proof in one map.
Link repositories for document evidence and upcoming backlog handoff.
Connect GitHub or GitLab so Sculptor can reference repo context and prepare initiative handoff as issues when your delivery workflow is ready.
Bridge strategy artefacts to the tools your teams already run on.
Jira, Linear, Azure DevOps, ClickUp, Asana, Trello, Notion, and ScrumDesk connections store organisation-scoped access for evidence and upcoming task handoff.
Bridge documents from drives and vaults into agent context.
Google Drive, Microsoft OneDrive, and Obsidian vault bridges let upcoming agent flows pull file context without scattering copies across chats.
Trigger workflows when strategy state changes.
Store Zapier webhook or API credentials for upcoming workflow triggers tied to approvals, surveys, and execution checkpoints.
Organisation social signals for market and positioning evidence.
Reddit and LinkedIn connections store encrypted tokens for upcoming social evidence in Category Entry Points and positioning work.
Survey and validation feedback from Microsoft Forms for Category Entry Points evidence.
Connect Microsoft Forms under Company → Connectors (Research & feedback). Load connector evidence on a CEP map to see mentioned, partial, or gap coverage from real survey responses — read-only, never writes to Forms.
Read-only HubSpot deal-pipeline stage counts for strategy and coach grounding — not Billing Stripe.
Connect HubSpot once under Company → Connectors (Evidence). Sync stores stage deal counts for the project evidence strip. Optional Ground coach injects a bounded snapshot into chat — never writes deals back to HubSpot.
Read-only Outlook Calendar meeting-rhythm evidence for grounded strategy coaching.
Connect Microsoft Outlook Calendar under Company → Connectors (Calendar), bind one calendar to a project, and sync its 28-day aggregate. Ground coach uses only bounded meeting counts, weekly cadence, and redacted subject samples — never attendee details.
Serve governed priorities to Claude Desktop, Cursor, and custom agents — with provenance, not vector guesswork.
Mint scoped project tokens. Tools like get_priorities return board-approved objectives with authority level, fidelity, and valid_until. Access logs record who queried what and when. Deprecated artefacts are excluded from serving.
Register HTTP MCP endpoints your organisation already runs — tools appear in chat with namespace controls.
Administrators and editors add servers under Company → Organisation AI. Members use the shared tool catalog in coached and agentic runs without pasting API keys into every chat.
Create an account, link your connectors, and run the Strategy Pack with real data behind every assumption.