Ask Your AI About Your Own Stack
General AI assistants can tell you what a CDP is. They cannot tell you what your CDP costs, when it renews, or what it is connected to. Connect one to Stack Builder and it can.
Read-only. Included with Consultant, Team and Enterprise plans.
Four steps, once
No API keys to rotate, no tokens to paste into a config file. You sign in and approve, the same as any other connector.
- 1
Copy your server URL
In Stack Builder, open Settings → Connections. Your MCP server URL is there, along with the switch for agreement access.
- 2
Add it as a connector
In Claude Desktop: Settings → Connectors → Add custom connector, and paste the URL. ChatGPT, Codex and any other MCP client use the same one.
- 3
Sign in and approve
You sign in with your Stack Builder account and approve access on a consent screen. Nothing is shared until you do.
- 4
Ask about your stack
"List my workspaces" is the place to start — every other tool takes an id from there.
What you can ask
You do not name tools. You ask a question and the assistant picks them.
“Which vendors in my CDP Rollout stack talk to each other, and how?”
ConsultantReturns the vendors with their categories and roles, plus every data-flow connection between them.
“What does that stack cost per month, and what renews in the next 90 days?”
ConsultantPer-vendor monthly and annual cost, the total, and the renewal dates behind it.
“Summarise the vendors I have under evaluation and what each RFI is asking for.”
ConsultantYour RFI evaluations with their vendors, use case, brief, timeline, budget and status.
“What change proposals are open on this team, and which are blocked?”
TeamProposals with status, change type, priority, due date and affected nodes.
“Which contracts have a notice period shorter than 60 days?”
EnterpriseAgreement metadata — commercial terms, SLA, dates, renewals. Never the document text.
“Find customer data platforms that mention identity resolution.”
Any planSearches vendor names and descriptions in the catalog for a keyword. No stack required.
Every tool on the server
Twelve, all read-only. Nothing is hidden behind a vague “and more”.
| Tool | What it returns | Plan |
|---|---|---|
list_workspaces | Your personal and team workspaces, each with its plan and what it unlocks. | Any plan |
search_vendors | Catalog search: a keyword matched against vendor names and descriptions. | Any plan |
get_vendor | One vendor: category, description, website, headquarters, parent company. | Any plan |
list_stacks | Stacks in a workspace with vendor and connection counts. | Consultant |
get_stack | One stack in full: vendors, roles, data-flow connections, summary stats. | Consultant |
get_stack_costs | Per-vendor and total cost, plus upcoming renewals. | Consultant |
list_rfis | Your RFI evaluations: vendors, use case, timeline, budget, status. | Consultant |
get_rfi | One RFI in full: company, vendors, use case, brief, timeline, budget, status. | Consultant |
list_proposals | Change proposals: title, status, type, priority, due date. | Team |
get_proposal | One proposal in full: description, affected nodes, resolution, implementation status. | Team |
list_agreements | Agreement metadata: vendor, type, status, value, dates, renewal. | Enterprise |
get_agreement | One agreement: commercial terms, SLA, security posture, data protection, legal clauses. | Enterprise |
What it deliberately cannot do
Connecting an AI assistant to procurement data is a decision your security team will have an opinion about. Here is the shape of the answer.
Read-only, with no exceptions
Every tool is annotated read-only and there is no write path. An assistant cannot create, edit, delete or share anything in your account — the worst a bad prompt can do is ask a question.
Your permissions, not new ones
Row-level security applies to every request. The connection sees exactly what your own account sees and nothing beyond it — joining a workspace or leaving one changes what the assistant can read, immediately.
The documents stay here
Agreement tools return structured fields: values, dates, notice periods, and the clause text our extraction pulled out (liability, termination, governing law and similar). The uploaded file and its full text are never sent to an AI client.
Agreements are off until you say so
Even on Enterprise, agreement access starts disabled. You turn it on per account in Settings → Connections, and you can turn it off again without touching the connector.
One workspace per call
Tools take a workspace id and answer for that workspace alone. Nothing bleeds between your personal work and a client team.
More detail on how the platform handles your data is on the security page.
Frequently Asked Questions
What is MCP?
Which AI clients work with it?
Which plan do I need?
Can the assistant change my diagrams?
Does it send my vendor contracts to the AI?
Where do I find the server URL?
How do I disconnect?
Your stack, in the assistant you already use
Connect it once and ask what your architecture costs, what renews next, and how your tools connect, without exporting anything.
No credit card required. Free plan available.