Docs / MCP server
MCP server
Manage your PROlinks links, domains, tags and UTM campaigns from an AI assistant.
PROlinks has a remote Model Context Protocol (MCP) server. Connect it to an AI assistant, such as Claude Code, Claude Desktop, Cursor or VS Code. Then ask the assistant to create branded links, edit UTM campaigns or read click data. You do not need to open the dashboard.
The server uses the same data and the same permissions as your PROlinks account. It cannot do anything that you cannot do in the dashboard.
What you need
- A PROlinks plan that includes API access (Base or Pro).
- An API token from Settings > API Tokens.
- An MCP client that supports remote servers over Streamable HTTP with a custom
Authorizationheader.
The server URL
https://prolinks.pro/mcp/prolinks
Start with Getting started.
- Getting started Create an API token, connect your AI assistant and create your first link in a few minutes.
- Connect a client Configuration for Claude Code, Claude Desktop, Cursor, VS Code and other MCP clients.
- Organizations How the MCP server chooses the organization that a tool acts on.
- Tools reference Every tool that the PROlinks MCP server exposes, with its arguments.
- Limits and errors How tool calls count against your plan, and what each error message means.
- Example prompts Prompts that show what you can do with PROlinks from your AI assistant.
Are you an agent? Read this section as Markdown: /api/v1/docs/mcp