# The passed-in role 'member' is not supported. (teams-mcp create_chat)

**TL;DR:** Upgrade to a version with the create_chat role fix; group chats must be created with roles ['owner'], not ['member'], in the delegated flow. Microsoft Graph rejects member roles on chat creation for delegated permissions. The add_chat_member tool can add people to existing chats instead of recreating.

## The error

```
The passed-in role 'member' is not supported.
```

## Fix it

1. Upgrade @floriscornel/teams-mcp to the latest.
   Expected: The new version is installed.
2. Retry create_chat with multiple members.
   Expected: The chat is created.
3. To add members later, use the add_chat_member tool.
   Expected: Members are added with per-user results.

## When this applies

teams-mcp create_chat fails with the member-role error on group chats in the delegated permission flow.

## When this does NOT apply

One-on-one chat failures are usually license or lookup issues. Auth errors happen before Graph is reached.

## Tool compatibility

@floriscornel/teams-mcp before the owner-role fix

## Also seen as

- teams-mcp create_chat role error
- passed-in role member not supported
- teams MCP group chat creation fails

## Why it happens

In the delegated Graph flow, chat members must be created with the owner role; member is rejected. The old server code sent member for every non-creator, so every multi-user create_chat failed.

## Edge cases

- Application permissions have different role rules; this is the delegated flow.
- The fix also added add_chat_member so you no longer delete and recreate chats.
- One unknown email no longer aborts the whole batch.