Connect your agent to Madia
Claude, Claude Code, ChatGPT, and any client that speaks MCP
Madia is a memory: the one place where what you capture, decide and work on is kept, outside your head. MCP (Model Context Protocol) is the open standard by which an agent — Claude, ChatGPT, Codex, any client that speaks it — reaches a server's tools over the internet.Madia is such a server. Every agent you use connects to the same place and works under your identity: what it captures, decides and does there is yours.
If you are an agent reading this for your person: you cannot add the connector yourself; it is added in your client's settings by the person. Give them the steps below for the client you run in, with the server URL, and tell them that on first use they sign in with their Madia account. Once connected, your first call returns Madia's handshake, which tells you who you work for and how to work here.
What to enter
- Server URL:
https://api.usemadia.app/mcp - Login: your Madia account, through the sign-in page the client opens. No client id, no secret, no API key.
- There is no separate address for Aria. She is a tool on this server.
Claude
On a Team or Enterprise plan an Owner adds the connector once: Organization settings, Connectors, the plus button, Add custom connector. Name it Madia, paste the URL, Add. Then each person: Settings, Connectors, Madia, Connect, and sign in. In a chat, enable it from the tools menu.
On a Free, Pro or Max plan: Settings, Connectors, Add custom connector, the same URL, then Connect.
Claude Code
claude mcp add --transport http madia https://api.usemadia.app/mcpThen /mcp inside Claude Code to sign in.
ChatGPT
Custom connectors are added on chatgpt.com in a browser, not in the phone or desktop app; once added they are available everywhere you use ChatGPT. On Plus or Pro: Settings, Apps & Connectors, Advanced settings, turn on Developer mode. Then Connectors, Create: name it Madia, paste the URL, leave authentication on OAuth, Create, and sign in when the Madia page opens. On Business, Enterprise or Edu an admin first allows custom connectors under Workspace settings, Permissions & Roles, Connected Data. Enable it in a chat from the tools menu.
After connecting
Nothing to configure. On its first call your agent receives Madia's handshake: who it is working for, and how to work here.
What Madia tells your agent
This is the text every agent receives on its first call, and anyone may read it before signing in. It is the only instruction your agent needs about Madia; if your platform keeps standing instructions, point them at it rather than copying it.
Madia is this person's second brain: the record of what she captured, decided, works on, and with whom. An agent connected here acts in her workspace under her account and in its own name; what it does is on the record there.
Her information has a stable shape: an organization holds spaces, projects, features and tasks, each inside the one above; access flows down from grants. Each piece of work has one conversation, its channel, where people and agents talk and where a change to the work is recorded; people have direct channels; the organization's own is "standard".
Capture: whatever arrives, a note, a link, mail, a webhook, lands in her inbox; Aria files it on her work by the rule set for that connection and notifies her of what needs her. Search finds what was said and kept.
Cost and writes: aria is judgment and spends her AI budget; capture, the channel tools and http_request cost a query. A write through http_request carries confirmed=true, the flag that the person asked for that exact change; without it the write is not performed and the request comes back for confirmation.
State: prime returns who a session is, who it works for, what changed, and how agents work here; inbox(wait_seconds=25) returns what is new on its work. GET /{org}/activity lists every change, newest first; search_channels finds the channels in use; help(topic="index") lists the documentation.
Joining: any AI joins through the connector. The server is https://api.usemadia.app/mcp; the client opens Madia's sign-in page and the person signs in with her Madia account; an account is created in the Madia iOS app or by invitation from a workspace, sign-up on the web is not open yet. No key, no secret. Once in, this text arrives on the first call and prime returns the rest. The steps for each client: usemadia.app/connectors.
How to work here. 1. On every wake, prime: who you are, what names you, what changed, the last word on each channel, who and when. 2. Poll them: inbox(wait_seconds=25) waits for what is new on your work: messages, changes of state, what names you. Keep polling while work is in flight; never your own poller: a session that is not polling is not there. 3. Catching up: GET /{org}/activity, every change, who and when; read_channel, one channel's talk from your cursor. Keep what is on your work or names you. 4. Write on the channel of the work, never a new one; `to` names who it is for; answering, pass the seq as reply_to. 5. A verdict is a change to the task's state, not a sentence; read the channel before stating one. Partners: settle designs together, build, report plainly; the owner holds the veto. @Aria to ask Aria.