# What is MadKudu MCP

<figure><img src="/files/SXSXoFi94UX1NwKJTh3X" alt=""><figcaption></figcaption></figure>

MadKudu MCP (Model Context Protocol) is how you plug MadKudu intelligence into your own tools - whether it’s an AI agent, a prospecting assistant, a custom dashboard, or a RevOps automation, when they support MCP so you don't have to go through API connections

## Why using MadKudu MCP

**For RevOps / Developers**

MadKudu MCP bridges the gap between your data and your AI agents. If you are building internal agents, Sales Copilot or other assistants, use MadKudu MCP to give them the context of your prospects data, without messing around with APIs and ETLs.

**For** **Sellers and non-technical folks**

MadKudu MCP allows you to access all your prospects information directly from your favorite AI tools (Claude, chatGPT, etc.) in just a prompt. When connected, your AI tool can research in your own customer data and signals MadKudu has aggregated.  Just like that, with just a prompt! &#x20;

## What can you do with MadKudu MCP

With MadKudu MCP connected, your AI agents can:

* Research an account or person getting a full profile and brief&#x20;
* Source new people to engage with
* Personalize outreach based on all signals found for these contacts
* Trigger actions like adding a person to a sequence or drafting an email

MadKudu MCP currently works with Claude, Cursor, Windsurf, and any MCP client that supports Streaming HTTP or STDIO transport


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developers.madkudu.com/madkudu-mcp/what-is-madkudu-mcp.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.