Skip to main content
Hosted access requires a pilot invitation and an authorized workspace. For the recommended skill-pack setup, use the quickstart. Follow this page when adding the connection manually.

​
Connect and confirm access

  1. Add this remote HTTP MCP server in your client’s settings:
  2. Complete browser sign-in and consent. Choose your account, workspace and project access.
  3. Refresh the tool list and read list_projects, using the command-discovery example below when your client exposes exec. Review the returned project names and identifiers.
  4. Choose the project before importing links or starting monitoring.
Your client keeps its OAuth credentials. No local ledger or context server is needed. If no project appears, check the selected workspace and ask its owner to confirm access. Create a project in the app only when you intend to and have permission.

​
Reconnect after a failure

  • No tools: check the endpoint and HTTP transport, finish browser consent, then refresh the tool list.
  • 401: reconnect your account.
  • 403 AGENT_APPROVAL_REQUIRED: keep the valid token and open the returned approvalUrl. Review the client in Agent access and approve the intended workspace/project access, then retry. Opening the URL alone does not approve it.
  • 400 WORKSPACE_REQUIRED: select an already approved workspace with X-Workspace-ID.
  • Other 403 errors: ask the workspace administrator to check membership, website access and required permissions. Reconnecting does not widen access.
Once the project read succeeds, start the campaign workflow. For job or provider errors, see troubleshooting.

​
Understand what you connected

Hosted MCP exposes the same authenticated operations as the shared HTTP and CLI command catalog. Check current availability and the connected tool list before choosing a workflow. Provider settings can still prevent a registered operation from running.Two optional connections have different purposes:The Linux CLI OAuth flow uses a separate local credential store. Terminal API-key and HTTP access use a workspace key. See account access.

​
Bounded views

​
Discover commands through the default view

Maintained source provides several views of one registry. Inspect the connected endpoint’s tool list and availability for its deployed behavior; a source description does not establish which version your client has connected to. The default /mcp view lists one tool, exec. It accepts one command string per call. Inspect the operation, then call it with one JSON object:
These are params objects for MCP tools/call; your client supplies the JSON-RPC envelope. A successful read returns accessible projects in structuredContent. An empty list is valid. Check isError and the returned error before treating the response as a working connection.The same tool accepts search <words>, tools [toolset], describe <name> and schema <name> [field.path]. Use a field path when a large schema points to a nested definition. Send separate calls for separate commands; a command string containing a batch is refused. exec uses call NAME {JSON}; the terminal CLI uses agentlinkops call NAME --args '{JSON}'.Command strings are limited to 8,000 characters. Use a direct canonical MCP call, REST or the CLI for a larger atomic argument object. Keep the operation intact.

​
Choose another view when needed

Customer toolsets are monitoring, classification, evidence, discovery, baseline, competitors, internal-links, reports, workspace, notifications, disavow, lifecycle and digests. A toolset can include operations whose provider admission is off. admission, library, rank and licensed are operator-only toolsets. Ordinary authenticated catalogs hide their commands and refuse direct calls with TOOL_NOT_FOUND. Adding scopes does not reveal them; operator identity is a separate requirement. Customer catalogs leave out the webhooks toolset because hosted webhook delivery is off. The X-MCP-Readonly: true header applies the read-only guard to any view. Changing a view never widens credential scopes or project access. Direct canonical tools/call requests remain available on authenticated views within those permissions. The older search_tools, describe_tools, run_read_command and run_write_command tools remain directly callable on the default view but are unlisted.MCP list commands return concise rows by default; format: "detailed" restores all fields where the command supports it. HTTP and terminal CLI calls default to detailed rows. Ordinary successful tool-call responses include structuredContent even when tools/list omits output schemas. Task-capable asynchronous operations can return a negotiated task handle first; read the terminal task result before reporting an observation. /mcp/all?schemas=full includes the output schemas in its listing. Use each command page for its complete contract.