Official Registry metadata
teams
Collaborate, chat, and manage meetings in Microsoft Teams.
48Recommendation
Configure in your coding agent
Copy this metadata-derived example, review it, and add secrets only through environment variables on your own machine.
~/.codex/config.toml or codex mcp addRun this command locally. Review package commands before confirming execution.
codex mcp add 'ai-waystation-teams-32675fa4' --url 'https://waystation.ai/teams/mcp'
.mcp.jsonAdd this entry to the project-level mcpServers object.
{
"mcpServers": {
"ai-waystation-teams-32675fa4": {
"type": "http",
"url": "https://waystation.ai/teams/mcp"
}
}
}.cursor/mcp.jsonKeep secret values as environment-variable references.
{
"mcpServers": {
"ai-waystation-teams-32675fa4": {
"type": "http",
"url": "https://waystation.ai/teams/mcp"
}
}
}.vscode/mcp.jsonReview the generated server entry before enabling it.
{
"servers": {
"ai-waystation-teams-32675fa4": {
"type": "http",
"url": "https://waystation.ai/teams/mcp"
}
}
}~/.gemini/settings.jsonAdd this entry to mcpServers and keep trust disabled initially.
{
"mcpServers": {
"ai-waystation-teams-32675fa4": {
"httpUrl": "https://waystation.ai/teams/mcp",
"trust": false
}
}
}Stacklane does not install, connect to, execute, or security-certify MCP servers. Metadata and risk signals are automated discovery aids.
Declared requirements
Risk signals
- No elevated requirement declared in registry metadata