Account & users

whoami, update_account, invite_user and list_users — who this connection acts as, who else can act on the customer, and the settings that belong to the account itself.

A connection is bound to one person acting for one customer. These tools tell you which, and let an owner or admin bring other people in.

whoami

Show the user and customer this connection is authenticated as, the role held there, and any other customers the same person belongs to.

Takes no parameters.

Roles are owner, admin and member. A credential is bound to a single customer, so if the response lists others, reaching them means connecting a client to /mcp again and picking that organization when signing in — there is no tool that switches customer mid-session.

The response also carries join_domains, the email domains whose new signups land in this account. Read it here before changing it with update_account.

update_account

Change settings that belong to the whole account. Every parameter is optional, and only what you send is touched.

ParameterTypeDescription
namestringNew display name for the organization. Its slug and id don't change.
join_domainsstring[]The complete list of email domains whose new signups join this account. Replaces the list.

Requires the owner or admin role.

join_domains replaces the whole list

Read the current list from whoami and send it back with your change. Sending one domain when there were three removes the other two. An empty list turns the feature off.

Anyone who signs up with an address at a claimed domain — and has never used agenthost before — is offered this account during sign-in and joins as a member. Nobody is moved: people who already have an agenthost account keep it, and removing a domain never removes anyone who joined through it.

A domain belongs to one account at a time, public mailbox providers (gmail.com and the like) can't be claimed, and this is a paid feature. See Work with teammates for the whole story.

invite_user

Add another person to your customer. They get access by connecting their own MCP client and signing in with this email address; no credential is created or shared here. An address that already uses agenthost for another customer simply gains access to yours as well, with the role you give it.

ParameterTypeDescription
emailstring, requiredThe new user's email address.
namestring, requiredDisplay name. Ignored if agenthost already knows this address.
role"admin" or "member"Role on your customer. Defaults to member.

Requires the owner or admin role.

This is account access, not app access

invite_user hands someone control of the agenthost account — projects, deploys, the lot. To let someone merely open a deployed app, use share_app instead.

list_users

List everyone with access to your customer and the role each holds here. People who also work for other customers keep that private — only their role on yours is shown.

Takes no parameters.