---
title: "corestack_team_member_invite"
url: https://docs.corefinity.com/mcp/tools/corestack_team_member_invite
type: tool
last_updated: 2026-11-13
feature: team
related:
  - https://docs.corefinity.com/api/reference/organisation/invite-team-user.md
  - https://docs.corefinity.com/guides/organisation/people/users-and-invitations.md
---
# corestack_team_member_invite

**Invite a team member.** Invite somebody to your company's team with one role. They are emailed a link to set up their account. Scope: write.

- Scope: `write`
- Runs as a task: no

## When to use it

Invite somebody to your company's team with one role. They get an email with a link to set up their account; until
they accept, corestack_team_members_list shows them as `invite_sent`. When somebody cannot be invited with a link, they
are told by email instead, and the invitation stays on your team as `invite_sent` until it expires or you remove it. That
email goes to an address at most once a day from your company (and five times a day in all); the invitation is made all
the same. The answer is the same either way. Use corestack_team_roles_list for the roles you may give (`assignable: true`). This is
the Control Panel's Invite User and `POST /api/user/invite`.

## Inputs

- `name` (string, up to 255 characters, required)
- `email` (string, up to 254 characters, required): not already on your team.
- `role` (string, up to 255 characters, required): a role's slug you may give.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "email": {
      "maxLength": 254,
      "type": "string"
    },
    "name": {
      "maxLength": 255,
      "type": "string"
    },
    "role": {
      "description": "A role's slug (corestack_team_roles_list).",
      "maxLength": 255,
      "type": "string"
    }
  },
  "required": [
    "name",
    "email",
    "role"
  ],
  "type": "object"
}
```

## Refusals

- `forbidden`: you may not invite people (an owner, or the invite users permission, may).
- `owner_grant`: only an owner of the company, or Corefinity staff, may make someone an owner (agency-owner or client-owner); holding the edit users or invite users permission is not enough. Message: "Only an owner or Corefinity staff can make someone an owner."
- `permission_grant`: the role carries a permission you do not hold (a custom role always; a standard role unless you are an owner of the company or Corefinity staff). Message: "You can only give someone a role if you hold all of its permissions yourself."
- `invite_company_gone`: your company is not active yet (for example, it is still awaiting its order), so nobody can be invited to its team until it is, and nothing was sent. Message: "This company is not active, so nobody can be invited to its team until it is."
- `invalid_arguments`: on `email` (not an address, or already on your team: "Someone with this email address is already on this team."), `role` ("You are not allowed to add this role to this company.") or `name`.
- The refusals every tool can answer: `invalid_arguments`, `tenant_mismatch`, `scope_required`, `pin_refused`, `rate_limited`, `temporarily_unavailable`, `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_team_member_invite",
  "arguments": {
    "name": "Sam Smith",
    "email": "sam@example.com",
    "role": "client-member-full"
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_team_member_invite with name Sam Smith, email sam@example.com, role client-member-full. (Invite a team member.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [POST /api/user/invite](https://docs.corefinity.com/api/reference/organisation/invite-team-user.md)
- Guide: [Users and invitations](https://docs.corefinity.com/guides/organisation/people/users-and-invitations.md)
