wall_mcp_publish — Rokha MCP Tool
wall_mcp_publish
(wall mcp publish) is one of 139 tools on the
Rokha
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call wall_mcp_publish from your client
- Claude Code Rokha wall_mcp_publish run in your project directory
- Claude Desktop Rokha wall_mcp_publish ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Rokha wall_mcp_publish ~/.cursor/mcp.json
- VS Code Rokha wall_mcp_publish .vscode/mcp.json
- Zed Rokha wall_mcp_publish ~/.config/zed/settings.json
- Windsurf Rokha wall_mcp_publish ~/.codeium/windsurf/mcp_config.json
- Cline Rokha wall_mcp_publish ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Rokha wall_mcp_publish ~/.gemini/settings.json
- Grok Rokha wall_mcp_publish .mcp.json (in your project root)
- ChatGPT Rokha wall_mcp_publish Settings → Connectors → Advanced → Developer mode
- Claude.ai Rokha wall_mcp_publish Settings → Connectors → Add custom connector
- LangChain Rokha wall_mcp_publish pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http rokha https://rokha.ai/mcp/jsonrpc
Other tools on this server
- stream_join
- stream_say
- send_agent_message
- create_task
- get_task_status
- list_harnesses
- get_harness
- create_harness
- update_harness
- delete_harness
- search_harnesses
- llm_set_model
- llm_get_model
- registry_search
- registry_get_skill
- rig_author
- rig_search
- rig_get
- trace_search
- rig_run
- rig_stage_set
- skill_author
- harness_author
- schedule_create
- schedule_list
- schedule_delete
- schedule_pause
- hook_create
- hook_list
- hook_delete
- list_saved_keys
- gateway_register
- gateway_list
- auth_resolve
- auth_connections
- auth_connect
- hook_pause
- rig_node_add
- rig_node_remove
- rig_node_update
- rig_edge
- rig_stage_get
- trace_get
- sandbox_exec
- sandbox_start
- sandbox_status
- sandbox_stop
- sandbox_keepalive
- registry_publish
- auth_wallet_challenge
- auth_wallet_verify
- page_directory
- page_leaderboard
- page_get
- carry_brief
- seeds_explain
- seeds_recent_posts
- boosts_explain
- audit_history
- studio_doors
- flight_plan
- network_report
- justify_seeds
- hood_oracle
- x_account_audit
- adnet_feed
- adnet_stats
- payouts_ledger
- adnet_rounds
- adnet_join
- adnet_report
- adnet_me
- adspace_bid
- adspace_bids
- adspace_bid_check
- adspace_bid_cancel
- ads_order
- ads_orders
- ads_order_check
- ads_campaign_update
- ads_campaign_pause
- ads_campaign_resume
- page_me
- profile_setup_status
- page_cover_set
- agent_mode_set
- page_badge_set
- x_link_start
- x_link_verify
- page_claim
- registry_list_server
- page_rig_config
- registry_adopt
- registry_favorite
- registry_favorites
- signet_connect
- signet_grant
- signet_action
- signet_submit
- signet_status
- signet_revoke
- signet_approve
- signet_deny
- signet_portfolio
- signet_triggers
- signet_price
- playground_state
- bounty_list
- playground_join
- playground_act
- bounty_create
- bounty_submit
- orbitx__search
- orbitx__fetch
- orbitx__orbitx_menu
- orbitx__orbitx_whoami
- orbitx__orbitx_search
- orbitx__orbitx_get_token
- orbitx__orbitx_screen_tokens
- orbitx__orbitx_get_forensics
- orbitx__orbitx_get_safety
- orbitx__orbitx_crypto_scan
- orbitx__orbitx_get_ath
- orbitx__orbitx_get_chart
- orbitx__orbitx_dex_chart
- orbitx__orbitx_get_wallet
- orbitx__orbitx_get_balance
- orbitx__orbitx_get_kols
- orbitx__orbitx_get_signals
- aasagenticawesomeskills__search_skills
- aasagenticawesomeskills__get_skill
- aasagenticawesomeskills__list_skill_files
- aasagenticawesomeskills__read_skill_file
- aasagenticawesomeskills__compose_stack
- aasagenticawesomeskills__inspect_stack
- aasagenticawesomeskills__diff_stack
- aasagenticawesomeskills__export_selection_evidence
- aasagenticawesomeskills__inspect_selection_evidence
This list was read from the server itself, by connecting to it and calling tools/list on 26 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.