This guide is for LinkDR admins connecting research and ops MCP.
Before you begin
You need:
- An AI client with MCP support (Cursor, Grok, Claude, and similar)
- A LinkDR account with the admin role
- A brand, keyword, or order question to test with
Connect research MCP
In Cursor, Grok, Claude, or another MCP client, add a server with only this URL:
{
"mcpServers": {
"linkdr": {
"url": "https://linkdr.com/mcp"
}
}
}| Client | Where to paste it |
|---|---|
| Cursor | Settings → MCP → New MCP server |
| Grok | Connectors → custom MCP → URL |
| Claude | Custom connector → URL |
Do not add an Authorization header. The client should see 401, open a browser, and take you through LinkDR sign-in and Allow.
When that succeeds, try:
Call get_domains with domains: ["genppt.com"] and tell me what you got.
If you see a miss, we do not have that host. Try a keyword next, or fetch keyword fan-out.
Running the app locally? Use http://localhost:3000/mcp instead.
How sign-in works: Auth.
Attach a research or ops skill
MCP gives the agent tools. A skill tells it the order to call them.
- Keyword fan-out for brand → SERP → listicles and creators
- YouTube outreach when you only care about ranking videos
- Ops orders for fulfillment status from the database
Fetch the skill file at /docs/admin/skills/<name>/SKILL.md in the same chat as the MCP connection so the agent does not improvise a crawl of the live web.
Next steps
- Connect MCP if you want the tool catalog before a skill.
- Tools for arguments and empty-result behavior.
- Troubleshooting if sign-in never opens or you get 403.