Step 1
Query
You, in Claude or Codex:
“Analyse Acme's last week through DemandIntel. What's the one training need I can fix to move the team's performance?”
Natural language → the ask() tool + QA data.
DemandIntel in Claude, Codex & your tools
Connect DemandIntel to Claude, Codex, Cursor or any MCP client with a single command, the installer drops in our training Skill and wires up the MCP server in one hit. Ask it what to coach, and let it build the training.
No account yet? Request beta access, once approved you can generate your token and connect in under a minute.
The loop
DemandIntel is not a one-off report generator. Wired into your AI tool it becomes a loop where every engagement makes the next one sharper - because the review that closes one cycle is the evidence that opens the next.
Query
Ask DemandIntel, in plain language, what's really happening on the calls - no dashboards to hunt through.
Plan
It answers from real QA and competency data, and points to the one highest-leverage gap to fix.
Create
Your AI tool turns that gap into ready-to-run training: session plan, notes, handouts, scripts, scenarios.
Deliver
You run the session - grounded in the team's own conversations, not a generic curriculum.
Review
Weeks later, ask again: did the score move? The answer is the evidence - and the next question.
A worked example
Here is the loop running end to end on a real demo account, exactly as it plays out in Claude. No exports, no slide deck to assemble by hand - the tool does the listening and the prep; you stay the expert in the room.
“Use DemandIntel to analyse Acme Co’s training requirements for the last week. What is the most important training need where I can impact the team’s performance? Then create the sales-training assets I need to deliver the training.”
You, in Claude - to the DemandIntel MCP
Step 1
Query
You, in Claude or Codex:
“Analyse Acme's last week through DemandIntel. What's the one training need I can fix to move the team's performance?”
Natural language → the ask() tool + QA data.
Step 2
Plan
DemandIntel answers with evidence:
Reps book meetings without confirming budget.
QA data confirms it's the whole team, not one rep. Fix first: qualification.
Step 3
Create materials
Claude builds the training kit:
Built from the team's real calls, via a Skill.
Step 4
Deliver
You run the session:
Deliver the training to the team, grounded in their own conversations, not a generic template.
The trainer stays the expert; the tool preps.
Step 5
Review
Two weeks on, ask again:
“Did qualification scores move?”
Pull the QA trend and see the change, evidence of impact.
The result becomes the next question. ↺
Every answer sharpens the next question — a virtuous circle
The same query, re-run two weeks later, becomes the proof the training worked — and the start of the next cycle.
Create
Session plan, trainer notes, handouts, practice scripts and scenarios, all built from your team's real calls. You stay the expert in the room; the tool does the prep.
Get connected
No config files to hand-edit, no OAuth dance. Mint a token, paste one line into your terminal, and the installer drops the DemandIntel training Skill into your assistant and registers the MCP server (~31 tools) in a single hit.
Step 1
In Settings → API & MCP Access, click Create token. Choose read scope, optionally cap monthly usage or lock it to specific clients. Copy the di_pat_ secret, shown once.
Step 2
Paste the installer command below into your terminal with your token. It installs the DemandIntel Skill into ~/.claude/skills/ and registers the MCP server automatically.
Step 3
Restart your assistant. DemandIntel and its Skill are now available, ask a question in plain language and your tool picks the right DemandIntel tool automatically.
Run this in your terminal
curl -fsSL https://raw.githubusercontent.com/demandintel/demandintel-skills-resource/main/install.sh | DEMANDINTEL_API_KEY=di_pat_… bashReplace di_pat_… with the token from Step 1. The installer needs curl and bash, standard on macOS and Linux. Then restart your assistant and run /mcp in Claude Code to confirm demandintel is live.
{
"mcpServers": {
"demandintel": {
"url": "https://mcp.app.demandintel.io/v1?token=di_pat_…"
}
}
}[mcp_servers.demandintel]
command = "npx"
args = ["-y", "mcp-remote", "https://mcp.app.demandintel.io/v1", "--header", "Authorization: Bearer di_pat_…"]Prefer to install the Skill manually? Download the pack and drop it into your assistant's skills folder.
What you can reach
Curated tools return instantly. ask handles the genuinely novel questions in natural language, routing to the right data behind the scenes.
Free-form Q&A
Spot-check & coaching
Competency & QA
Reports, calls & entities
All tools are read-scope today; mutations - for example generating reports - require a write-scoped token.
Safe by design
Access is a scoped Personal Access Token; only a hash is stored, the secret is shown once and can be revoked instantly.
Read-only by default; an optional client filter limits a token to specific clients - ideal for a contractor or partner.
Each request is logged with status, duration and usage, so you can see what a token has done and cap its spend.
Set an optional monthly usage cap on any token as a spend control - the platform stops the token once the cap is reached.
The listening, the analysis, and the prep, inside the tool you already use. You bring the judgement and the room.
Need an account? Request beta access to connect the DemandIntel MCP server.