Back to VisFlow

Remote MCP

VisFlow Agent Setup

Loading configuration Open this page from the Agent Setup button in the VisFlow extension.

Step 1 · Client

Choose your agent

Only the VisFlow configuration will be changed

Step 2 · Method

Choose a setup method

Applies to Codex app, CLI, and IDE All three local Codex clients share the same MCP configuration.
Codex setup steps
    Codex configuration
    The configuration contains credentials for the current account. Sensitive values are masked on screen, while Copy still copies the complete usable configuration.

    Step 3 · Usage

    Choose how the agent should invoke VisFlow

    Choose either method
    Task wording Name VisFlow at the beginning of the task Use one explicit invocation phrase for each task. No global rules file needs to be edited.
    Method A steps
      Five explicit invocation patterns and examples
      Name “VisFlow” explicitly. Writing only “use the extension” may cause the agent to select a different extension.

      Quick troubleshooting

      A server with the same name already exists

      Delete only the existing entry named VisFlow and try again. Do not clear the entire MCP configuration or remove other extension servers.

      The command returns “command not found”

      Confirm that Codex CLI or Claude Code is installed and available on PATH. If unsure, use the graphical setup method on this page.

      Connected, but the tool count is 0

      Restart the client and begin a new conversation. If the count remains 0, verify the HTTP transport, complete URL, Authorization value, and service availability.

      defaultTarget is null

      The current configuration is not bound to this VisFlow extension device. Reopen this page from the extension and replace the old configuration with the newly generated complete URL.

      A 401 or 403 error appears

      The current sign-in credential may have expired. Sign in to VisFlow again, reopen this page from the extension, and replace the old entry with the newly generated configuration.

      The agent still selects its built-in Browser or Chrome first

      First confirm that the task begins with “Use VisFlow.” To avoid repeating this in later tasks, switch to Method B, save the current agent’s user-level global rule, restart, and begin a new conversation. Do not add MCP twice or install extra dependencies.

      A long-running task remains pending or running

      This is a short-poll status for the same task. The agent must continue querying the original commandId; it must not execute again, switch browsers, or ask whether it should keep waiting.