You can connect an AI assistant, such as Claude, to your Nimbata account. The assistant can then look up your calls, reports and setup, and, if you allow it, make changes for you, such as creating a tag or blocking a spam caller. It connects with your own Nimbata login, so it can only see and do what you can in Nimbata.

This page covers the Nimbata side, which is the same for every assistant: the access you give, the role permission it needs, and how to review or end a connection. To connect a specific assistant, see its page: Claude.

Before you start

Plan
Every Nimbata plan
Permissions
MCP Access, in your role's Account permissions

What each access level allows

You choose the access level when you authorize an assistant. The app names each level in three places, so this table shows all three.

View View and manage
What the assistant can do Look up your data: calls and call reports, text messages, tracking numbers, destinations, call flows, workflows, tags, fields, sources and blocked callers. Everything View allows, plus changes: create and edit projects, call flows, workflows, tags, fields and sources, add destinations, and block callers.
On the authorization page View (“View your data”) View and manage (“View and make changes to your data.”)
In Connected apps Read-only View and manage
Role permission it needs MCP Access with Read (or Full access) MCP Access with Full access

No assistant can delete anything (removing a blocked caller included), buy or release numbers, change your plan or billing, manage users and roles, or send text messages. Those stay in the Nimbata app.

If your role allows only Read, the authorization page offers no choice: it shows that the assistant will be able to view your data.

Give a role access to AI assistants

People can connect an assistant only when their role includes MCP Access. To change a role, you need the Roles permission.

Note

A new Nimbata account’s Admin role already includes MCP Access with Read and Full access. Roles you create don’t include it until you add it.

  1. Open the role

    Go to AccountRoles and click the role you want to change.

  2. Open MCP Access

    In the list of categories, click Account, then open MCP Access (its description reads “Control read-only or full access through MCP clients”).

  3. Choose the level

    Check Read to let people connect with View only, or Full access to also let them choose View and manage. Changes save automatically.

    MCP Access
    Control read-only or full access through MCP clients
    ✓Read
    ✓Full access
    MCP Access in a role's Account permissions: Read allows View, and Full access also allows View and manage.

Warning

Removing a level from a role stops the connections that use it. For example, if you remove Full access, connections approved with View and manage stop working until each person connects again, this time with View.

Detailed guide: Organization roles

Review or disconnect your connected apps

Each person reviews and disconnects their own connections, on their own profile.

  1. 1Open Connected apps

    Go to AccountMy Profile. Under Connected apps, click Manage.

    User Profile

    Connected apps
    Manage apps connected to your account.
    Connected apps sits on your profile, under the security settings. Click Manage (1).

  2. Review your connections

    Each connection shows its access (Read-only or View and manage), when you Approved it, when it Expires and, once it has been used, when it was Last used.

  3. 1Click Disconnect

    Next to the app, click Disconnect, then click Disconnect again to confirm. The app loses access to your account right away.

    Each connection shows its access and dates. Click Disconnect (1), then confirm.

To use the assistant again, connect again from the assistant. Disconnecting is also how you change a connection’s access level: disconnect it, then connect again and choose the other level.

How long a connection lasts

A connection lasts one year from when you approve it: that’s its Expires date in Connected apps. It ends sooner when:

  • the assistant doesn’t use it for 90 days,
  • you disconnect it,
  • your role loses the access it was approved with (see the warning above), or
  • your organization can no longer use AI assistants, for example because its subscription has ended.

When a connection ends, the assistant tells you the Nimbata connection has expired or was revoked. Connect again from the assistant.

Troubleshooting

“Permission required” when you connect

“Connection unavailable” when you connect

  • Your organization can’t connect AI assistants right now, for example because its subscription has ended. Contact your Nimbata administrator. An admin can choose a plan in AccountPlans & Billing.

The assistant says the connection is read-only

  • You approved View, which can’t make changes. Disconnect the app in Connected apps, then connect again from the assistant and choose View and manage.
  • If the authorization page doesn’t offer View and manage, your role has only Read. Ask an admin to add Full access.

The assistant says you don’t have permission to make changes

  • Your role doesn’t allow that change. Ask your administrator for access. The assistant can do only what you can do in the app.

The assistant says Nimbata is limiting requests

  • Nimbata limits how many requests each person can make, and your personal API tokens count toward the same limit. Wait for the time the assistant gives, then try again.

Frequently asked questions

Does everyone on my team need to connect?

Yes. Each person connects with their own Nimbata login, and the assistant then has that person’s access. One person’s connection never gives anyone else access.

Can I switch between View and View and manage later?

Yes. Disconnect the assistant in Connected apps, then connect again from the assistant and choose the other level.