Skip to main content
The hosted product MCP endpoint is https://app.agentlinkops.com/mcp. It performs operations on your AgentLinkOps workspace. Hosted access requires a pilot invitation.

​
Connect and confirm access

  1. Add that URL as a remote HTTP MCP server in your client’s server settings.
  2. Complete browser sign-in and consent when the client requests it. Choose the intended account and workspace.
  3. Refresh the client’s tool list, then call list_projects.
  4. Confirm the returned project before any import or monitoring write.
Use this first instruction:
The client’s credential store holds the OAuth grant. Keep the token there. API credentials for HTTP and CLI have their own setup.

​
Understand what you connected

The hosted tool list describes registered operations. Your scopes and project grant control access; provider and delivery settings control which work can run. Check capability status before requesting discovery. The repository context server runs locally over stdio and reads files inside its chosen repository. It needs a separate connection. Documentation search, when supplied by the docs host, searches help pages; it does not perform product operations.

​
Reconnect after a failure

If the connection has no tools, check the endpoint and HTTP transport, finish browser consent, and refresh discovery. For a 401, reconnect the account. For a 403, inspect the workspace, project grant and operation’s required scopes before requesting a new grant. Repeating consent without correcting access will not restore a forbidden operation. Once project access works, check a placement. See troubleshooting for persistent errors. Use documentation search when the task is to read instructions or schemas. Its MCP endpoint has separate read-only tools.