Ext Ops Panel
Open dashboard
Comparison

OCPF BC Agentic Development Framework vs codev

OCPF BC Agentic Development Framework is a plugin bundle for AI coding tools published by OnlyCopilotFans. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-17. 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
MarketplaceOCPF BC Agentic Development Frameworkcodev
Community marketplace ajansari/ocpfbcagenticdevframework Listed
Version: 5.7.3
Forks (GitHub): 3
Stars (GitHub): 8
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

OCPF BC Agentic Development Framework vs codev
FactOCPF BC Agentic Development Frameworkcodev
Marketplaces that list it11
Stars (GitHub) (differs)8 (better)0 (worse)
Forks (GitHub) (differs)3 (better)0 (worse)
Last release (differs)2026-10-15Not published
Where it runs (differs)Installs as a plugin bundleNot stated
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)15Not a bundle
Licence (differs)PolyForm-Shield-1.0.0Not stated
Repository (differs)github.com/ajansari/ocpfbcagenticdevframeworkgithub.com/flxbl-io/codev-mcp
Changes in the last 7 days (differs)40
First seen (differs)2026-10-152026-10-11

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

OCPF BC Agentic Development Framework

In its own words, on Community GitHub marketplaces:

The OnlyCopilotFans Business Central Agentic Development Framework: a guided DEFINE, DESIGN, BUILD, PROVE routine for building AL extensions the right way, per-tenant or for AppSource. Picks Full, Lite, or Build-a-Feature (one object or a few, no steps, no documents), sets up the latest runbook, connects Microsoft's AL tools with nothing to install, adds reasoning, light, and generator sub-agents, writes every project document from a template, measures token usage and cost at every step boundary, and keeps a live HTML dashboard of the build.

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

OCPF BC Agentic Development Framework As a Claude Code plugin

Claude Code
/plugin marketplace add ajansari/ocpfbcagenticdevframework
/plugin install ocpf-bc@onlycopilotfans

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.

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: OCPF BC Agentic Development Framework · What it can do: codev · 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.

Where the data comes from: how the catalog is built