Ext Ops Panel
Open dashboard
Comparison

sf-env-awareness vs codev

sf-env-awareness is a plugin bundle for AI coding tools published by Pierre-louis242. 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-20. 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
Marketplacesf-env-awarenesscodev
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

sf-env-awareness vs codev
Factsf-env-awarenesscodev
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot 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)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/pierre-louis242/sf-env-awarenessgithub.com/flxbl-io/codev-mcp
Changes in the last 7 days00
First seen2026-10-112026-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

sf-env-awareness

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

Salesforce-specific project auditing skill. Checks sfdx-project.json configuration, package dependency ordering, API version alignment across all metadata files, scratch org definition completeness, permission set coverage, flow conflict analysis (including Record-Triggered Flow collisions), Apex test coverage readiness, and deployment dependency ordering. Produces a structured report with exact fix commands. Built from real-world Salesforce consulting experience including multi-package projects, ISV managed packages, and 2GP pipelines.

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

sf-env-awareness As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install sf-env-awareness@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.

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: sf-env-awareness · 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