Tempio

Agent integrations

There is one programmatic surface and every client uses it. A Model Context Protocol server over streamable HTTP, reached with a key you mint in the app or with a token a client earns by signing in, either way scoped to one workspace and to the things you chose when you granted it. The in-app agent and your own client call the same org-scoped tool layer, so a tool behaves identically whichever one is holding it.

What differs per client is the setup: where the config lives, what the command is, and how the client reports a connection it could not make. That is what each page here covers, along with the prompts worth running first and what a change looks like while it is still a change request. A client whose handshake has not been evidenced has a page that is reachable by URL and indexed nowhere, because a compatibility claim is a claim like any other.

Clients and pairings

Questions

Put frontier AI to work on every ad account you run.

Tempio connects your ad accounts into one workspace and hands your own AI the numbers and the tools. Every change it writes is a draft until you approve it, or until a rule you wrote does.

Request early access
  • Read and draft by default. Approve is a separate permission you grant.