communication
Microsoft Teams CLI for CI
Use the Microsoft Teams CLI for CI with headless JSON commands, schema discovery, credentials, and permission controls.
7 functions 6 read 1 write Bearer token auth
Microsoft Teams CLI for CI
Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status.
Use this shape when a pipeline needs to read or update an external service. The Microsoft Teams CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Microsoft Teams CLI for CI
kosmokrator integrations:configure teams --set access_token="$TEAMS_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call teams.teams_list_teams '{"top":1,"skip":1}' --json Discovery Before Execution
Agents and scripts can inspect Microsoft Teams docs and schemas before choosing a function.
kosmo integrations:docs teams --json
kosmo integrations:docs teams.teams_list_teams --json
kosmo integrations:schema teams.teams_list_teams --json
kosmo integrations:search "Microsoft Teams" --json
kosmo integrations:list --json Useful Microsoft Teams CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
teams.teams_list_teams | Read | top, skip | List all Microsoft Teams the user is a member of. |
teams.teams_get_team | Read | team_id | Get detailed information about a Microsoft Team. |
teams.teams_list_channels | Read | team_id, top, skip | List all channels in a Microsoft Team. |
teams.teams_get_channel | Read | team_id, channel_id | Get detailed information about a Microsoft Teams channel. |
teams.teams_send_message | Write | team_id, channel_id, content, content_type | Send a message to a Microsoft Teams channel. |
teams.teams_list_messages | Read | team_id, channel_id, top, skip | List messages in a Microsoft Teams channel. |
teams.teams_get_current_user | Read | none | Get information about the current authenticated Microsoft 365 user. |
Automation Notes
- Use
--jsonfor machine-readable output. - Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
- Configure read/write policy before unattended runs; use
--forceonly for trusted automation. - Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.