Can I use Microsoft Teams as a CLI?

Yes. KosmoKrator exposes a Microsoft Teams CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Microsoft Teams through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Microsoft Teams tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Microsoft Teams credentials stored?

Microsoft Teams credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Microsoft Teams MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

other

Microsoft Teams CLI for Shell Scripts

Use the Microsoft Teams CLI for shell scripts with headless JSON commands, schema discovery, credentials, and permission controls.

8 functions 7 read 1 write Manual OAuth token auth

Submit Microsoft Teams feedback View package source

Microsoft Teams CLI for Shell Scripts

Call integration functions from shell scripts with stable JSON input and output.

Use shell scripts for small local automations that need one or more integration calls. 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 Shell Scripts
kosmokrator integrations:configure microsoft-teams --set access_token="$MICROSOFT_TEAMS_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call microsoft-teams.microsoft_teams_list_teams '{}' --json

Discovery Before Execution

Agents and scripts can inspect Microsoft Teams docs and schemas before choosing a function.

kosmo integrations:docs microsoft-teams --json
kosmo integrations:docs microsoft-teams.microsoft_teams_list_teams --json
kosmo integrations:schema microsoft-teams.microsoft_teams_list_teams --json
kosmo integrations:search "Microsoft Teams" --json
kosmo integrations:list --json

Useful Microsoft Teams CLI Functions

Function	Type	Parameters	Description
`microsoft-teams.microsoft_teams_list_teams`	Read	none	List all Microsoft Teams teams the authenticated user has joined. Returns team IDs, names, and descriptions.
`microsoft-teams.microsoft_teams_get_team`	Read	team_id	Get details for a specific Microsoft Teams team by its ID. Returns the team name, description, and other properties.
`microsoft-teams.microsoft_teams_list_channels`	Read	team_id	List all channels in a Microsoft Teams team. Returns channel IDs, names, and descriptions.
`microsoft-teams.microsoft_teams_get_channel`	Read	team_id, channel_id	Get details for a specific Microsoft Teams channel by its team and channel ID.
`microsoft-teams.microsoft_teams_list_messages`	Read	team_id, channel_id, limit	List recent messages in a Microsoft Teams channel. Returns message content, sender info, and timestamps.
`microsoft-teams.microsoft_teams_send_message`	Write	team_id, channel_id, content, content_type	Send a message to a Microsoft Teams channel. Supports plain text and HTML content.
`microsoft-teams.microsoft_teams_list_chats`	Read	limit	List chats for the authenticated Microsoft Teams user. Returns chat IDs, topics, and types (one-to-one, group, or meeting).
`microsoft-teams.microsoft_teams_get_current_user`	Read	none	Get the profile of the currently authenticated Microsoft Teams user. Returns display name, email, and job title.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Microsoft Teams CLI Pages

CI Microsoft Teams CLI for CI. Cron Jobs Microsoft Teams CLI for cron jobs. Headless Automation Microsoft Teams CLI for headless automation. Coding Agents Microsoft Teams CLI for coding agents.