Skip to main content
Plugins give Onyx agents live access to external tools and services. An agent can use a plugin to read current data or to take an action, such as post a Slack reply or create a ticket. Admins manage all plugins in Admin Panel → Plugins (/admin/plugins). Users connect their accounts and set personal defaults in Plugins in the main sidebar (/app/plugins). The Admin Panel Plugins page with an MCP server, an OpenAPI plugin, and a Slack Craft App

Where things moved in Onyx 5

In Onyx 5.0, MCP servers, OpenAPI actions, and Craft Apps moved to one Plugins page. Existing servers, tools, credentials, and Craft App settings stay the same. Only the location changed. Old links open the new pages.

Plugin types

Onyx has three plugin types. Each type connects to a different kind of external system.
You can add the same service more than once. For example, add the Slack Craft App for Craft and the Slack MCP server for Chat.

Plugins compared to connectors

Connectors and plugins solve different problems.

Add a plugin

Go to Admin Panel → Plugins, click Add, then select MCP, OpenAPI, or Craft Apps. Follow the guide for the plugin type: MCP, OpenAPI, or Craft Apps. The Add menu with MCP, OpenAPI, and Craft Apps options Only full admins can add Craft Apps. The Craft Apps filter and type show only for full admins, and only when Craft is available on your plan. Users with the Manage Actions permission can add and edit MCP and OpenAPI plugins. A Group Manager can restrict an MCP server only to the groups they manage. Only full admins can change which plugins are on in default Chat for the workspace.

The Plugins page

Cards sort by status: active plugins first, then plugins with issues, then plugins that are off. Onyx-managed Craft Apps on Onyx Cloud cannot be deleted. Deleting a plugin removes it from the workspace, from every custom agent, and from every user. To keep a plugin but stop default Chat or Craft from using it, turn off its availability switch instead.

Plugin settings

Changes stay as a draft until you click Save Changes.

Availability and personal defaults

A personal default can only narrow what the admin allows. If an admin turns off Enable in default Chat, no user can turn the plugin on in default Chat. Custom agents that already use the plugin keep it, and its credentials and settings stay the same.
Default Chat selection for MCP and OpenAPI plugins is now on the Plugins page. Chat Preferences manages only built-in tools, such as Internal Search and Web Search. In Terraform, onyx_custom_tool.enabled sets the default Chat selection for an OpenAPI plugin.

Status icons

The status icon on each card shows where the plugin is available. Each segment of the icon is one surface: Main Chat, Custom agents, and Craft.

Approvals in Craft

Craft can ask a user to approve an action before it runs. Admins set the policy for each MCP tool and each Craft App action: Turn on Let users manage approval settings to let users choose a stricter or more permissive policy for actions that the admin did not disable.
Approval policies apply only in Craft. In default Chat and custom agents, an agent calls MCP and OpenAPI tools without an approval prompt. Turn off tools in Chat that must not run without review.

Next steps

MCP servers

Connect an MCP server and choose its tools.

OpenAPI plugins

Turn a REST API schema into agent tools.

Craft Apps

Let Craft act as each user in Slack, Gmail, Notion, and more.

Plugins for users

Connect accounts and set personal defaults.