Build forms, manage responses, and run AI analysis via the BionicForms API.
MCP (Model Context Protocol) server that exposes the BionicForms REST API as tools for Claude. Build forms, manage responses, and trigger AI analysis — all from Claude Desktop or Claude Code. Install via npm (no build step required): Then configure your MCP client (see below) with as the command. Add to in your project root: No API key yet? Use the tool — it creates an account and returns a key…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
registerNo description publishedThis tool published no description. Forge does not invent one.
list_formsNo description publishedThis tool published no description. Forge does not invent one.
create_formNo description publishedThis tool published no description. Forge does not invent one.
get_formNo description publishedThis tool published no description. Forge does not invent one.
update_formNo description publishedThis tool published no description. Forge does not invent one.
delete_formprivilegedNo description publishedThis tool published no description. Forge does not invent one.
update_form_schemaNo description publishedThis tool published no description. Forge does not invent one.
publish_formNo description publishedThis tool published no description. Forge does not invent one.
list_responsesNo description publishedThis tool published no description. Forge does not invent one.
get_responseNo description publishedThis tool published no description. Forge does not invent one.
delete_responseprivilegedNo description publishedThis tool published no description. Forge does not invent one.
list_approvalsNo description publishedThis tool published no description. Forge does not invent one.
trigger_analysisNo description publishedThis tool published no description. Forge does not invent one.
get_analysisNo description publishedThis tool published no description. Forge does not invent one.
query_analysisNo description publishedThis tool published no description. Forge does not invent one.
list_webhooksNo description publishedThis tool published no description. Forge does not invent one.
create_webhookNo description publishedThis tool published no description. Forge does not invent one.
update_webhookNo description publishedThis tool published no description. Forge does not invent one.
delete_webhookprivilegedNo description publishedThis tool published no description. Forge does not invent one.
get_accountNo description publishedThis tool published no description. Forge does not invent one.
0 of 20 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP (Model Context Protocol) server that exposes the BionicForms REST API as tools for Claude. Build forms, manage responses, and trigger AI analysis — all from Claude Desktop or Claude Code. Install via npm (no build step required): Then configure your MCP client (see below) with as the command. Add to in your project root: No API key yet? Use the tool — it creates an account and returns a key in one step. Or register at bionicforms.com and generate a key from Settings > API Keys. Variable |…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.