StreamVi Account MCP

StreamVi Account MCP acts on behalf of a StreamVi account and its accessible projects. Its server address is https://mcp-streamvi-account.senler.io/mcp. This is separate from project-level StreamVi MCP and the StreamVi channel, which brings broadcast chat messages into Senler.

Prepare the connection

For widget visitors, use the ready-made StreamVi Account connection in "Per lead" mode and add it to the replying agent. The connection template must support per-lead authorization and manual tokens. Adding an arbitrary URL does not replace a template-installed connection for saving user credentials.

Your website backend obtains a valid StreamVi account token and identifies the user from its authenticated session. Do not use a project token in place of an account token or give every visitor one shared token.

Pass the token from your backend

In the server request that saves user authorization, set credential_type: "bearer", auth_method: "manual" and this secret_payload:

{
  "access_token": "<STREAMVI_ACCOUNT_TOKEN>",
  "token_type": "Bearer",
  "subject_type": "account",
  "subject_user_id": 123
}

subject_user_id identifies the StreamVi user who owns the token. It is not a project_id, Senler lead ID or installed MCP ID. Your backend determines it, not the visitor's message text.

For a manual account token, scope is optional: StreamVi checks permissions on every request. Providing scope additionally limits available methods. OAuth authorization uses the granted OAuth scopes; manual-token rules do not override them.

Next, initialize the widget with the signed external ID. The server request's external_user_id and the widget's user.external_id must identify the same website visitor. The token stays on the server; the browser receives only the ID and user_hash. Updating and revoking access are covered in the same guide.

Choose a project for an action

For project operations, the agent first finds an accessible project and then passes its numeric project_id to the specific method. The text code shown in the StreamVi cabinet is not that ID. MCP can resolve a project by its external code, which must retain its original case and leading zeros.

A user ID must not substitute for a project ID. Managing an existing channel also requires the internal ID returned by channel search, not its platform ID. The agent must read the method schema and use returned identifiers. StreamVi checks account permissions independently of what the visitor asks in chat.