Agents and MCP

The cloud workspace MCP endpoint is https://mcp.alshival.ai/workspace/mcp/. Configure an OAuth-capable client with this URL and complete the portal consent flow; do not invent a client secret. API-key clients use a permitted Bearer credential.

Manage and revoke connections in Account → API & MCP. Tool availability and execution depend on live workspace permissions and service grants. Use workspace discovery before selecting an ID; do not assume a connection sees every workspace.

Desktop also offers a local stdio MCP through alshitasks mcp. Inspect alshitasks mcp --help for the installed version's grant and read-only options. Local agent access is distinct from cloud OAuth and from resource-log ingestion.

For application logging, use the REST or OTLP examples in this guide. No direct public Alshival chat-message REST endpoint is advertised by the current API.