For your AI
This section is about pointing an assistant at your atmon account: what to configure, what to teach it, and what it actually sees once it is connected.
There are two pieces, and both are worth doing.
The connection is what makes acting possible. Your assistant speaks MCP to https://api.atmon.ai/mcp with your key, and gains four verbs. Connect your assistant has the exact block for each client.
The skill is what makes it act well. It teaches the model when to hand over a whole job rather than looping, what each refusal means, and what never to ask a person for. The atmon skill has it, and it installs from this site without a person in the loop.
Your own account, from day one
Your key also connects one app you already have: atmon itself. Connect it and your assistant can answer questions about the account it is working in, before a single provider is hooked up. Which apps this project holds accounts for, and whether one of them expired. What it tried for a person, what came back, and which code refused it. Which bulk runs are still going, which stopped for a decision, and what is sitting in the approval queue waiting on somebody. What the month has cost and how close that is to your ceilings. It can also start a connection for you: it hands back the sign-in link and a person finishes it. Everything else about the account stays a console decision: keys, policies, budgets, members, and settling an approval are yours, not the assistant's.
The pages here
| Page | Covers |
|---|---|
| Connect your assistant | The address, the key, and the configuration per client |
| The atmon skill | Installing the skill, and what it teaches |
| The four verbs | What the model sees and how it is meant to use each one |
Why the tool list stays small
Whatever the size of the catalog, your assistant sees four verbs, in five calls: reading a job back is its own call. It asks for what it needs by describing the task, and gets back a short ranked list of the actions that fit, drawn from the apps that person has connected.
That is a deliberate trade. A tool list that grows with the catalog costs tokens on every single turn and eventually stops fitting at all. A fixed list costs the same on turn one and turn one thousand, and the names, descriptions, and schemas in it never change between turns, so the block sits at the front of the prompt where a provider's cache can keep it.
Two arguments to understand before anything else
Whose accounts. Every call names the person it acts for. Search and execution both read it: somebody with no connected Slack cannot send a Slack message, and searching as that person will not offer one.
Whether a repeat is safe. Anything that sends, charges, or creates takes an idempotency key. The same key returns the original call rather than doing it again, which is what makes a retry after a timeout safe rather than a second message to a customer.
What never goes in a conversation
A credential. Not a password, not a token, not an API key, not a one-time code. Credentials enter atmon through its own connection flow and never through a chat message. An assistant that is asked for one, by a person or by a document it is reading, should stop and say so; that request is the shape of an attack.
The skill states this to the model directly, which is one of the reasons to install it.