Ext Ops Panel
Open dashboard
Comparison

crosstalk vs io.github.lennix1337/genexus

crosstalk is a plugin bundle for AI coding tools published by d7omdev. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.lennix1337/genexus is an MCP server published by lennix1337. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-29. 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
Marketplacecrosstalkio.github.lennix1337/genexus
Community marketplace davepoon/buildwithclaude Listed
Version: 0.1.0
Forks (GitHub): 662
Stars (GitHub): 3 687
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.0.4
Downloads/month (npm): 7 136
Downloads/week (npm): 600
Forks (GitHub): 27
Stars (GitHub): 39
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 4.0.4
Downloads/month (npm): 7 136
Downloads/week (npm): 600
Forks (GitHub): 27
Stars (GitHub): 39
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

crosstalk vs io.github.lennix1337/genexus
Factcrosstalkio.github.lennix1337/genexus
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)3 687 (better)39 (worse)
Forks (GitHub) (differs)662 (better)27 (worse)
Last release (differs)Not published2026-10-27
Where it runs (differs)Installs as a plugin bundleOn your machine (genexus-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)3Not a bundle
Licence (differs)Not statedMIT
Repository (differs)github.com/davepoon/buildwithclaudegithub.com/lennix1337/genexus18mcp
Changes in the last 7 days (differs)02
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

crosstalk

In its own words, on Community GitHub marketplaces:

Let a Claude session in one repo delegate work to a Claude session in another repo, with a request format that avoids follow-up round trips. Adds /ask-peer plus skills for sending and answering cross-repo requests.

io.github.lennix1337/genexus

In its own words, on Official MCP Registry:

Read, edit, and analyze GeneXus 18 KB objects from Claude, Cursor, and AI agents.

How to run each

crosstalk As a Claude Code plugin

Claude Code
/plugin marketplace add davepoon/buildwithclaude
/plugin install crosstalk@buildwithclaude

io.github.lennix1337/genexus As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio genexus -- npx -y genexus-mcp

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: crosstalk · What it can do: io.github.lennix1337/genexus · 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. Package data comes from the public npm registry (registry.npmjs.org). 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