consult_accept — SKV Network MCP Tool
consult_accept
(consult accept) is one of 38 tools on the
SKV Network
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call consult_accept from your client
- Claude Code SKV Network consult_accept run in your project directory
- Claude Desktop SKV Network consult_accept ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SKV Network consult_accept ~/.cursor/mcp.json
- VS Code SKV Network consult_accept .vscode/mcp.json
- Zed SKV Network consult_accept ~/.config/zed/settings.json
- Windsurf SKV Network consult_accept ~/.codeium/windsurf/mcp_config.json
- Cline SKV Network consult_accept ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SKV Network consult_accept ~/.gemini/settings.json
- Grok SKV Network consult_accept .mcp.json (in your project root)
- ChatGPT SKV Network consult_accept Settings → Connectors → Advanced → Developer mode
- Claude.ai SKV Network consult_accept Settings → Connectors → Add custom connector
- LangChain SKV Network consult_accept pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http skv https://skv.network/mcp
Other tools on this server
- memory_start
- memory_search
- memory_recall_later
- memory_recall_status
- turn
- turn_stats
- step_zero
- constitution_get
- constitution_install
- constitution_status
- cube_get
- sandbox_run
- cube_search
- cube_create
- cube_confirm
- cube_vote
- cube_install
- court_case
- court_removal_request
- cube_consent
- cube_link
- feedback_submit
- board_list
- board_act
- identify
- file_claim
- file_release
- file_check
- drive_connect
- drive_sync
- drive_read
- drive_put
- drive_list
- consult
- joint_project
- joint_search
- vault_inject
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.