Demandbase MCP connector
Connect Demandbase to Elaichi and your team can look up accounts, surface buying intent, pull company news and find contacts from Claude, ChatGPT, Cursor or Microsoft Copilot, with every request logged under the person who made it.
- Connects with an API key
- Free 14-day trial
- No credit card
Which accounts are showing intent for cloud security this week?
Working in Demandbase with Elaichi
-
Get single Demandbase activity type by ID
-
List all Demandbase activity types
-
Get single Demandbase bulk job by ID
How to connect Demandbase to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Demandbase MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Demandbase MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Demandbase MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Demandbase MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Demandbase MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Demandbase to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Demandbase through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Demandbase is logged.
-
Sales
Brief yourself on an account before a call
Ask for a company's Demandbase profile, its recent news and the topics it has been researching, and walk into the meeting knowing what they care about.
-
Sales Development
Find the right contacts at a hot account
Search Demandbase contacts at a company showing intent and get names and titles to reach out to this week.
-
Marketing
Spot accounts surging on your keywords
Run a Demandbase intent search for the topics your campaign covers and see which companies are showing interest right now.
-
Marketing Operations
Keep activity types tidy across campaigns
Create or rename activity types in Demandbase so engagement from a new channel is tracked the way the team expects.
-
Revenue Operations
Export an account list for the next push
Start an export job for a Demandbase account list and hand the result to the people building sequences, without leaving the chat.
-
Revenue Operations
Add a custom source and watch credit usage
Set up or update a custom source in Demandbase, map its fields, and check credit usage so the team stays within plan.
Try asking
- “Which accounts are showing intent for cloud security this week?”
- “Brief me on Acme Corp before my 2pm call”
- “Find VP-level contacts at companies surging on data governance”
What connecting Demandbase gets you
6 screens from Elaichi, each doing one job for your Demandbase account.
Ask Elaichi to work across your apps.
Which accounts are showing intent for cloud security this week?
Brief me on Acme Corp before my 2pm call
Find VP-level contacts at companies surging on data governance
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Demandbase questions in plain language.
Get answers from live companies, contacts and intent signals, no dashboard digging required.
Copy the endpoint
AI apps
One endpoint for every AI client.
Use Demandbase from Claude, ChatGPT or Cursor through one governed endpoint, no SDK, no shared key.
Tool catalog
59 Demandbase tools, no code to write.
Companies, contacts, intent, news, activity types and custom sources, covered out of the box.
Toolboxes
Every team gets its own Demandbase toolbox.
Sales sees accounts and intent, marketing ops manages sources, each scoped to the team.
Shared connections
Share a Demandbase connection, never the key.
One person connects, teammates work through it, and nobody else sees the API key.
Audit log
Know who touched which Demandbase account.
Every search, export and update is logged with who, when and which resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Demandbase digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch companies
Demandbase
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Demandbase
Queued
Workflows
A schedule runs the weekly intent digest.
Surging companies are fetched, grouped and drafted, a person approves, then it posts back to Demandbase.
Demandbase health
Refreshed 4 minutes ago · every 15 minutes · from the companies collection
Companies
1,284 ↓ 12%
Contacts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Companies created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales North America 27%
Marketing 21%
Marketing Ops 18%
Collections and dashboards
Demandbase health, computed on a schedule.
Four metrics, 14 days of records created and a team breakdown, no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Demandbase
All three can connect Demandbase to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Demandbase tools | Allow or restrict single Demandbase tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Demandbase call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Demandbase tools for your AI agents
59 tools are ready to call through Elaichi's MCP endpoint the moment you connect Demandbase, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Demandbase to Claude?
Two steps. In Elaichi, choose Demandbase and paste in your Demandbase API key; there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Demandbase is ready to use.
Does Demandbase work with ChatGPT and Cursor as well as Claude?
Yes. Once Demandbase is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Demandbase once and every client picks it up.
What can an AI agent actually do with my Demandbase data?
It can look up a company in Demandbase, search for accounts showing intent on a topic, pull recent company news, find contacts at an account, and start an export of an account list. It can also create or update activity types and custom sources, and check credit usage. Short, concrete asks such as "accounts surging on data governance this week" work better than long sentences.
Does connecting Demandbase give the AI access to everything in my account?
No. Every request runs under the Demandbase access of the person who signed in, so the agent sees the companies, contacts and sources that person could already see. Elaichi can narrow that further with roles and restrictions, and it never widens it.
Can I stop an agent from deleting or changing things in Demandbase?
Yes. Restrictions in Elaichi work per action, so you can restrict deleting a custom source or updating an activity type in Demandbase for a role or for one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Demandbase connection when someone leaves?
Offboarding that person in Elaichi ends their access to Demandbase at once. A connection they shared keeps working for everyone else on the team. If you disconnect Demandbase in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.
Does the Demandbase MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Demandbase is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Demandbase?
Yes. Both let Claude, ChatGPT or Cursor use Demandbase. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Demandbase call.
How is Elaichi different from Composio for Demandbase?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Demandbase: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Demandbase in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot