What is an MCP plugin?

It is best treated as an agent plugin that includes MCP configuration or MCP servers as components, rather than treating the MCP server itself as the whole product.

What does an agent plugin marketplace need?

It needs installable packages, ownership, component inventory, permissions, versioning, telemetry, eval evidence, and a path to promote or retire releases.

Can Telvine publish marketplace-ready plugins?

Yes. Telvine records the plugin product and its component inventory so marketplaces can show more than a name and README.

Marketplaces

MCP Plugin Marketplace: From Tool Servers to Installable Agent Products

MCP makes tools and context easier to expose to agents. A marketplace makes those capabilities easier to install, govern, measure, and improve.

Start with Telvine Read the plugin guide

Publish the product

Use Telvine when the plugin is ready to be treated like software.

The first useful milestone is simple: one plugin directory, one owner, one release record, and one measurement model.

npm i -g @telvine/cli
telvine login
telvine publish ./my-plugin

Why MCP alone is not the product

An MCP server can expose useful tools. It does not automatically provide packaging, product ownership, release policy, install flows, telemetry, evals, or customer-facing improvement evidence.

That is why an MCP plugin marketplace should treat MCP as a component layer. The buyer installs a plugin. The plugin may include MCP servers, Skills, connectors, hooks, commands, and assets.

What a marketplace should show

A serious marketplace needs more than descriptions. It should show what the plugin does, which components it contains, which harnesses it supports, what permissions it needs, when it changed, and whether the latest version is better than the previous release.

Telvine gives plugin owners a way to publish and measure that product record.

Component inventory and supported harnesses.
Security notes, permission scopes, and data handling posture.
Version history, eval evidence, and promotion state.
Metadata-only usage, error, latency, and outcome telemetry.

Publishing with Telvine

Use the Telvine CLI to publish the plugin directory and keep the product record tied to its components.

The marketplace can then become a distribution surface, not a loose index of tool servers.

Where it applies

Use cases that deserve a maintained plugin

Internal enterprise marketplace

Give employees approved plugins for CRM, finance, knowledge, IT, and operations workflows.

MSP client catalogue

Let clients adopt packaged plugins for recurring workflows while the MSP manages versions and support.

Developer ecosystem

Help builders distribute components as installable products with telemetry and release evidence.

FAQ

Common questions

What is an MCP plugin?: It is best treated as an agent plugin that includes MCP configuration or MCP servers as components, rather than treating the MCP server itself as the whole product.
What does an agent plugin marketplace need?: It needs installable packages, ownership, component inventory, permissions, versioning, telemetry, eval evidence, and a path to promote or retire releases.
Can Telvine publish marketplace-ready plugins?: Yes. Telvine records the plugin product and its component inventory so marketplaces can show more than a name and README.