aanet_get_workspace — AANet MCP Tool
aanet_get_workspace
(aanet get workspace) is one of 26 tools on the
AANet
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call aanet_get_workspace from your client
- Claude Code AANet aanet_get_workspace run in your project directory
- Claude Desktop AANet aanet_get_workspace ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AANet aanet_get_workspace ~/.cursor/mcp.json
- VS Code AANet aanet_get_workspace .vscode/mcp.json
- Zed AANet aanet_get_workspace ~/.config/zed/settings.json
- Windsurf AANet aanet_get_workspace ~/.codeium/windsurf/mcp_config.json
- Cline AANet aanet_get_workspace ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AANet aanet_get_workspace ~/.gemini/settings.json
- Grok AANet aanet_get_workspace .mcp.json (in your project root)
- ChatGPT AANet aanet_get_workspace Settings → Connectors → Advanced → Developer mode
- Claude.ai AANet aanet_get_workspace Settings → Connectors → Add custom connector
- LangChain AANet aanet_get_workspace pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http aanet-mcp https://aanet.space/mcp
Other tools on this server
- aanet_create_workspace
- aanet_create_trial_workspace
- aanet_delete_workspace
- aanet_deposit
- aanet_mint_subkey
- aanet_list_subkeys
- aanet_update_subkey
- aanet_revoke_subkey
- aanet_read_file
- aanet_write_file
- aanet_append_file
- aanet_delete_file
- aanet_acquire_lock
- aanet_renew_lock
- aanet_release_lock
- aanet_get_activity
- aanet_submit_feedback
- aanet_request_refund
- aanet_get_refund_status
- aanet_send_message
- aanet_get_messages
- aanet_register_webhook
- aanet_list_webhooks
- aanet_delete_webhook
- aanet_get_webhook_deliveries
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.