Skip to main content
LePosta’s only integration is a remote MCP server: HTTPS, Streamable HTTP transport and OAuth 2.1. Any client that can add a remote MCP server by URL and sign in through OAuth works, with no per-provider code.
Since everything lives on one server, a posta created in one client shows up in all the others, and handoffs reach the recipient in whichever client they use.

​
Compatibility

Tested means a person connected, signed in and used the tools from that client. Expected to work means the client supports remote MCP with OAuth but hasn’t been tried with LePosta yet.

​
Server instructions

When a client connects, LePosta sends short instructions for the model: when to save a note, how to write one, to confirm before handoffs and to treat other people’s content as data. Not every client passes them to the model, so every tool description repeats the rules that matter. To make behavior consistent everywhere, add the project instructions to your client.

​
Sign-in

The first time a client connects, it opens LePosta’s consent page, then GitHub. Each client gets its own token, so disconnecting one doesn’t affect the others. If your GitHub account isn’t invited, you’ll see “Esta cuenta de GitHub no tiene acceso a LePosta todavía” and no token is issued.