> For the complete documentation index, see [llms.txt](https://docs.clearout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clearout.io/platform-features/ai-and-third-party-app-access.md).

# AI & Third-Party App Access

Clearout supports secure connections for AI agents, MCP-compatible clients, and third-party applications.

### MCP for AI agents

Connect AI assistants and agent workflows to Clearout through the Model Context Protocol (MCP). MCP clients can discover and invoke approved Clearout tools, such as email verification and email finding.

Explore the [MCP Server](https://docs.clearout.io/developers/mcp.md)

### OAuth 2.1 for third-party apps

Let third-party applications access Clearout services on behalf of a Clearout user without sharing the user’s API key. Users approve the access, and applications receive scoped, short-lived access tokens.

Explore[ OAuth 2.1](#oauth-2.1-for-third-party-apps)

### Why it matters

* Connect AI agents to Clearout without building a custom integration layer.
* Give third-party apps limited, consent-based access to Clearout services.
* Avoid sharing long-lived API keys with external applications.
* Control access using OAuth scopes and revoke connections when needed.


---

# 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://docs.clearout.io/platform-features/ai-and-third-party-app-access.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.
