Plugins and MCP

Plugins give the agent tools beyond your workspace, such as looking up tickets, querying a database or reading a CRM. Olyvr supports the Model Context Protocol (MCP), so any MCP server can be a plugin.

Open Plugins from the sidebar to browse the catalog or add your own.

Add an MCP server

Local (stdio)
Remote (HTTP)

Olyvr starts the server as a program on your machine.

Field	Example
Name	`Filesystem`
Command	`npx -y @modelcontextprotocol/server-filesystem`
Arguments	`/Users/me/Projects`
Environment	`API_TOKEN=…`

The program must already be installed. For the example above, that means Node.js.

Olyvr connects to a server over streamable HTTP.

Field	Example
Name	`Tickets`
URL	`https://mcp.example.com/mcp`
Headers	`Authorization: Bearer …`
Sign-in	OAuth, if the server supports it

The URL must use http:// or https:// and can’t contain a username or password. Use headers or OAuth instead.

Add the server from Plugins, or install it from the catalog.
Click Connect. Olyvr starts or contacts the server and lists its tools. This must finish within 30 seconds.
Try a tool with Run to check it works, then use it in chat.

The agent can use the tools of every plugin that is connected, up to 80 tools per plugin. Tool calls are checked against each tool’s declared input schema, and each call times out after two minutes.

For remote servers that use OAuth, choose Sign in and complete the sign-in in your browser. Olyvr discovers the server’s sign-in settings, registers itself where the server allows it, and refreshes tokens automatically.

Some services (for example GitHub, HubSpot and Slack’s official MCP server) don’t allow automatic registration. An admin first saves the service’s client ID and secret under Settings → Admin. Until then the app says an admin must register an app before anyone can sign in.

For Salesforce, an admin first turns on the hosted MCP server (Setup → MCP Servers, platform/sobject-all) and creates an External Client App with the scopes mcp_api and refresh_token, PKCE and JWT-based access tokens turned on, and Olyvr’s callback URL. Its Consumer Key goes under Settings → Admin as the client ID, with no secret. The steps are also shown there.

Connect GitHub with a token

Open the GitHub plugin, paste a GitHub personal access token, and choose Save token and connect. This works without registering an OAuth app. Grant the token access to the repositories and operations you want to use; your organization’s token and SSO policies still apply. The token is encrypted and masked after saving. Saving the masked value keeps the existing token.

Choose Use OAuth instead to remove the saved token and return to GitHub sign-in. OAuth requires an admin to register the app under Settings → Admin.

Secrets

Environment values, headers and OAuth tokens are encrypted on disk and shown as •••• afterwards. Leave a masked value unchanged to keep it; type a new value to replace it.

Approvals

By default, Olyvr asks before running a plugin tool. Each approval covers one call with exactly the arguments shown, and expires after 10 minutes. See Approvals for the modes.

Built-in plugins

OneDrive: search and read files in a Microsoft account you connected in Memory Data Sources, without importing them first. Read-only.
Slack: search messages, read channels, DMs and threads, find people, and post. It uses the same Sign in with Slack as the Slack data source, so there is no Slack app to register. Posting always asks you first. A workspace connected before search was added asks you to sign in with Slack again to search. For Slack’s official MCP server instead, use Slack MCP (your own app), which needs an admin-registered Slack app.

Workspace MCP endpoint

Olyvr also exposes your workspace as an MCP server with two read-only tools, workspace_search and workspace_read, at /mcp on the app’s local port. It requires the app’s session token, so for now it’s only for integrations launched by Olyvr itself.