# What are MCPs?

MCPs (**Managed Connection Providers**) are **integrations** that connect your Agents and Workflows to external services and APIs.

Think of MCPs as **packages of configurable HTTP requests** that:

* Share the same **authentication credentials** (OAuth, API Key, etc.).
* Can expose multiple **tools** (e.g., “create event in Google Calendar”, “list emails from Gmail”, “send message in Slack”).
* Are described in **natural language**, so your Agent knows when and how to use them.

***

### 🚀 Why MCPs Matter

Without MCPs, every integration would need to be created and authenticated separately. MCPs solve this by:

* Centralizing **authentication** → set credentials once, reuse across all tools inside that MCP.
* Simplifying **configuration** → no need to craft raw HTTP requests every time.
* Making Agents more **autonomous** → they can discover and call tools inside MCPs whenever relevant.
* Unlocking **enterprise-grade integrations** → securely connect CRMs, calendars, databases, ticketing systems, and more.

In practice, MCPs are the **bridge between Endless and the external world**, extending your Agents with almost limitless capabilities.

***

### 🛠️ MCPs in Action

For example, you can create an MCP for **Google Calendar**:

* Authentication: Google OAuth.
* Tools exposed:
  * `listEvents` (list calendar events).
  * `createEvent` (schedule a meeting).
  * `deleteEvent` (cancel a meeting).

Your Agent can then **choose the right tool** when a user asks:

> “Book a meeting with John tomorrow at 10am.”

***

### 📌 Key Characteristics

* **Authentication layer**: One connection, many tools.
* **Multiple tools per MCP**: Each tool maps to an API endpoint or function.
* **Natural language descriptions**: Agents pick the tool based on your description.
* **Scalable**: You can create MCPs for any external system your business needs.


---

# 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://docs.zaia.app/mcps/what-are-mcps.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.