doorman_list_hooks — Doorman MCP Tool
doorman_list_hooks
(doorman list hooks) is one of 25 tools on the
Doorman
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call doorman_list_hooks from your client
- Claude Code Doorman doorman_list_hooks run in your project directory
- Claude Desktop Doorman doorman_list_hooks ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Doorman doorman_list_hooks ~/.cursor/mcp.json
- VS Code Doorman doorman_list_hooks .vscode/mcp.json
- Zed Doorman doorman_list_hooks ~/.config/zed/settings.json
- Windsurf Doorman doorman_list_hooks ~/.codeium/windsurf/mcp_config.json
- Cline Doorman doorman_list_hooks ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Doorman doorman_list_hooks ~/.gemini/settings.json
- Grok Doorman doorman_list_hooks .mcp.json (in your project root)
- ChatGPT Doorman doorman_list_hooks Settings → Connectors → Advanced → Developer mode
- Claude.ai Doorman doorman_list_hooks Settings → Connectors → Add custom connector
- LangChain Doorman doorman_list_hooks pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http doorman https://withdoorman.com/mcp
Other tools on this server
- doorman_docs
- doorman_signup
- doorman_whoami
- doorman_list_forms
- doorman_create_form
- doorman_update_form
- doorman_get_install_snippet
- doorman_inbound_setup
- doorman_test_submission
- doorman_send_test_delivery
- doorman_list_submissions
- doorman_list_workspaces
- doorman_create_workspace
- doorman_update_workspace
- doorman_client_report
- doorman_invite
- doorman_label_submission
- doorman_audit_rows
- doorman_alerts
- doorman_hubspot_status
- doorman_hubspot_map_forms
- doorman_create_hook
- doorman_delete_hook
- doorman_contact_support
This list was read from the server itself, by connecting to it and calling tools/list on 7 October 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.