Team tools

The team feature includes read and write tools for site-level membership. Write access can invite or remove guest and developer members. Removing a member removes access to the site; it does not delete the person's Faurya account.

Supported access levels

Role requirements and site scoping

Team service checks require authenticated user context and site access. Team changes are owner-sensitive and can return team_permission_required, owner_access_required, ROLE_NOT_ALLOWED, cannot_invite_owner, or cannot_remove_owner depending on the operation and current role. Supply siteId for multi-site connections.

Supported invite roles are guest and developer.

Tool summary

Common errors

team_permission_required, owner_access_required, site_not_permitted, invalid_email, invalid_role, cannot_invite_self, cannot_invite_owner, already_member, member_not_found, cannot_remove_owner, notification_failed, INSUFFICIENT_SCOPE, and VALIDATION_ERROR.

faurya_list_team_members

What it does

Lists the owner and all guest or developer members who currently have access to a permitted Faurya site.

Permission required

Team: Read.

When to use it

Use before inviting or removing members, or to audit site access.

Example prompt

List team members for this Faurya site.

Input

Example MCP input

{ "siteId": "site_example" }

Output

data contains owner and member entries with safe role information.

Example output

{
  "success": true,
  "requestId": "req_example",
  "data": {
    "members": [
      { "email": "user@example.com", "role": "owner" },
      { "email": "developer@example.com", "role": "developer" }
    ]
  },
  "meta": {
    "warnings": [],
    "pagination": { "nextCursor": null, "hasMore": false }
  }
}

Common errors

team_permission_required, site_not_permitted, INSUFFICIENT_SCOPE.

Notes

This is read-only.

faurya_invite_team_member

What it does

Invites a person to a permitted Faurya site as a guest or developer. The invited person and site owner are notified by email.

Permission required

Team: Write. Owner-sensitive access applies.

When to use it

Use when the user clearly wants to add a guest or developer to a site.

Example prompt

Invite user@example.com as a developer to this site.

Input

Example MCP input

{ "siteId": "site_example", "email": "user@example.com", "role": "developer" }

Output

data confirms invitation or membership status.

Example output

{
  "success": true,
  "requestId": "req_example",
  "data": { "email": "user@example.com", "role": "developer", "invited": true },
  "meta": {
    "warnings": [],
    "pagination": { "nextCursor": null, "hasMore": false }
  }
}

Common errors

invalid_email, invalid_role, cannot_invite_self, cannot_invite_owner, already_member, owner_access_required, notification_failed.

Notes

This changes site access. Confirm email and role before calling.

faurya_remove_team_member

What it does

Removes an existing guest or developer member from a permitted Faurya site without deleting their Faurya account.

Permission required

Team: Write. Owner-sensitive access applies.

When to use it

Use when the user clearly wants to revoke a member's access to a site.

Example prompt

Remove user@example.com from this site.

Input

Example MCP input

{ "siteId": "site_example", "email": "user@example.com" }

Output

data confirms removal from site access.

Example output

{
  "success": true,
  "requestId": "req_example",
  "data": { "email": "user@example.com", "removed": true },
  "meta": {
    "warnings": [],
    "pagination": { "nextCursor": null, "hasMore": false }
  }
}

Common errors

member_not_found, cannot_remove_owner, owner_access_required, invalid_email.

Notes

Destructive to site access. Confirm with the user before calling.

Related pages

• Overview
• Installation
• Site Settings