Ext Ops Panel
Open dashboard
Comparison

al-development-collection-for-claude-code vs codev

al-development-collection-for-claude-code is a plugin bundle for AI coding tools published by javiarmesto. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). codev is an MCP server published by flxbl-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceal-development-collection-for-claude-codecodev
Claude Code: claude-plugins-community Listed
Version: 4.2.0
Forks (GitHub): 37
Stars (GitHub): 109
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.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

al-development-collection-for-claude-code vs codev
Factal-development-collection-for-claude-codecodev
Marketplaces that list it11
Stars (GitHub) (differs)109 (better)0 (worse)
Forks (GitHub) (differs)37 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.context7.com/mcp)Not stated
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)3Not published
Parts of the bundle (differs)41Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/javiarmesto/aldc-al-development-collection-for-github-copilotgithub.com/flxbl-io/codev-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 days agono remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

al-development-collection-for-claude-code

In its own words, on Claude Code: claude-plugins-community:

ALDC (AL Development Collection) is a comprehensive AI-assisted development toolkit for Microsoft Dynamics 365 Business Central. It provides 4 specialized agents (architect, conductor, developer, presales), 11 domain knowledge skills (API, events, pages, performance, testing, etc.), and 6 development workflows (spec creation, build, PR preparation, etc.). Key features: • Extension-only development — never modifies base application objects • Human-in-the-Loop gates at critical decision points • TDD/spec-driven development cycle • Event-driven architecture patterns • Skills Evidencing — agents declare which skills and patterns they applied • 8 path-scoped AL rules (injected via /aldc:al-initialize) • 3 MCP servers for AL symbols, documentation, and Microsoft Learn First-time setup: run /aldc:al-initialize in your AL project directory.

codev

In its own words, on Official MCP Registry:

Connect AI agents to codev for Salesforce projects, builds, releases, validations, and insights.

How to run each

al-development-collection-for-claude-code As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install al-development-collection-for-claude-code@claude-community

codev

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only al-development-collection-for-claude-code 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: al-development-collection-for-claude-code · What it can do: codev · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built