Virillio/Docs

Customization

Plugins and MCP

Connect the services you use and choose the access each connection needs.

On this page

Connect a plugin

  1. Open Plugins in the sidebar.
  2. Choose an available service and read its description, requirements, and access information.
  3. Follow the connection flow and sign in to the service if requested.
  4. Review the permissions before approving the connection.
  5. Return to a session and ask for a small read-only action to confirm the connection works.

A service appearing in the catalog may still require its own account, subscription, or administrator approval. Tool availability can change with provider access.

What MCP means

Model Context Protocol, or MCP, lets a connected server expose tools and context to the agent. A server may provide read-only lookup, actions that change data, or both. Use servers whose operator and capabilities you understand.

Describe a custom connection

For a server not in the catalog, use its official connection instructions and ask Virillio to configure the supported MCP settings. This is an example of the information to supply, not executable configuration:

Connection name: Project reference
MCP URL: https://mcp.example.com/mcp
Authentication: use the server's documented sign-in flow
First check: list the tools without changing any data

Replace the example URL with your server’s real address. Do not paste credentials into the request. Review the resulting user configuration and requested permissions.

Disconnect or troubleshoot

Use the plugin’s connection controls to disconnect. If you want to revoke the underlying authorization, also remove access in the connected service’s account settings.

For sign-in errors, check which account you used and whether the service requires administrator approval. For missing tools, confirm that the connection is active and that your account has access to the requested resource.

Reviewed Suggest a correction ↗

Search documentation

Find a guide, a workflow, or an answer.