About JasonBright.Mcp.Teams
JasonBright.Mcp.Teams is an MCP server in the Science category: mCP stdio server exposing Microsoft Teams through Microsoft Graph: read teams, channels, chats and messages, and send messages behind an opt-in gate. Signs in once interactively and runs silently thereafter.
Install
git clone https://github.com/jgbright/mcp-dotnetThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Tools (26)
ado_api_requestOne REST call this server has no typed tool for, on its own credential and its own organization only. A JSON Patch body is sent as `application/json-patch+json`, which is the only type the work item endpoints take; `content_type` overrides that
Parameters not published.
ado_auth_statusWhich credential is in use, whether it still works, and whether `AZURE_DEVOPS_PAT` does
Parameters not published.
deployment_statusConfig-driven, see the deployment map section
Parameters not published.
get_pipeline_runReports each failed task with its stage, job, errors and log tail, and what the run was built from
Parameters not published.
get_pull_requestFinds the pull request from its id alone, with review threads
Parameters not published.
get_releaseArtifacts, pending approvals, and each failed task with its phase, job, errors and log tail; `include_tasks` lists every task and `task_log` fetches one's log
Parameters not published.
get_release_definitionHow one is configured: variables at both scopes, variable groups, and each environment's tasks with their inputs and the deployment group and tags each phase targets
Parameters not published.
get_release_definition_targetsWhere each stage lands: its deployment group and the machines its tags select right now. An empty `machines` list is a stage that would deploy to nothing
Parameters not published.
get_work_itemDescription, repro steps and acceptance criteria; relations and discussion on request
Parameters not published.
get_work_itemsSeveral ids in one request, with their bodies, or exactly the fields named in `fields`
Parameters not published.
Show all 26 tools
list_deployment_groupsThe machines classic release stages deploy to, with their tags and agent status. Not the Environments YAML pipelines use
Parameters not published.
list_pipeline_runsNo description in manifest
Parameters not published.
list_pipelinesNo description in manifest
Parameters not published.
list_projectsNo description in manifest
Parameters not published.
list_pull_requestsWhole project when `repo` is omitted
Parameters not published.
list_release_definitionsClassic release pipelines, with the environments each deploys to
Parameters not published.
list_releasesReleases of one definition, newest first, with every environment's status
Parameters not published.
list_reposNo description in manifest
Parameters not published.
list_work_itemsWIQL or filter arguments, see below
Parameters not published.
search_codeNeeds the Code Search extension, see below
Parameters not published.
search_release_definitionsWhere a name or value appears across every definition: in a variable, a task input, or both
Parameters not published.
search_wikiNo description in manifest
Parameters not published.
search_work_itemsFull text. `list_work_items` is the structured query
Parameters not published.
wait_for_pipeline_runPolls until the run finishes, then reports like `get_pipeline_run`. A timeout returns the run as it stands with `timedOut: true`
Parameters not published.
wait_for_pull_requestPolls until the pull request completes or is abandoned, then reports like `get_pull_request`. A timeout returns it as it stands with `timedOut: true`
Parameters not published.
wait_for_releasePolls one environment until it stops moving, then reports like `get_release`
Parameters not published.
Ask AI
Ask AI about JasonBright.Mcp.Teams
Powered by Claude · Grounded in docs
Security checks
6 checks have not been run yet.