Yadulink / Documentation / MCP + VS Code

Use Yadulink MCP in VS Code to audit pages, signals, and workflows.

VS Code can add and manage MCP servers from user or workspace configuration. For Yadulink, the goal is to give the agent sales context without opening permissions too broadly.

MCP + VS Code

Trust, logs, and disable controls

VS Code provides controls to enable, disable, inspect logs, and confirm trust for an MCP server. Keep those controls in the deployment checklist.

MCP + VS Code

Sandbox for local servers

When a local stdio server is used on macOS or Linux, sandboxing can restrict file and network access. For a remote Yadulink server, the main controls are OAuth, scopes, and logging.

Verified facts

What this documentation should make explicit.

Purpose

VS Code can add and manage MCP servers from user or workspace configuration. For Yadulink, the goal is to give the agent sales context without opening permissions too broadly.

Workflow proof

VS Code provides controls to enable, disable, inspect logs, and confirm trust for an MCP server. Keep those controls in the deployment checklist.

Assistant prompt

With Yadulink MCP in VS Code, suggest a workspace configuration, minimum scopes, trust checks, and prompts for auditing public SEO.

Verification method

How to turn the guide into an operational test.

  1. 01 VS Code setup Choose workspace configuration if the server should stay tied to the SEO or product repo.
  2. 02 VS Code setup Add the Yadulink MCP configuration through `mcp.json` or the relevant VS Code command.
  3. 03 VS Code setup Start the server, confirm trust, and review exposed tools before use.