# Claude Team MCP MCP server

Agent View of the PolicyLayer registry record for Claude Team MCP: identity, probed posture, risk grade, and all 18 tools classified. HTML page: https://policylayer.com/tools/7836246-claude-team-mcp

## Facts

- Server id: `7836246/claude-team-mcp`
- Homepage: https://github.com/7836246/claude-team-mcp
- Registry record: grade D, identity unverified
- Lifecycle: active
- Rate-limited: no
- Tools: 18
- Tool categories present: Execute, Read, Write
- Tags: 7836246 claude team mcp, automation
- Record last modified: 2026-09-28T02:09:20.452Z

## Tools (18)

| Tool | Category | Risk | Record |
| --- | --- | --- | --- |
| `fix_bug` | Execute | High | https://policylayer.com/tools/7836246-claude-team-mcp/fix-bug.md |
| `run_workflow` | Execute | High | https://policylayer.com/tools/7836246-claude-team-mcp/run-workflow.md |
| `team_work` | Execute | High | https://policylayer.com/tools/7836246-claude-team-mcp/team-work.md |
| `analyze_project_structure` | Read | Low | https://policylayer.com/tools/7836246-claude-team-mcp/analyze-project-structure.md |
| `ask_expert` | Read | Low | https://policylayer.com/tools/7836246-claude-team-mcp/ask-expert.md |
| `code_review` | Read | Low | https://policylayer.com/tools/7836246-claude-team-mcp/code-review.md |
| `cost_estimate` | Read | Low | https://policylayer.com/tools/7836246-claude-team-mcp/cost-estimate.md |
| `explain_plan` | Read | Low | https://policylayer.com/tools/7836246-claude-team-mcp/explain-plan.md |
| `history_context` | Read | Low | https://policylayer.com/tools/7836246-claude-team-mcp/history-context.md |
| `history_get` | Read | Low | https://policylayer.com/tools/7836246-claude-team-mcp/history-get.md |
| `history_list` | Read | Low | https://policylayer.com/tools/7836246-claude-team-mcp/history-list.md |
| `history_search` | Read | Low | https://policylayer.com/tools/7836246-claude-team-mcp/history-search.md |
| `list_workflows` | Read | Low | https://policylayer.com/tools/7836246-claude-team-mcp/list-workflows.md |
| `read_project_files` | Read | Low | https://policylayer.com/tools/7836246-claude-team-mcp/read-project-files.md |
| `suggest_workflow` | Read | Low | https://policylayer.com/tools/7836246-claude-team-mcp/suggest-workflow.md |
| `team_dashboard` | Read | Low | https://policylayer.com/tools/7836246-claude-team-mcp/team-dashboard.md |
| `usage_stats` | Read | Low | https://policylayer.com/tools/7836246-claude-team-mcp/usage-stats.md |
| `generate_commit_message` | Write | Medium | https://policylayer.com/tools/7836246-claude-team-mcp/generate-commit-message.md |

## Tool descriptions

- `fix_bug` — 让 QA 专家修复 Bug
- `run_workflow` — 使用指定工作流执行任务
- `team_work` — 让 AI 开发团队协作完成任务。团队包含前端专家、后端专家、QA专家，会智能分配任务并互相协作。
- `analyze_project_structure` — 分析项目结构，识别技术栈和架构
- `ask_expert` — 向特定专家咨询问题
- `code_review` — 让专家审查代码
- `cost_estimate` — 预估任务执行成本（Token 用量、预计耗时）
- `explain_plan` — 解释 Tech Lead 会如何分配任务（不实际执行）
- `history_context` — 获取最近的协作上下文，可用于继续之前的工作
- `history_get` — 获取某次协作的详细记录
- `history_list` — 查看团队协作历史记录列表
- `history_search` — 搜索协作历史记录
- `list_workflows` — 列出所有可用的工作流模板
- `read_project_files` — 读取项目文件内容，让专家了解代码上下文
- `suggest_workflow` — 根据任务自动推荐合适的工作流
- `team_dashboard` — 查看团队当前状态：可用专家、模型配置、最近活动
- `usage_stats` — 查看各模型的使用统计（调用次数、成功率、平均耗时）
- `generate_commit_message` — 根据代码变更生成 Git commit message

## Related servers

- UnClick (1662 tools) — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server.md
- Apibase (1384 tools) — https://policylayer.com/tools/io-github-whiteknightonhorse-apibase.md
- Delx Mcp A2a (1068 tools) — https://policylayer.com/tools/io-github-davidmosiah-delx-mcp-a2a.md
- MCP Framework Personal (912 tools) — https://policylayer.com/tools/inggerman-mcps.md
- Hermoso (896 tools) — https://policylayer.com/tools/hermoso.md
- Nodebench (824 tools) — https://policylayer.com/tools/io-github-homenshum-nodebench.md
- Altium-MCP-Suite (817 tools) — https://policylayer.com/tools/altium-mcp-suite.md
- Eda Agent (777 tools) — https://policylayer.com/tools/eda-agent.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=7836246-claude-team-mcp · API: https://policylayer.com/registry/api · Recommended policies for every tool: https://policylayer.com/policies/7836246-claude-team-mcp