Bring Form Builder
to Pydantic AI
Learn how to connect Indy to Pydantic AI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Indy MCP Server?
Connect your Indy account to any AI agent and manage forms and records through natural conversation.
What you can do
- Form Management — List all forms, inspect configurations, create new forms, and delete unused ones
- Record Tracking — Browse all form submissions, inspect individual records with full field data
- Template Management — List and inspect form templates for reusable designs
- Group Organization — Browse form groups for organized management
- File Access — List files attached to form submissions
How it works
1. Subscribe to this server
2. Enter your Indy Access Token
3. Start managing forms from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Operations Teams — manage form submissions and track response data without the dashboard
- Project Managers — create intake forms, review submissions, and organize templates
- Developers — integrate form management into AI-driven workflows
Built-in capabilities (12)
Create a new form
Create a new webhook
Delete a form
Delete a webhook
Get account status
Get form details
Get submission details
Get user details
List all forms
List form submissions
List connected users
List active webhooks
Why Pydantic AI?
Pydantic AI validates every Indy tool response against typed schemas, catching data inconsistencies at build time. Connect 12 tools through Vinkius and switch between OpenAI, Anthropic, or Gemini without changing your integration code. full type safety, structured output guarantees, and dependency injection for testable agents.
- —
Full type safety: every MCP tool response is validated against Pydantic models, catching data inconsistencies before they reach your application
- —
Model-agnostic architecture. switch between OpenAI, Anthropic, or Gemini without changing your Indy integration code
- —
Structured output guarantee: Pydantic AI ensures tool results conform to defined schemas, eliminating runtime type errors
- —
Dependency injection system cleanly separates your Indy connection logic from agent behavior for testable, maintainable code
Indy in Pydantic AI
Indy and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Indy to Pydantic AI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Indy in Pydantic AI
The Indy MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Pydantic AI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Indy for Pydantic AI
Every tool call from Pydantic AI to the Indy MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I create new forms and manage submissions through the AI agent?
Yes. Use create_form to build new forms, list_forms to see all forms, list_records to browse submissions, and get_record to inspect individual responses with full field data. Use delete_form to remove unused forms.
Can I use templates to create forms faster?
Yes. Use list_templates to browse available form templates and get_template to inspect their structure. Templates provide reusable form designs that save time on repetitive form creation.
Can I access files attached to form submissions?
Yes. Use list_files to retrieve all files attached to form submissions. Each file includes metadata like name, size, and the record it belongs to.
How does Pydantic AI discover MCP tools?
Create an MCPServerHTTP instance with the server URL. Pydantic AI connects, discovers all tools, and generates typed Python interfaces automatically.
Does Pydantic AI validate MCP tool responses?
Yes. When you define result types as Pydantic models, every tool response is validated against the schema. Invalid data raises a clear error instead of silently corrupting your pipeline.
Can I switch LLM providers without changing MCP code?
Absolutely. Pydantic AI abstracts the model layer. your Indy MCP integration works identically with OpenAI, Anthropic, Google, or any supported provider.
MCPServerHTTP not found
Update: pip install --upgrade pydantic-ai