> For the complete documentation index, see [llms.txt](https://developers.madkudu.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.madkudu.com/madkudu-mcp/first-time-using-mcp.md).

# First time using MCP

You don’t need to write code. 

Once you've [connected MadKudu in a couple clicks](/madkudu-mcp/install-in-ai-platforms-in-2min.md), in your tool just try asking:

> Tell me who Francis at MadKudu is

## Use case examples

* Prep for a sales meeting 
* Prospect into a new account
* Source new contacts to go after
* Personalize outreach

## Prompts examples

> "Get me an account brief for Acme"

> Who are the top users at Acme and what have they been doing?

> "Find contacts at Acme in Marketing with Director or VP titles"

> "Draft a personalized email to John at Acme using MadKudu details"


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.madkudu.com/madkudu-mcp/first-time-using-mcp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.