MCP Servers & Agent Integrations
Cloud logging, MCP integrations, frontend tooling, and SSH workflows for production DevTools teams.
Workspace API & MCP
The DevTools MCP server and its non-workspace tools have been retired. Its old HTTP, SSE and tool-list endpoints return 410.
Open your workspace's API & MCP app to connect. This app appears only when staff have granted the API & MCP Access service. Internal workspaces have that service by default.
The single Streamable HTTP endpoint is https://mcp.alshival.ai/workspace/mcp/. Use a scoped workspace/personal key or OAuth connection; old DevTools keys do not work here.
Your agent sees only authorized tools and operations. Staff-only tools require staff credentials and workspace access; knowing a tool's name cannot bypass authorization. Start with workspace_discover (operation=discover) and workspace_context (operation=briefing).
Connections, keys, and usage limits are all in the API & MCP app. Built-in chat uses the same server with separate signed conversation authorization.
Open API & MCP