MetaGPT
Open-source Python multi-agent framework that assigns product manager, architect, project manager, engineer, and other software-company roles to LLM agents for natural-language programming, repo generation, data interpretation, research, debate, and custom agent workflows.
Open the source and read safety notes before installing.
Safety notes
- MetaGPT can generate full repositories under a workspace from one-line requirements. Review generated code, dependencies, licenses, prompts, and build scripts before running or publishing anything.
- The framework coordinates multiple LLM roles and can call code, web, RAG, browser, email, GitHub, and provider integrations through its dependencies and optional extras; scope credentials and tools per workflow.
- Generated requirements, API designs, architecture documents, diagrams, and code can be plausible but wrong. Treat them as drafts until tested against source requirements and local constraints.
- Data Interpreter and notebook-style workflows may execute code, create plots, read files, and emit artifacts; run them in an isolated environment for untrusted data.
- Long multi-agent runs can consume significant model tokens and external API quota, so set cost ceilings, timeouts, and stopping criteria before production use.
Privacy notes
- Requirements, prompts, role messages, generated code, diagrams, documents, repo files, notebook outputs, model responses, logs, and traces may contain private product or workspace data.
- Configured LLM providers, browser/search tools, RAG/vector services, GitHub integrations, email/IMAP tools, cloud providers, and generated workspaces may receive or retain workflow data.
- Do not commit `~/.metagpt/config2.yaml`, provider keys, local model URLs, generated repos with secrets, workspace logs, notebook outputs, or customer requirements.
- If teams share MetaGPT outputs, strip private prompts, internal system names, customer data, generated credentials, and non-public architecture details first.
Prerequisites
- Python 3.9 through 3.11 and an isolated Python environment.
- Node.js and pnpm for workflows that render diagrams or use MetaGPT's documented software-company generation path.
- LLM provider configuration in `~/.metagpt/config2.yaml`, such as OpenAI, Azure, Ollama, Groq, or another supported provider route.
- API keys, base URLs, local model endpoints, and generated workspace paths kept outside source control.
- A review plan for generated repositories, diagrams, requirements, documents, code, and Data Interpreter outputs before use.
Schema details
- Install type
- cli
- Troubleshooting
- No
- Scope
- Source repo
- Estimated setup
- 30 minutes
- Difficulty
- intermediate
- Pricing
- free
- Disclosure
- editorial
- Application category
- DeveloperApplication
- Operating system
- Cross-platform
Full copyable content
pip install --upgrade metagptAbout this resource
Overview
MetaGPT is an open-source Python framework for building software-company style multi-agent workflows. Its README frames the core pattern as assigning different roles to GPT-backed agents so they collaborate on complex tasks. For software generation, MetaGPT can take a one-line requirement and produce artifacts such as user stories, competitive analysis, requirements, data structures, APIs, documents, and repository files.
The entry is useful for Claude-adjacent teams because MetaGPT is a high-search, high-star agent framework with a distinct mental model: instead of a single coding assistant or generic tool-calling loop, it models a team with product manager, architect, project manager, engineer, and related roles following orchestrated SOPs.
Install
Install the PyPI package:
pip install --upgrade metagpt
The README also documents conda setup, source installs, and a requirement to install Node.js and pnpm before actual use:
conda create -n metagpt python=3.9
conda activate metagpt
Initialize configuration before running workflows:
metagpt --init-config
Then edit ~/.metagpt/config2.yaml with the selected LLM provider, model, base
URL, and API key.
Common Commands
Generate a small project from a requirement:
metagpt "Create a 2048 game"
Use MetaGPT as a Python library:
from metagpt.software_company import generate_repo
repo = generate_repo("Create a 2048 game")
print(repo)
Run a Data Interpreter workflow:
import asyncio
from metagpt.roles.di.data_interpreter import DataInterpreter
async def main():
di = DataInterpreter()
await di.run("Run data analysis on sklearn Iris dataset, include a plot")
asyncio.run(main())
Agent Capabilities
| Area | MetaGPT Coverage |
|---|---|
| Multi-agent model | Product manager, architect, project manager, engineer, and other role-based agents |
| Software generation | User stories, competitive analysis, requirements, data structures, APIs, documents, diagrams, and repository files |
| CLI | metagpt console script for running natural-language requirements |
| Python API | generate_repo, ProjectRepo, Data Interpreter, and custom role/workflow development |
| Provider config | ~/.metagpt/config2.yaml with OpenAI-style, Azure, Ollama, Groq, and other model routes described by the README |
| Optional capabilities | Search, Selenium/browser workflows, RAG, Data Interpreter, Android assistant extras, GitHub/email/cloud integrations, and test/dev extras |
| Research surface | MetaGPT paper, AFlow/SPO/AOT research links, agent tutorials, debate, researcher, and Data Interpreter use cases |
MCP Fit
MetaGPT is not an MCP server. It belongs in tools as a framework and CLI for role-based multi-agent workflows. It can still be useful in the same search cluster as MCP because teams often compare MCP tool access with higher-level agent frameworks. If MetaGPT agents are connected to external tools, browsers, repos, email, or RAG systems, apply the same permission and approval discipline you would apply to MCP-connected agents.
Source Review
Verified on 2026-06-18:
- GitHub reports
FoundationAgents/MetaGPTas an MIT-licensed repository with 68,000+ stars and a latest release tagv0.8.1. - The README describes MetaGPT as a multi-agent framework that assigns different roles to GPTs and models a software company as a multi-agent system.
- The README documents
pip install --upgrade metagpt, Python 3.9+ and<3.12, Node.js and pnpm prerequisites,metagpt --init-config,~/.metagpt/config2.yaml, CLI usage, Python library usage, and Data Interpreter usage. setup.pydeclares themetagptpackage, MIT license, Python>=3.9,<3.12, console scriptmetagpt=metagpt.software_company:app, and extras for Selenium, search, RAG, tests, development, and Android assistant workflows.requirements.txtincludes provider, browser, RAG/vector, GitHub, email, notebook, data, and model integration dependencies.- PyPI resolves package metadata for
metagptversion0.8.2; currentmainsource metadata shows a newersetup.pyversion value, so version-sensitive install decisions should check PyPI and the upstream repository before pinning.
Safety and Privacy
MetaGPT's most attractive workflow is also the risky one: a brief requirement can produce many files, diagrams, dependencies, and design decisions. Keep that output in a reviewable workspace, run tests before trusting it, and do not let generated repositories inherit production credentials or privileged shells.
Role messages, product requirements, architecture documents, generated source,
notebook outputs, and tool results may expose sensitive product plans or
customer context. Treat ~/.metagpt/config2.yaml, generated workspaces, logs,
and shared artifacts as private until reviewed.
Duplicate Check
Checked current content/tools/, content/mcp/, content/agents/,
content/skills/, guides, collections, open pull requests, and repository-wide
content for FoundationAgents/MetaGPT, geekan/MetaGPT, MetaGPT, metagpt,
AI software company, software company as multi-agent system, Data Interpreter,
natural-language programming, and role-based multi-agent framework. Existing
entries cover adjacent agent frameworks and coding agents such as AutoGen,
CrewAI, LangGraph, Agno, Mastra, Pydantic AI, Smolagents, CAMEL, OpenHands,
Open SWE, mini-SWE-agent, and Claude Code, but no dedicated MetaGPT tools entry,
exact source URL duplicate, target file, or open duplicate PR was found.
Source citations
Add this badge to your README
How it compares
MetaGPT side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | MetaGPT Open-source Python multi-agent framework that assigns product manager, architect, project manager, engineer, and other software-company roles to LLM agents for natural-language programming, repo generation, data interpretation, research, debate, and custom agent workflows. Open dossier | AgentScope Apache-2.0 Python framework for building visible, controllable, production AI agents and multi-agent services with event streaming, permission controls, workspaces, sandbox backends, middleware, MCP support, Mem0 memory, agent teams, and multi-tenant multi-session serving. Open dossier | CAMEL-AI CAMEL Open-source Python multi-agent framework for building agent societies, role-playing agents, stateful ChatAgent workflows, RAG agents, synthetic data generation, MCP-enabled use cases, and research-scale agent experiments. Open dossier | AG2 Agent Framework Open-source Python AgentOS and multi-agent framework, evolved from AutoGen, for building conversable agents, group chats, swarms, human-in-the-loop workflows, tool use, RAG, code execution, and provider-backed agent systems. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | tools | tools | tools | tools |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | FoundationAgents | AgentScope | CAMEL-AI | AG2 |
| Added | 2026-06-18 | 2026-06-18 | 2026-06-18 | 2026-06-18 |
| Platforms | CLI | CLI | CLI | CLI |
| Source repo | — | — | — | — |
| Safety notes | ✓MetaGPT can generate full repositories under a workspace from one-line requirements. Review generated code, dependencies, licenses, prompts, and build scripts before running or publishing anything. The framework coordinates multiple LLM roles and can call code, web, RAG, browser, email, GitHub, and provider integrations through its dependencies and optional extras; scope credentials and tools per workflow. Generated requirements, API designs, architecture documents, diagrams, and code can be plausible but wrong. Treat them as drafts until tested against source requirements and local constraints. Data Interpreter and notebook-style workflows may execute code, create plots, read files, and emit artifacts; run them in an isolated environment for untrusted data. Long multi-agent runs can consume significant model tokens and external API quota, so set cost ceilings, timeouts, and stopping criteria before production use. | ✓AgentScope examples can give agents Bash, file-read, file-write, edit, search, MCP, and custom tools. Scope tool permissions and approval rules before connecting a real project or account. The README demonstrates permission control, including bypass mode. Do not use bypass-style behavior on production systems, sensitive files, paid APIs, cloud resources, or unreviewed tool chains without compensating controls. Workspace support can run tools and code through local, Docker, or E2B backends; review filesystem mounts, network access, secrets, resource limits, and cleanup behavior. Agent teams, background tasks, and multi-session services can continue work after the initial request; define cancellation, timeout, wakeup, escalation, and audit behavior. Mem0 memory, Redis-backed sessions, MCP configuration, OpenTelemetry, FastAPI services, and model-provider integrations all need version pinning, credential isolation, and security review before production use. | ✓CAMEL agents can coordinate multi-step tasks, call tools, use web/search integrations, connect to MCP examples, and run with provider credentials; review tool permissions before giving agents write access or account access. Large-scale agent societies and role-playing workflows can generate high volumes of model calls, tool calls, logs, synthetic data, and intermediate artifacts; set budgets, rate limits, and stop conditions before long runs. RAG, document, media, browser, communication, and data-tool extras may access local files, third-party APIs, vector stores, notebooks, or generated datasets; isolate experiments from production systems. CAMEL examples include MCP-oriented use cases, but MCP does not make connected tools safe by default. Scope server permissions, credentials, filesystem access, and approval gates separately. Do not treat generated code, generated datasets, citations, research summaries, or multi-agent decisions as verified until they have been reviewed against source data and policy requirements. | ✓AG2 agents can converse, call tools, execute code, use retrieval systems, run browser workflows, and coordinate group chats; require explicit permissions and approval gates for high-impact actions. The upstream install docs and examples commonly involve provider credentials; keep API keys, config files, notebooks, and `.env` files out of commits and support tickets. Code execution, Docker, Jupyter, browser-use, and RAG extras can touch local files, network services, notebooks, databases, and external websites; scope them tightly before granting agent access. Multi-agent conversations can continue through nested chats, swarms, group chats, and custom reply handlers; define termination, escalation, retry, and human takeover behavior. Track the release roadmap before upgrading because deprecations and the v1.0 transition can change which APIs should be used for new work. |
| Privacy notes | ✓Requirements, prompts, role messages, generated code, diagrams, documents, repo files, notebook outputs, model responses, logs, and traces may contain private product or workspace data. Configured LLM providers, browser/search tools, RAG/vector services, GitHub integrations, email/IMAP tools, cloud providers, and generated workspaces may receive or retain workflow data. Do not commit `~/.metagpt/config2.yaml`, provider keys, local model URLs, generated repos with secrets, workspace logs, notebook outputs, or customer requirements. If teams share MetaGPT outputs, strip private prompts, internal system names, customer data, generated credentials, and non-public architecture details first. | ✓AgentScope workflows can process prompts, model responses, tool arguments, tool outputs, workspace files, code, credentials accidentally present in context, event streams, web UI state, logs, traces, memory records, session state, and tenant metadata. Long-term memory through Mem0 and multi-session service storage can persist user facts, intermediate outputs, retrieved context, and tool results beyond a single conversation. Docker, E2B, MCP servers, model providers, Redis, OpenTelemetry exporters, FastAPI deployments, and web UI integrations may send or store data outside the local Python process depending on configuration. Do not expose private prompts, API keys, unpublished code, customer data, tenant identifiers, session transcripts, or workspace artifacts in public issues, examples, screenshots, logs, or generated reports. | ✓Prompts, model responses, agent messages, tool arguments, tool outputs, retrieved documents, search results, logs, generated datasets, traces, and errors may include user or workspace data. Model providers, search providers, MCP servers, vector stores, web tools, document parsers, browser tools, and observability integrations may receive data from CAMEL workflows. Keep provider API keys, OAuth tokens, MCP server credentials, vector database URLs, generated logs, and synthetic datasets out of committed examples, screenshots, public issues, and shared notebooks. If `CAMEL_MODEL_LOG_ENABLED` or other logging/tracing integrations are enabled, review request/response logs and model configuration logs before sharing or retaining them. | ✓Prompts, messages, tool arguments, tool outputs, code snippets, notebook state, retrieved documents, vector-store contents, provider responses, traces, and execution logs may contain sensitive user or workspace data. Do not expose secrets, API keys, private file paths, customer records, internal documents, database rows, or raw exceptions through agent messages, logs, notebooks, screenshots, or public examples. Provider extras and retrieval integrations can route data through OpenAI, Anthropic, Google, AWS, local model servers, databases, vector stores, browser automation, or other third-party services. If AG2 is used for code execution or browser automation, define which files, domains, credentials, downloads, screenshots, and logs can be read or retained. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Featured in
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.