ThatApp.io
Developers · Public Tool API & MCP

ThatApp inside the AI client of your choice.

Mint a token, paste it into Claude, ChatGPT desktop, or any Model Context Protocol client, and that client can reach ThatApp's tools and your connectors directly.

Talk to us → See AVA's tools →
# add ThatApp as a custom connector
endpoint mcp.thatapp.io
transport streamable-http
token tap_•••••••••••
→ tools available
flows · data lake · saved views · usage
What you get

Your tools, your tokens, your control.

A library of tools at one endpoint

Platform tools at one surface and a meta-dispatch interface to your iPaaS connector library at another. Your AI client can query, build, and report.

Mint, list, and revoke tokens

Issue tokens from your dashboard and revoke them when you are done. A leaked token is recoverable, honored within about sixty seconds.

Scoped per surface

Each token is scoped to a specific surface, so a token for one cannot be reused for the other. Destructive cross-tenant tools are intentionally disabled.

Two transports

Stdio for local clients like Claude Desktop, and streamable HTTP for remote web clients. Use whichever your client supports.

Three steps to a connected client.

1

Mint a token

Issue a scoped token from your ThatApp dashboard in a couple of clicks.

2

Add the connector

Paste the endpoint and token into Claude, ChatGPT desktop, or any MCP client.

3

Ask away

Your assistant can now query your data lake, manage flows, and read usage.

Built for partners and power users, today

The public tool surface is aimed at consulting partners and developers building on top of ThatApp. Per-user scoped tokens and metered rate limits are on the roadmap. If you are building something ambitious, talk to us and we will set you up properly.