ausca_browser_session_status — Ausca MCP Tool
ausca_browser_session_status
(ausca browser session status) is one of 14 tools on the
Ausca
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call ausca_browser_session_status from your client
- Claude Code Ausca ausca_browser_session_status run in your project directory
- Claude Desktop Ausca ausca_browser_session_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Ausca ausca_browser_session_status ~/.cursor/mcp.json
- VS Code Ausca ausca_browser_session_status .vscode/mcp.json
- Zed Ausca ausca_browser_session_status ~/.config/zed/settings.json
- Windsurf Ausca ausca_browser_session_status ~/.codeium/windsurf/mcp_config.json
- Cline Ausca ausca_browser_session_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Ausca ausca_browser_session_status ~/.gemini/settings.json
- Grok Ausca ausca_browser_session_status .mcp.json (in your project root)
- ChatGPT Ausca ausca_browser_session_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Ausca ausca_browser_session_status Settings → Connectors → Add custom connector
- LangChain Ausca ausca_browser_session_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-services https://ausca.com/mcp
Other tools on this server
- ausca_agent_inbox_attachment
- ausca_agent_inbox_delete
- ausca_agent_inbox_messages
- ausca_agent_inbox_read
- ausca_agent_inbox_status
- ausca_artifact_access
- ausca_browser_session_close
- ausca_browser_session_connect
- ausca_cancel_invocation
- ausca_get_invocation
- ausca_get_offer
- ausca_prepare_invocation
- ausca_search_offers
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.