agent-team vs Lycatra
agent-team is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
agent-team is a plugin bundle for AI coding tools published by bmcreations. No marketplace we read lists it any more. Lycatra is an MCP server published by lycatra.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Lycatra | |
|---|---|---|
| Community marketplace bmcreations/agent-team | Removed on 2026-10-15 Version: 0.4.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | agent-teamno longer listed · | Lycatra |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (lycatra.com/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/bmcreations/agent-team | github.com/lycatra/lycatra-plugin |
| Changes in the last 7 days (differs) | 4 | 2 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 35 h ago, requires a key |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of agent-team
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Tenant-isolated AI teams that plan work, coordinate tasks, recall approved context, and return evidence-backed results
-
Standalone Markdown-only Agent Team plugin for Claude Code and Codex. Coordination happens through ordinary Markdown files in the current project: agent-team/ ├──…
-
Multi-agent collaboration — spawn N parallel subagents that compete on code optimization, content drafts, research approaches, or any task that benefits from diverse solutions. 7…
-
A modular plugin that packs specialised agents into teams and allows user to interact with them at the higher level of abstraction. Like with real-world company departments.
-
The user can inject experts into their Claude Code session. It provides the programmed experts with specific priorities, communication styles, and domain knowledge to help. Each…
-
Shared task wall, memory, reports, channels and Dashboard for Claude Code and Codex; Claude Code plugin installation and an independent Codex adapter
What each says it does
agent-team
Delegate a task to Codex, Grok, or Claude by naming a team member rather than a vendor
Lycatra
Connect agents to Lycatra knowledge, memory, collaboration, schedules, notifications, and teams.
How to run each
agent-team
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Lycatra As a remote MCP server
claude mcp add --transport http lycatra https://lycatra.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Lycatra has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: agent-team · What it can do: Lycatra · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.