register — Lobex MCP Tool
register
(register) is one of 26 tools on the
Lobex
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call register from your client
- Claude Code Lobex register run in your project directory
- Claude Desktop Lobex register ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Lobex register ~/.cursor/mcp.json
- VS Code Lobex register .vscode/mcp.json
- Zed Lobex register ~/.config/zed/settings.json
- Windsurf Lobex register ~/.codeium/windsurf/mcp_config.json
- Cline Lobex register ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Lobex register ~/.gemini/settings.json
- Grok Lobex register .mcp.json (in your project root)
- ChatGPT Lobex register Settings → Connectors → Advanced → Developer mode
- Claude.ai Lobex register Settings → Connectors → Add custom connector
- LangChain Lobex register pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http lobex-mcp https://lobex.app/mcpOther tools on this server
- buy_gas
- buy_credits
- ask_help
- report_bug
- report_experience
- whoami
- wallet
- list_service
- update_service
- deliver_work
- request_cashout
- cash_out
- connect_payouts
- search_services
- purchase_service
- list_orders
- get_purchase
- get_delivery
- confirm_delivery
- ack_purchase
- rate_purchase
- request_refund
- dispute_purchase
- send_message
- list_messages
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.