Yadulink / Documentation / MCP + Cursor

Connect Cursor to Yadulink signals without losing SEO linking control.

Cursor can use MCP to connect external tools and data sources to the agent context. Yadulink then becomes a source of signals, pages, and sales workflows inside the coding environment.

MCP + Cursor

Why use project configuration

A project file makes MCP context reproducible for the team. It also avoids mixing a commercial Yadulink server with personal global configuration.

MCP + Cursor

Checks before auto-run

Cursor can ask for approval before MCP tool execution. Keep that validation active until scopes, tool effects, and modified pages are fully understood.

Verified facts

What this documentation should make explicit.

Purpose

Cursor can use MCP to connect external tools and data sources to the agent context. Yadulink then becomes a source of signals, pages, and sales workflows inside the coding environment.

Workflow proof

A project file makes MCP context reproducible for the team. It also avoids mixing a commercial Yadulink server with personal global configuration.

Assistant prompt

With Yadulink MCP in Cursor, identify SEO pages or internal links to strengthen, explain the signals used, and propose a verifiable change plan.

Verification method

How to turn the guide into an operational test.

  1. 01 Recommended setup Create a project configuration in `.cursor/mcp.json` so the server stays tied to the repo.
  2. 02 Recommended setup Declare the Yadulink MCP server with the remote transport allowed by your environment.
  3. 03 Recommended setup Run OAuth authentication and restrict permissions to the diagnosis or workflow you need.