Use a personal API key when you want a local agent, such as Codex or Claude
Code, to help configure Ando as you. This is best for personal setup work:
organizing your sidebar, tuning notifications, checking delivery readiness, and
reviewing your own workspace setup.
If you are truly next-level lazy, send this page to your agent and ask it to
walk you through the setup. It should still read first, explain what it can
change, and wait for your approval before writing anything.
A personal API key acts as you and inherits your workspace access. Create a
separate key for each local client, keep it private, and revoke it when you no
longer use that client.
Create a personal API key
- Open Studio → API & Webhooks → API keys.
- Create a Personal key for your local client.
- Expand Customize permissions before saving.
- Keep the ordinary read permissions the client needs.
- Enable Profile write if you want the client to update notification
settings for you.
Personal keys are described in Developers → Overview.
The MCP setup page also has client-specific setup for
Codex CLI and Claude Code.
Connect your local agent
Add Ando MCP to the local client with this server URL:
Pass your personal API key as the bearer token. After connecting, ask the local
agent to identify what tools are available before making changes. The available
tool list is the source of truth for what that client can read or update.
Try a prompt like this:
This is also a good time to tune the local agent’s own review settings. Ask it
to explain when it can make changes automatically, when it will ask before
editing or running commands, and how its auto-review or approval settings affect
your Ando setup work.
Your sidebar should match how you work, not the order channels happened to be
created. Ask the local agent to help you decide what should be pinned, grouped,
muted, or left in the regular conversation list.
Try a prompt like this:
If your local agent has tools for sidebar changes, have it apply only the
approved changes. If it does not, use its plan as a checklist while you update
the sidebar in Ando.
Tune notifications
Local MCP clients can read and update your own notification settings with a
personal API key. Enable Profile write on the key if you want the client to
save changes.
Ask the client to call get_notification_settings before writing. It can use
get_notification_delivery_readiness to find setup blockers and
explain_notification_behavior to explain whether a specific kind of message
would notify you.
Try a prompt like this:
For more detail, see Notifications.
Use miniapps with your agent
Miniapps are small native Ando surfaces an agent can post when a normal message
would be clumsy. They are useful for choices, approvals, lightweight trackers,
and repeatable workflows that should stay in the conversation.
Ask your local agent to use a miniapp when you want to review or change
structured information without switching tools. For example, it can ask an
explicit question, propose a poll, update a CRM-style list, or keep a small
shared record current.
Try a prompt like this:
Miniapps still follow Ando permissions. Posting one does not grant your agent
new workspace access, connect an account, or approve a provider action for you.
When a miniapp needs connected-app access, Ando asks a person to choose the
account and consent to the requested operations.
For the agent-facing details, see Miniapps. 
