NeurionTools & context

Tools, skills & MCP

Manage Browser Use, task guidance, and external tool connections.

HydraLabs · Published

Browser Use and Computer Use

Browser Use is built into Neurion. It works with the browser panel and supports navigation, page interaction, screenshots, and approved downloads. Review its enabled state on the Plugins page before starting a browser task.

Computer Use refers to screen understanding and keyboard or pointer interaction with desktop applications. Its user-facing entry points are not exposed in the current desktop interface. Browser Use is the available interface for supported page tasks; do not assume that it can operate every native application.

A capability preference does not establish a live connection or the task’s authority. Check the actual tool state and review the requested actions.

Enable, disable, and reconnect tools

  1. Open Plugins and select the capability or connector.
  2. Review its description, connection state, and tools.
  3. Enable or disable it for subsequent tasks.
  4. For an MCP connector that needs authentication, complete its connection flow and verify that its status is connected.

Disabling a capability in use revokes that access and stops the affected task. Re-enabling it requires a fresh task setup. These preferences do not disable CyberBot’s separate internal HTTP investigation path.

Installed, enabled, authenticated, and connected are different states. A listed connector with no live tools is not a successful connection.

Understand the permission boundary

Use and import skills

Skills provide task guidance, instructions, and associated resources. Open Skills to read a skill, enable or disable it, and inspect its source before use. Use the skill’s available task action to start work with its guidance.

You can import a supported local skill folder through the Skills manager. The application creates a local copy; review the instructions, resources, and scripts before enabling imported guidance. Remove an imported skill through the manager when you no longer need it.

A skill does not create an MCP connection or grant tool access. An MCP server can provide working tools without supplying a skill. Connecting a CAD viewer, for example, does not by itself install CAD creation guidance or a geometry engine.

A disabled skill is not active guidance. Check the skill’s enabled state and the tools actually available to the task before relying on it.

Connect MCP servers deliberately

Use the MCP configuration to add a supported local command-based server or an HTTP server. Enter the server’s documented command and arguments or URL, review any environment values or headers, and complete authentication if the server requires it.

  • Use a local command only when you trust the program and its installation source.
  • Use HTTPS for remote servers. Plain HTTP is restricted to supported loopback connections.
  • Review the server’s published tools and requested access before enabling it.
  • Confirm the connected state and make a harmless read-only call before relying on the connection.
  • Keep secrets out of screenshots, source control, and conversations.

A connector configured for Code is available to Code tasks, not Chat. A server’s tools, resources, and app view are separate capabilities: a viewer is not a file generator, and a resource is not an executable tool.

Use the installed connector’s actual tool descriptions to determine what it can do. The Plugins page does not imply that every external product, tool, or marketplace is installed.