Before you connect
What must be switched on in your organization before an assistant can connect, and what a connection acts as.
Two things to settle before you add Nuvelics to an assistant: that MCP is on for your organization, and what a connection will be allowed to do.
MCP must be on for the organization
MCP is off by default. While it is off, every MCP call is refused, whatever credential it carries, and your organization does not appear as a choice when you approve a connection.
An owner or an admin turns it on. The permission behind the switch is mcp:manage, which owners and admins
hold; an admin can run MCP without being able to do owner-only things such as renaming the organization. If
you are a member or a viewer, ask one of them. The steps are in MCP, where an owner
or admin can also copy the address your assistant connects to.
You need an account in the organization
A connection acts as you, so you need a Nuvelics account that belongs to the organization. If you do not have one yet, accept an invitation first: see Accept an invitation.
What a connection acts as
When you approve a connection, the assistant acts as you, in the one organization you picked, and nobody else. Two limits apply at once:
- It is capped to the permissions the MCP tools use, never your full account access, and never anything to do with running the platform itself.
- It is capped to your own role. If you cannot do something in the web app, your assistant cannot do it either.
What a connection can do has the detail. Next, connect a client.