Agentteam

What is AgentTeam?

AgentTeam is a reusable AI software development team built on the Model Context Protocol (MCP). Thirteen specialized agents — Product Manager, Project Manager, UX Researcher, UX/UI Designer, Frontend, Backend, Full-Stack, Mobile, DevOps, QA, Security, Data Engineer, and Data Scientist — collaborate on software projects through a shared SQLite database, each strictly constrained to their role. It is designed to be called from any Claude Code project via MCP.

How to use AgentTeam?

Install the MCP server with one command: claude mcp add agent-team -- npx agent-team-mcp. Alternatively, edit your MCP config manually. The /team skill is installed automatically on first startup. Invoke with /team build me a REST API for task management or /team --projects to manage existing projects.

Key features of AgentTeam

• 44 MCP tools across 12 domains (projects, tasks, discussions, etc.)
• Thirteen role-constrained AI agents collaborating in parallel
• Shared SQLite database persists all project state across sessions
• Project lifecycle: active → paused → archived → closed
• User journal captures decisions, preferences, and reasoning
• Token-efficient architecture with lazy-loaded team protocol

Use cases of AgentTeam

• Spin up a full product team to design and build a new feature
• Investigate a technical subject with specialists producing structured research artifacts
• Resume paused software projects without losing context or prior decisions
• Automate multi-agent code generation, review, and deployment planning

FAQ from AgentTeam

What runtime environment does AgentTeam require?

AgentTeam runs as a Node.js MCP server and is installed via npx, so Node.js is required. The server uses SQLite for persistence and communicates over stdio.

How do I install AgentTeam?

Install it with claude mcp add agent-team -- npx agent-team-mcp. You can also manually add it to claude_desktop_config.json or run from a local clone after npm install and npm run build.

What is the user journal?

The user journal is a persistent log of your decisions, preferences, and reasoning captured during team conversations. It is scoped to a project (or global) and can be queried by future agents via list_journal_entries.

Can I reuse the same team across sessions?

Yes. All project state is persisted in a SQLite database. Any agent can rejoin a project by reading the current summary and picking up where the team left off. Projects support lifecycle transitions (active, paused, archived, closed).

How does AgentTeam avoid redundant work?

Specialists share structured research artifacts via the share_artifact tool, and the Project Manager orchestrates tasks so no agent re-researches what another has already found. The team protocol is lazy-loaded to save ~6,000 words of context.