Provides forms capabilities through a typed MCP contract.
Forms MCP Server
Form builder and submissions for AI agents — create forms with typed fields, validate inputs, collect responses, analyze results. 11 tools with 10 field types and built-in validation.
What it gives an agent
A purpose-built capability behind one MCP connection.
The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.
Architecture
How Forms MCP Server fits into an agent system.
The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.
ADK-Rust agent
Chooses a capability from the reviewed tool catalog.
MCP client
Discovers schemas, sends calls, and receives typed content.
Forms MCP Server
Validates the request and owns 11 documented tool contracts.
Domain system
Keeps the API, data, credentials, and business rules behind the server.
From the project documentation
The server’s published architecture
Tool catalog
What can an agent ask Forms MCP Server to do?
Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.
11 named tools
list_formsList all forms
read onlyget_formGet form with fields
read onlycreate_formCreate a form with fields
internal writeadd_fieldAdd a field to a form
internal writepublish_formPublish form for submissions
internal writesubmit_formSubmit form with validation
internal writevalidate_submissionValidate without submitting
read onlylist_submissionsList form responses
read onlyget_submissionGet a specific response
read onlyget_analyticsResponse analytics
read onlydelete_formDelete form and submissions
destructiveGovernance
Understand the effect of every tool.
A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.
- The registry manifest declares read only, internal write, destructive tool risk classes.
MCP surface
What the current documentation declares.
MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.
Install and connect
Follow the project’s documented starting point.
Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.
cargo install mcp-formslet toolset = McpToolset::from_stdio(
"mcp-forms",
["mcp-forms"],
).await?;
let agent = LlmAgentBuilder::new("agent")
.tools(toolset.tools().await?)
.build()?;Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.
Official documentation
Continue with the project maintainers’ source of truth.
This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.
Keep exploring
More in business operations.
Source record
Release and repository metadata for this catalog entry.
- Version
- 1.0.0
- License
- Apache-2.0
- Tools
- 11
- Revision
- ff5f6905a9cf
- Updated
- May 25, 2026