Claude Team MCP
<div align="center">
# ๐ค Claude Team
**Multi-Agent MCP Server for AI-Powered Development Teams**
*Orchestrate GPT, Claude, Gemini and more to collaborate on complex tasks*
[](https://www.npmjs.com/package/claude-team)
[](https://www.npmjs.com/package/claude-team)
[](https://nodejs.org/)
[](https://modelcontextprotocol.io)
[](LICENSE)
[](https://github.com/7836246/claude-team-mcp)
[English](README.md) | [็ฎไฝไธญๆ](README_CN.md)
</div>
---
## โจ Features
| Feature | Description |
|---------|-------------|
| ๐ค **Multi-Model Collaboration** | Configure multiple AI models to work together, each leveraging their strengths |
| ๐ง **Smart Task Distribution** | Tech Lead analyzes tasks and automatically assigns them to the best-suited experts |
| ๐ **Workflow Templates** | 5 pre-built workflows: code generation, bug fixing, refactoring, review, documentation |
| ๐ฏ **Custom Experts** | Define your own experts (Rust, K8s, Security, etc.) via environment variables |
| ๐ **Observability** | Dashboard, cost estimation, and task planning preview |
| ๐ **Proxy API Support** | Custom Base URLs, compatible with various proxy services |
| ๐ **Collaboration History** | Complete record of all collaborations with search support |
---
## ๐ Quick Start
### Installation
```bash
# Global install
npm install -g claude-team
# Or use directly with npx (no install needed)
npx claude-team
```
### Basic Configuration
Add to your IDE's MCP configuration file:
<details>
<summary><b>๐ Configuration File Locations</b></summary>
| IDE | Path |
|-----|------|
| **Claude Code** | `~/.claude/config.json` |
| **Windsurf** | `~/.codeium/windsurf/mcp_config.json` |
| **Cursor** | `~/.cursor/mcp.json` |
</details>
```json
{
"mcpServers": {
"claude-team": {
"command": "npx",
"args": ["-y", "claude-team"],
"env": {
"CLAUDE_TEAM_MAIN_KEY": "sk-your-api-key",
"CLAUDE_TEAM_MAIN_URL": "https://api.openai.com/v1",
"CLAUDE_TEAM_MAIN_MODEL": "gpt-4o",
"CLAUDE_TEAM_MAIN_PROVIDER": "openai"
}
}
}
}
```
### Start Using
```
> Help me build a user login feature with the team
> Have the team optimize this code for performance
```
---
## ๐ฌ How It Works
```
User: "Optimize this SQL query for performance"
Tech Lead Analysis โ
โโโ Creates: SQL Optimization Expert (powerful)
โโโ Creates: Index Analysis Expert (balanced)
โโโ Workflow: sequential
```
```
User: "Build a settings page with dark mode"
Tech Lead Analysis โ
โโโ Creates: UI Component Expert (balanced)
โโโ Creates: Theme System Expert (fast)
โโโ Creates: State Management Expert (balanced)
โโโ Workflow: parallel โ review
```
---
## ๐ ๏ธ Available Tools
### Core Tools
| Tool | Description |
|------|-------------|
| `team_work` | ๐ Team collaboration (auto-creates experts) |
| `ask_expert` | ๐ฌ Consult an expert (supports custom experts) |
| `code_review` | ๐ Code review |
| `fix_bug` | ๐ Bug fixing |
### Workflow Tools
| Tool | Description |
|------|-------------|
| `list_workflows` | ๐ List all workflow templates |
| `run_workflow` | โถ๏ธ Execute a specific workflow |
| `suggest_workflow` | ๐ก Auto-recommend workflow based on task |
**Pre-built Workflows:**
| Workflow | Purpose | Steps |
|----------|---------|-------|
| `code-generation` | Generate code from requirements | Design โ Implement โ Test โ Review |
| `bug-fix` | Diagnose and fix bugs | Diagnose โ Fix โ Verify |
| `refactoring` | Code refactoring | Analyze โ Plan โ Execute โ Review |
| `code-review` | Multi-dimensional review | Security / Quality / Performance (parallel) |
| `documentation` | Generate documentation | Analyze โ Document |
### Observability Tools
| Tool | Description |
|------|-------------|
| `team_dashboard` | ๐๏ธ View team status, experts, models, stats |
| `cost_estimate` | ๐ฐ Estimate task cost (tokens, price, time) |
| `explain_plan` | ๐ง Preview task assignment plan |
| `usage_stats` | ๐ View model usage statistics |
### Integration Tools
| Tool | Description |
|------|-------------|
| `read_project_files` | ๐ Read project files for context |
| `analyze_project_structure` | ๐๏ธ Analyze project structure and tech stack |
| `generate_commit_message` | ๐ Generate commit message from diff |
### History Tools
| Tool | Description |
|------|-------------|
| `history_list` | ๐ View collaboration history |
| `history_get` | ๐ Get history details |
| `history_search` | ๐ Search history records |
| `history_context` | ๐ Get recent context |
---
## โ๏ธ Configuration
### Environment Variables
| Variable | Required | Description |
|----------|----------|-------------|
| `CLAUDE_TEAM_MAIN_KEY` | โ
| Main model API Key |
| `CLAUDE_TEAM_MAIN_URL` | โ | Main model API URL |
| `CLAUDE_TEAM_MAIN_MODEL` | โ | Main model ID (default: gpt-4o) |
| `CLAUDE_TEAM_MAIN_PROVIDER` | โ | Provider: `openai` / `anthropic` / `gemini` |
| `CLAUDE_TEAM_MODEL{N}_*` | โ | Worker model N config (inherits from MAIN) |
| `CLAUDE_TEAM_CUSTOM_EXPERTS` | โ | Custom experts (JSON format) |
> N = 1, 2, 3... supports up to 10 worker models
### Custom Experts
Define your own experts beyond the built-in `frontend`, `backend`, `qa`:
```json
{
"env": {
"CLAUDE_TEAM_CUSTOM_EXPERTS": "{\"rust\":{\"name\":\"Rust Expert\",\"prompt\":\"You are a Rust expert...\",\"tier\":\"powerful\"},\"k8s\":{\"name\":\"K8s Expert\",\"prompt\":\"You are a Kubernetes expert...\",\"tier\":\"balanced\"}}"
}
}
```
| Field | Required | Description |
|-------|----------|-------------|
| `name` | โ
| Expert display name |
| `prompt` | โ
| Expert role description (System Prompt) |
| `tier` | โ | Model tier: `fast` / `balanced` / `powerful` |
| `skills` | โ | Skill tags array |
### Model Tiers
| Tier | Use Case | Example Scenarios |
|------|----------|-------------------|
| `fast` | Simple, quick tasks | Formatting, simple queries, docs |
| `balanced` | Regular dev tasks | Components, APIs, unit tests |
| `powerful` | Complex reasoning | Architecture, optimization, security |
---
## ๐ฆ Changelog
### v0.4.0
- ๐ฏ **Custom Experts** - Define experts via environment variables
- ๐ **Workflow Templates** - 5 pre-built workflows
- ๐ **Observability** - Dashboard, cost estimation, plan preview
- ๐ **Integration** - Project file reading, structure analysis, commit messages
- ๐ก **Smart Recommendations** - Auto-suggest workflows
- ๐งช **Test Coverage** - 155 test cases
### v0.3.0
- ๐ Task interrupt/resume support
- ๐ฌ Multi-turn expert conversations
- ๐ Token counting and cost estimation
- ๐ Expert templates (6 built-in + custom)
- ๐ Webhook notifications
- โก Exponential backoff retry
- ๐ง Hot config reload
<details>
<summary>Earlier versions</summary>
### v0.2.x
- ๐ Streaming output support
- ๐ Usage statistics
- ๐ฏ Model strategies
- ๐พ Result caching
- ๐ Auto model switching
### v0.1.x
- ๐ Initial release
- ๐ค Multi-model collaboration
- ๐ Proxy API support
</details>
---
## ๐ค Contributing
Contributions are welcome! Please read our:
- [Contributing Guide](CONTRIBUTING.md)
- [Code of Conduct](CODE_OF_CONDUCT.md)
- [Security Policy](SECURITY.md)
## ๐ License
[MIT](LICENSE)
---
<div align="center">
## โญ Star History
[](https://star-history.com/#7836246/claude-team-mcp&Date)
---
**[โฌ Back to Top](#-claude-team)**
Made with โค๏ธ by the community
</div>
TDQS
Scored across 18 tools
Most tools have distinct purposes (e.g., analyze_project_structure vs. team_work), but some overlap exists between 'ask_expert', 'code_review', and 'fix_bug' as they all involve expert interaction, though at different stages of development.
Tools predominantly use snake_case with descriptive names (e.g., 'analyze_project_structure', 'generate_commit_message'), but some like 'history_context' and 'team_dashboard' are more noun-centric, breaking the verb_noun pattern slightly.
At 18 tools, the server is slightly above the ideal range of 3-15 but still manageable. The count aligns with the broad scope of team collaboration, workflow management, and history tracking.
The tool set covers key operations for team collaboration (analysis, code review, bug fixing, workflow execution, history) but lacks administrative features like workflow creation or team member management, leaving minor gaps.