Claude Desktop Extension
oHallo publishes an extension for Claude Desktop. Install it, and you can work with your oHallo account by asking Claude in plain language: search the knowledge base, draft and approve policies, read and reply to conversations, look up contacts and accounts, and review your agents. It suits the moments when you are already writing in Claude and want an answer from your own operation without switching to the dashboard.
The extension reaches your account through an API key that you create in the dashboard. The permissions on that key decide what it can do.
The MCP hub connects oHallo to your business systems. This extension goes the other way: it connects Claude Desktop to your oHallo account.
What you can do with it
Section titled “What you can do with it”| Area | What you can ask for |
|---|---|
| Brands | List and read your brands, create a brand, and update its name, sender, appearance, languages, and the assistant’s instructions |
| Knowledge base | Search articles, read them, create new ones, and approve them |
| Policies | Search policies, create them, and approve them |
| Conversations | Read conversations and the items waiting for a person, reply, compose a new message, and mark an attention item resolved |
| Contacts and accounts | Search contacts and accounts, read them, and keep their details current |
| Agents | Read your agent definitions and update an agent’s instructions |
Ask the way you would ask a colleague, for example “find the knowledge base article about return shipping” or “show me the conversations waiting for a person today”.
Work done through the extension lands in your account straight away and appears in the dashboard like any other change. It is recorded against the API key you used, so it stays distinguishable from work done by a person signed in to the dashboard.
Before you start
Section titled “Before you start”You need two things:
- Claude Desktop, installed on your computer.
- An oHallo API key. Users with the Owner or Admin role create keys under Settings, then API access. See API Access for the steps. The full key is shown once at creation, so copy it before you leave the page.
Setting it up
Section titled “Setting it up”Setup is three steps and takes about a minute once you have the key.
- Go to ohallo.ai/extensions and select Download Claude extension. You receive a single file named
ohallo-production.mcpb. - Open the downloaded file. Claude Desktop recognises it and offers to install it.
- Paste your oHallo API key when Claude Desktop asks for it. The key begins with
sf_live_v1_.
Claude Desktop stores the key with the extension, so you enter it once. The extension then connects to your account, and your oHallo capabilities become available in your conversations with Claude.
What the extension is allowed to do
Section titled “What the extension is allowed to do”The scopes on the key decide what the extension can reach. This is the same permission model the oHallo API uses, so a key that reads conversations over the API reads conversations here too. The extension does exactly what the key allows, and asking for anything beyond it returns a clear permission message that tells you which scope is missing.
| Grant the key | And you can ask Claude to |
|---|---|
| Brands read | List and read brands |
| Brands write | Create brands and update them |
| Knowledge base read | Search and read articles |
| Knowledge base write | Create, update, and approve articles |
| Policy read | Search and read policies |
| Policy write | Create, update, and approve policies |
| Conversations read | Read conversations and attention items |
| Conversations write | Reply, compose an outbound message, and resolve attention items |
| Contacts read and write | Search contacts, and create or update them |
| Accounts read and write | Search accounts, and create or update them |
| Agents read and write | Read agent definitions, and update an agent’s instructions |
Grant each key the scopes its work needs and leave the rest out. If you later want the extension to do more, create a key with the wider scopes and enter that key in the extension.
Good practice
Section titled “Good practice”- Give the extension its own key, named for it, for example “Claude Desktop”. You can then see its activity in the Last used column and revoke it on its own.
- Keep the key in a password manager and pass it along a secure channel if a colleague needs one.
- Give each person their own key. Work is recorded against the key, so a key per person keeps the audit trail readable.
- Replace a key when someone leaves the team or moves to a new computer: create the replacement, install it, then revoke the old one.