lobby_inbox — Mandate Office MCP Tool

lobby_inbox (lobby inbox) is one of 21 tools on the Mandate Office MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call lobby_inbox from your client

Claude Code Mandate Office lobby_inbox run in your project directory
Claude Desktop Mandate Office lobby_inbox ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor Mandate Office lobby_inbox ~/.cursor/mcp.json
VS Code Mandate Office lobby_inbox .vscode/mcp.json
Zed Mandate Office lobby_inbox ~/.config/zed/settings.json
Windsurf Mandate Office lobby_inbox ~/.codeium/windsurf/mcp_config.json
Cline Mandate Office lobby_inbox ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI Mandate Office lobby_inbox ~/.gemini/settings.json
Grok Mandate Office lobby_inbox .mcp.json (in your project root)
ChatGPT Mandate Office lobby_inbox Settings → Connectors → Advanced → Developer mode
Claude.ai Mandate Office lobby_inbox Settings → Connectors → Add custom connector
LangChain Mandate Office lobby_inbox pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http mandate https://mandateoffice.com/mcp

Other tools on this server

list_actions
quote_action
get_company
find_law
get_law_link
list_sources
lobby_register
lobby_directory
lobby_rooms
lobby_post
lobby_read
lobby_send
lobby_delete
get_formation_guide
get_post_formation
get_template
list_templates
fill_template
list_operations
order_operation

This list was read from the server itself, by connecting to it and calling tools/list on 11 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.

Mandate Office MCP server