upsert_project_webhook — furrow forms MCP Tool
upsert_project_webhook
(upsert project webhook) is one of 27 tools on the
furrow forms
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call upsert_project_webhook from your client
- Claude Code furrow forms upsert_project_webhook run in your project directory
- Claude Desktop furrow forms upsert_project_webhook ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor furrow forms upsert_project_webhook ~/.cursor/mcp.json
- VS Code furrow forms upsert_project_webhook .vscode/mcp.json
- Zed furrow forms upsert_project_webhook ~/.config/zed/settings.json
- Windsurf furrow forms upsert_project_webhook ~/.codeium/windsurf/mcp_config.json
- Cline furrow forms upsert_project_webhook ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI furrow forms upsert_project_webhook ~/.gemini/settings.json
- Grok furrow forms upsert_project_webhook .mcp.json (in your project root)
- ChatGPT furrow forms upsert_project_webhook Settings → Connectors → Advanced → Developer mode
- Claude.ai furrow forms upsert_project_webhook Settings → Connectors → Add custom connector
- LangChain furrow forms upsert_project_webhook pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http furrow-forms https://api.furrowforms.com/mcp
Other tools on this server
- list_teams
- update_team
- get_account
- update_account
- create_upgrade_link
- list_clients
- get_client
- create_client
- update_client
- archive_client
- list_projects
- get_project
- list_forms
- get_form
- list_submissions
- get_submission
- get_snippet
- create_project
- update_project
- rotate_project_inbox
- archive_project
- create_form
- update_form
- archive_form
- test_webhook
- bootstrap_site
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.