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.

communication

Microsoft Teams MCP Integration for Codex

Connect Microsoft Teams to Codex through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write Bearer token auth

Submit Microsoft Teams feedback View package source

Connect Microsoft Teams to Codex

Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy.

Register kosmo mcp:serve as a local stdio server and choose the integration allowlist. The gateway is local, scoped to this integration, and starts with --write=deny so Codex can inspect read-capable tools without receiving write access by default.

Microsoft Teams MCP Config for Codex

Keep write access denied or ask-based unless the workspace is trusted.

{
  "mcpServers": {
    "kosmokrator-teams": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=teams",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=teams --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Microsoft Teams instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Microsoft Teams Tools Visible to Codex

Codex sees stable MCP tool names generated from the Microsoft Teams integration catalog.

MCP tool	Source function	Type	Description
`integration__teams__teams_list_teams`	`teams.teams_list_teams`	Read	List all Microsoft Teams the user is a member of.
`integration__teams__teams_get_team`	`teams.teams_get_team`	Read	Get detailed information about a Microsoft Team.
`integration__teams__teams_list_channels`	`teams.teams_list_channels`	Read	List all channels in a Microsoft Team.
`integration__teams__teams_get_channel`	`teams.teams_get_channel`	Read	Get detailed information about a Microsoft Teams channel.
`integration__teams__teams_send_message`	`teams.teams_send_message`	Write	Send a message to a Microsoft Teams channel.
`integration__teams__teams_list_messages`	`teams.teams_list_messages`	Read	List messages in a Microsoft Teams channel.
`integration__teams__teams_get_current_user`	`teams.teams_get_current_user`	Read	Get information about the current authenticated Microsoft 365 user.

Related Microsoft Teams Pages

Microsoft Teams CLIUse direct JSON commands instead of MCP discovery. Microsoft Teams MCPFull gateway reference and MCP tool names. KosmoKrator for CodexClient-level gateway setup.