The MCP server
A hosted MCP server at mcp.rii.link that lets agents mint, route, and read links. OAuth is recommended for interactive agents; existing workspace keys remain available for headless automation. Nothing to install and nothing to version.
Connect with OAuth
https://mcp.rii.link/mcpChoose OAuth when your client prompts. The consent screen shows the workspace, callback host and requested read/write access. Settings → Connections then shows the agent, scopes and last use, with immediate disconnect.
Connect Claude
Settings → ConnectorsOn claude.ai and Claude Desktop, add a custom connector with the endpoint above. Claude Code takes the same hosted server in one line and opens the OAuth flow when authentication is required.
Connect Cursor, VS Code & the rest
mcp.jsonAny current client that speaks Streamable HTTP takes the same URL. Cursor supports OAuth for remote servers; project configuration lives in .cursor/mcp.json and global configuration in ~/.cursor/mcp.json.
Use an API key for automation
Dashboard → Settings → API keysHeadless clients can still send the same Bearer keys as /v1 and inherit the key’s workspace, environment and scopes — a read-only key yields a read-only agent. Keep the key in an environment variable, never in a repository.
Configure API-key headers
mcp.jsonFor non-interactive Cursor or VS Code setups, add an Authorization header. Use a global or machine-managed configuration so the credential is not committed with a project.
Let the agent route
tools/listTool names mirror the resources in this reference — create_link, list_links, update_link, delete_link, list_domains, render_qr, link_stats. Ask for a link and watch the call; errors surface with the same stable codes as the REST envelope.