Your work. Your space.

Find the right Gonu tool for the next step.

Features & demosExplore Engineering Brain workflows and sample screensExploreWeb ChatFor quick questions, planning and everyday workTry nowDesktop WorkerFor local repository work with a dedicated desktop appDownloadVS Code ExtensionFor developers who already work in VS CodeSource betaGonu CLIFor terminal workflows and structured task inspectionSource betaGonu IDEFor developers exploring an integrated Gonu editorNot releasedDocs & demosPractical guides for every Gonu toolLearn
Skip to content
gonu.
Checking account…Try on web
Setup required

MCP tool connections

Connect a supported tool server, discover its tools and enable a deliberate selection.

Open MCP toolsExplore the example

WHEN IT HELPS

Put it to work.

Give a task access to an approved external capability while keeping tool selection and permissions explicit.

Before you begin

  • An authorized workspace role and a supported MCP server.
  • Operator support for the selected HTTP or isolated stdio transport.

WALK THROUGH IT

See the workflow, step by step.

Interactive example

Synthetic sample content, with simplified screens. No model call, upload, account change or paid task runs here.

  1. Open MCP tools and select the workspace. Enter the connection using the supported form and keep it disabled while reviewing the setup.

  2. Choose Discover tools. Read returned names, descriptions and schemas. Select only the tools your task requires and review read-only declarations.

  3. Save the tool selection and enable the connection when ready. During a task, review consequential tool requests and their affected resources before approving.

gonu / MCP tool connectionsSAMPLE
g.
ILLUSTRATIVE SCREEN · 1 / 3

MCP tools / Example server

NameExample documentation server
TransportSupported HTTP or isolated stdio
Initial stateDisabled
Example only · your real screen shows your own data.
Step 1 of 3

THE USEFUL RESULT

What you should leave with.

A scoped connection whose enabled tools can participate in authorized tasks.

Know the boundaries.

  • Connecting MCP does not make every server or tool compatible; unsupported schemas/transports may be unavailable.
  • Tool output is untrusted context. It cannot grant new permissions or instruct the agent to reveal secrets.

IF SOMETHING DOESN’T WORK

Discovery fails or the transport is unavailable.

Check the displayed transport/runtime requirements, URL or command configuration, and administrator policy. Never paste secret values into a support transcript.

Contact support