Ext Ops Panel
Open dashboard
Comparison

Enterprise Search vs Tsenta: AI job application agent

Enterprise Search is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). Tsenta: AI job application agent is an MCP server published by tsenta.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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
MarketplaceEnterprise SearchTsenta: AI job application agent
Claude: knowledge-work-plugins Listed
Version: 1.3.0
Forks (GitHub): 3 913
Stars (GitHub): 35 283
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

Enterprise Search vs Tsenta: AI job application agent
FactEnterprise SearchTsenta: AI job application agent
Marketplaces that list it11
Stars (GitHub) (differs)35 283 (better)0 (worse)
Forks (GitHub) (differs)3 913 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.autojobs.me/api/v1/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)12Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/anthropics/knowledge-work-pluginsgithub.com/tsenta/tsenta-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-05
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 33 h ago returned HTTP 401

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

Enterprise Search

In its own words, on Claude: knowledge-work-plugins:

Search across all of your company's tools in one place. Find anything across email, chat, documents, and wikis without switching between apps.

Tsenta: AI job application agent

In its own words, on Official MCP Registry:

Find jobs, tailor your resume to each role and apply on Workday, Greenhouse, Lever, Ashby and more.

How to run each

Enterprise Search As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install enterprise-search@knowledge-work-plugins

Tsenta: AI job application agent As a remote MCP server

Claude Code
claude mcp add --transport http tsenta https://api.autojobs.me/api/v1/mcp

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

Only Tsenta: AI job application agent 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: Enterprise Search · What it can do: Tsenta: AI job application agent · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/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