VisFlow Agent Connector

VisFlow Agent Connector packages two things:

• A VisFlow Agent Skill that teaches agents when and how to use VisFlow.
• A VisFlow MCP connector that lets MCP-capable agents call a signed-in VisFlow browser extension through Agent Relay.

Users do not need to clone the VisFlow source repository. The package can install MCP configuration, expose the bundled skill folder, or print a generic MCP JSON block for agents that use custom configuration.

Prerequisites

• Install the VisFlow browser extension and sign in.
• Use a VisFlow build with Agent Relay enabled.
• Install Node.js 18 or newer.
• Restart the target agent after installation.

Install

Recommended one-command install:

npx -y visflow-agent-connector install --env=prod

Test/internal environment:

npx -y visflow-agent-connector install --env=test

The installer configures the integrations available on the current machine:

• Codex: installs the VisFlow Skill and MCP config.
• Cursor: installs MCP config.
• VS Code: installs MCP config into the VS Code mcp.json.
• Wiscode-compatible clients: installs VS Code-style mcp.json under the WisCode user config directory. If Wiscode uses a different config path on your machine, pass --config <path-to-mcp.json>.
• Claude Code: installs MCP config through the claude CLI when available.
• OpenCode: installs MCP config.
• OpenClaw: installs MCP config through the openclaw CLI when available.
• Other MCP clients: supported through print-mcp-json.

Install a single client instead:

npx -y visflow-agent-connector install-codex --db-type=1 --base-url=https://api.research.360.cn/api

Wiscode or other VS Code-compatible clients:

npx -y visflow-agent-connector install-wiscode --env=prod

If the client stores MCP config somewhere else:

npx -y visflow-agent-connector install-wiscode --env=prod --config /path/to/mcp.json

After restarting the agent, ask:

调用 VisFlow 总结当前页面。

For simple one-step browser actions, agents should pass concise prompts to VisFlow and relay VisFlow's final message directly instead of rewriting the result from page metadata.

Agent Skill

Print the bundled skill path:

npx -y visflow-agent-connector skill-path

Install only the skill for Codex:

npx -y visflow-agent-connector install-codex-skill

Print the SKILL.md content:

npx -y visflow-agent-connector print-skill

Install the skill into a custom skills root:

npx -y visflow-agent-connector install-skill --target ~/.codex/skills

The skill is intentionally small. It tells agents to prefer the visflow_* MCP tools, how to verify setup, and which browser actions require caution.

MCP Client Installers

Codex

npx -y visflow-agent-connector install-codex --db-type=1 --base-url=https://api.research.360.cn/api

Writes a managed block into ~/.codex/config.toml.

Cursor

npx -y visflow-agent-connector install-cursor --db-type=1 --base-url=https://api.research.360.cn/api

Writes ~/.cursor/mcp.json. Use --scope=project to write ./.cursor/mcp.json instead.

VS Code

npx -y visflow-agent-connector install-vscode --db-type=1 --base-url=https://api.research.360.cn/api

Writes the user mcp.json for VS Code. Use --scope=project to write ./.vscode/mcp.json instead.

Wiscode-Compatible Clients

npx -y visflow-agent-connector install-wiscode --db-type=1 --base-url=https://api.research.360.cn/api

This writes VS Code-style MCP configuration to the WisCode user config directory. On macOS the default path is:

~/Library/Application Support/WisCode/User/mcp.json

The config content is:

{
  "servers": {
    "visflow": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "visflow-agent-connector", "mcp"]
    }
  }
}

If Wiscode uses this mcp.json format, this is enough after restarting the client. If it uses a custom location, run the command with --config /path/to/mcp.json.

Claude Code

npx -y visflow-agent-connector install-claude-code --db-type=1 --base-url=https://api.research.360.cn/api

Uses the claude mcp add-json command. Claude Code must already be installed. Use --scope=user, --scope=project, or --scope=local as needed.

OpenCode

npx -y visflow-agent-connector install-opencode --db-type=1 --base-url=https://api.research.360.cn/api

Writes ~/.config/opencode/opencode.json. Use --scope=project to write ./opencode.json instead.

OpenClaw

npx -y visflow-agent-connector install-openclaw --db-type=1 --base-url=https://api.research.360.cn/api

Uses the openclaw mcp set command. OpenClaw must already be installed.

Other MCP Clients

For any client that accepts a standard mcpServers JSON block:

npx -y visflow-agent-connector print-mcp-json --db-type=1 --base-url=https://api.research.360.cn/api

Example output:

{
  "mcpServers": {
    "visflow": {
      "command": "npx",
      "args": ["-y", "visflow-agent-connector", "mcp"],
      "env": {
        "VISFLOW_RELAY_BASE_URL": "https://api.research.360.cn/api",
        "VISFLOW_RELAY_DB_TYPE": "1",
        "VISFLOW_RELAY_AUTO_DISCOVER_SESSION": "true"
      }
    }
  }
}

Compatibility

VisFlow Agent Connector does not hardcode a Chrome extension ID. It scans local Chrome extension storage for a signed-in VisFlow session, so it works with:

• A zip package installed through Chrome developer mode.
• The Chrome Web Store version.

If multiple VisFlow extension builds are installed, set VISFLOW_RELAY_EXTENSION_ID in the MCP environment to target a specific extension.

Security Model

The skill does not grant browser access by itself. It only teaches an agent how to use the MCP connector and what safety constraints to respect.

The connector does not store the user's access token in agent configuration. For normal local usage, it discovers the current signed-in extension session from Chrome's local extension storage. Hosted or company agent services should use a service-level Agent Relay API key on the server side instead of relying on local discovery.

The connector does not execute arbitrary shell or browser JavaScript from an agent. It sends explicit Agent Relay commands such as ai.execute to the VisFlow extension, and the extension executes through its existing AI execution module.