GWlink
Request access

Connect your agent to GWlink

GWlink includes an MCP server for agents outside the desktop application. Give this page to the coding agent you want to connect. It can find the installed server, add it to its own client and check the connection without changing your model.

Give your agent this address

https://gwlink.gwlab.cl/mcp

The instructions below are written for the agent. GWlink must already be installed on the same computer.

Instructions for the agent

The user gave you this page because they want the agent client you are running in to connect to their local GWlink installation. Complete the setup in the current client.

Scope of this request

  • You may inspect the local GWlink and Node installations and update this client's MCP configuration.
  • Preserve every existing server and setting. Add or update only the server named gwlink.
  • Use a read only call for the connection check. Do not change the model as part of setup.
  1. 01

    Find the installed MCP entry

    Test the default path for this operating system. Write the resolved absolute path into the client configuration, not an environment variable or a placeholder.

    macOS default

    /Applications/GWlink.app/Contents/Resources/resources/gwlink-agent/mcp.mjs

    If GWlink is in another Applications folder, find GWlink.app there and keep the same path below Contents.

    Windows default

    %LOCALAPPDATA%\GWlink\resources\gwlink-agent\mcp.mjs

    If GWlink was installed elsewhere, find app.exe and use resources\gwlink-agent\mcp.mjs beside it.

  2. 02

    Resolve Node

    Resolve the Node executable to an absolute path and confirm that its major version is 20 or newer. Use command -v node on macOS or (Get-Command node).Source in PowerShell on Windows.

    If Node 20 or newer is unavailable, stop and tell the user what is missing. Do not write a configuration that points to a command you did not verify.

  3. 03

    Register gwlink in this client

    Use the client's native MCP command when it has one. Otherwise merge the server into its user configuration. Use stdio transport, the absolute Node executable as command, and the absolute mcp.mjs path as its only argument.

    {
  "mcpServers": {
    "gwlink": {
      "command": "<absolute path to Node>",
      "args": ["<absolute path to gwlink-agent/mcp.mjs>"]
    }
  }
}

    The JSON below describes the registration. Adapt it to the client's actual configuration format. Do not copy the MCP file out of the installed application.

  4. 04

    Verify the connection

    1. 1.Open GWlink. If this client cannot launch desktop applications, ask the user to open it.
    2. 2.Reload the MCP configuration or restart this client if it does not reload servers automatically.
    3. 3.List the gwlink tools and confirm that read_state is present.
    4. 4.Call read_state with an empty input. This verifies the live connection without changing the model.
    5. 5.Report the configuration file or command you changed, the two resolved paths and whether the read succeeded.

    Setup is complete only after the client can call read_state against the open GWlink application.

What the connection does

  • The client starts the installed mcp.mjs process over stdio.
  • That process discovers the running GWlink instance on the same computer. No port, token or API key belongs in the client configuration.
  • GWlink must be open when tools are called. If it is closed, the MCP server returns an explicit connection error.
  • Later tool calls can operate the visible GWlink interface and change the current model. Setup itself does not authorise a model change.
Connect an external agent to GWlink