Plugins & marketplace

4RGE has a plugin marketplace backed by a plugin registry. Plugins connect external services and tools to the platform so agents can work with them — many plugins are MCP tool servers for popular services, bundled with skills, rules, and hooks that guide agent behavior.

Installing a plugin does not bypass security: new tools register through the tool broker and follow the same approval and scoping rules as built-in tools.

What plugins add

Installed plugins expose new capabilities to agents:

All MCP tools flow through the tool broker. The marketplace includes integrations for a wide range of services, for example:

Browse the full catalog in the in-app Marketplace — the registry lists dozens of curated plugins with descriptions, logos, and install instructions.

Plugin anatomy

Each plugin ships a manifest under .4rge-plugin/plugin.json:

{
  "name": "my-plugin",
  "displayName": "My Service",
  "description": "Short description shown in the marketplace",
  "version": "1.0.0",
  "logo": "assets/logo.svg",
  "skills": "./skills/",
  "rules": "./rules/",
  "hooks": "hooks/hooks.json",
  "mcpServers": "./mcp.json"
}

Supporting files typically include:

See the create-plugin marketplace plugin if you are authoring a new integration.

Using plugins

1. Browse the marketplace

   Open Marketplace in 4RGE Desktop and search by service name or category.

2. Install

   Install the plugin for your user or workspace. Org admins may restrict which plugins are available.

3. Connect MCP

   Go to Tools & MCP, select the plugin's server(s), and complete OAuth or API key setup.

4. Use in prompts

   Reference the integration explicitly: "Create a Linear issue for this bug" or "Query Datadog for checkout errors."

Once installed, a plugin's tools become available to agents within the same controlled boundaries as built-in tools. Skills load automatically when the agent determines they are relevant, or when you ask for domain-specific help.

Example: observability triage

Using Datadog: show 5xx rate for checkout-api over the last 2 hours.
Correlate with deploy markers and summarize likely causes before suggesting a code fix.

Example: issue tracking

Using Linear: file a bug for the empty-cart checkout 500.
Include repro steps, link to project ENG, priority high.

Marketplace vs. org policy

Registry validation

Before a plugin ships, the monorepo runs npm run check:plugins (via scripts/check-plugin-assets.mjs) to validate manifests, asset paths, and marketplace entries in plugins/.4rge-plugin/marketplace.json. Each plugin folder must include a valid .4rge-plugin/plugin.json; optional mcp.json must use the flat server-id map expected by the desktop MCP loader. Failed checks block CI — fix path references or manifest fields before merging registry changes. Published plugins are versioned directories consumed by clients from registry.4rged.ai.

Authoring plugins

Teams can publish internal or public plugins to the registry:

1. Scaffold with the create-plugin marketplace plugin.
2. Add plugin.json, optional mcp.json, skills, and hooks.
3. Register the plugin in plugins/.4rge-plugin/marketplace.json.
4. Run npm run check:plugins to validate manifests and paths.

Published plugins are versioned folders in the monorepo registry; 4RGE Desktop installs from the marketplace index.

Security reminders

• Treat each plugin like any third-party integration — review permissions before connecting MCP.
• Prefer OAuth and least-privilege API keys.
• The 1Password plugin helps validate .env files sourced from 1Password Environments before shell commands run.
• See Agent security for secrets handling and approval habits.