Skip to content

A desktop coding agent with free access to frontier models.

TypeScript
4.6 KB
Raw Blame
---
title: "OmniRush.ai Connect as an Agent Plugin"
sidebarTitle: "Agent Plugins"
description: "Install OmniRush.ai Connect as one portable Agent Plugin, or import compatible Agent Plugins into your organization's Library."
---

[Agent Plugins](https://agent-plugins.org/) is an open package format that can
ship Agent Skills and MCP configuration together. OmniRush.ai publishes a
standards-compliant package for OmniRush.ai Connect at
[`integrations/agent-plugins/omnirush-connect`](https://github.com/omnirush-ai/omnirush-gui/tree/main/integrations/agent-plugins/omnirush-connect).

## What the OmniRush.ai package installs

The package contains:

- `plugin.json`, targeting the published Agent Plugins 1.0.0 schema for broad
  client compatibility;
- `mcp.json`, with a placeholder OmniRush.ai Connect Streamable HTTP endpoint
  (`https://replace-with-your-den-api-origin.invalid/mcp/agent`) that you
  replace with your Den API origin plus `/mcp/agent`. The reserved `.invalid`
  domain never resolves, so an unedited package fails closed;
- an `omnirush-connect` skill that teaches the agent to search for an exact
  organizational capability before executing it.

Set the endpoint in `mcp.json`, then install or copy the complete package
directory using your client's Agent Plugins workflow. The standard does not define a registry or one universal
installation command, so the last installation step depends on the client.

The package does not contain credentials or an `Authorization` header. Your
MCP client discovers OmniRush.ai OAuth from the endpoint, opens browser sign-in,
and scopes the resulting authorization grant to the selected organization.

The Agent Plugin selects the `streamable-http` transport; it does not pin a
wire-protocol revision. OmniRush.ai Connect negotiates stateless MCP 2026-07-28
with current clients while retaining its MCP 2025-11-25 compatibility path.
Existing clients can therefore continue using the same endpoint as they move
to the current MCP protocol.

## What this enables for an organization

An administrator can manage skills, shared MCP connections, and connected
services once in OmniRush.ai. Members can then install one portable OmniRush.ai
package in a compatible agent and receive only the capabilities granted to
them through their organization, teams, and individual access rules.

This separates distribution from access control:

1. the Agent Plugin tells the client how to reach OmniRush.ai;
2. OmniRush.ai determines what the signed-in member can discover;
3. `search_capabilities` returns relevant authorized capabilities;
4. `execute_capability` runs the selected capability or returns an actionable
   connection or permission state.

The result is one reusable organization capability layer across compatible
agents instead of a separate MCP and skill configuration for every client,
teammate, and machine.

## Import Agent Plugins into OmniRush.ai Library

OmniRush.ai's GitHub plugin importer recognizes the published Agent Plugins 1.0.0
schema and the schema-identical 1.1.0 working draft at a repository root or
subdirectory. It validates `plugin.json`, requires `mcp.json` to target the
same schema version, discovers only immediate `skills/<name>/SKILL.md`
entrypoints, and reads the package-root `mcp.json`. Existing 1.0.0 packages
remain valid when 1.1.0 packages are imported.

The Den import path currently supports:

- standards-compliant Agent Skills whose instructions are contained in
  `SKILL.md`;
- remote `streamable-http` MCP servers;
- legacy remote `sse` entries supported by the existing connection runtime;
- independent failure reporting, so one invalid skill or server does not hide
  valid siblings;
- Agent Plugin format and schema-version provenance on the imported Plugin.

The Den import path reports but does not install:

- local `stdio` servers, because they require a desktop execution and trust
  policy;
- remote entries with static headers, because OmniRush.ai does not yet persist or
  forward arbitrary package headers;
- additional scripts or assets referenced by a skill. The `SKILL.md`
  entrypoint is imported and the omitted assets are reported.

These limits are explicit in the import preview so an administrator cannot
mistake a partial package for a fully configured organizational Plugin.

## Authentication

Agent Plugins does not define portable OAuth fields. Do not add an OAuth object,
bearer token, or secret header to the package. OmniRush.ai Connect uses MCP
protected-resource discovery, browser authorization, PKCE, and the client's
credential store as described in the
[OmniRush.ai Connect reference](/cloud/run-in-the-cloud/cloud-mcp).