anvil
Server Details
Hosted MCP server for Anvil — fill & generate PDFs and run Etch e-signature packets for AI agents.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
10 toolsanvil_create_etch_packetCreate Etch e-signature packetDestructiveInspect
Create an Etch e-signature packet (documents + signers). GraphQL mutation: createEtchPacket. IMPORTANT: isDraft defaults to true (a safe draft that sends nothing). Setting isDraft=false with real signers SENDS signature-request emails to those signers. Use isTest=true while developing.
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | Optional payload data used to pre-fill the packet's documents. | |
| name | Yes | Human-readable name for the packet. | |
| files | No | Array of file/document objects (casts or uploads) to include. Passed straight through to Anvil. | |
| isTest | No | Set true to create a test packet (no legal weight, no charge). | |
| isDraft | No | Default true. When true, creates a draft and sends nothing. Set false to activate and email signers. | |
| signers | No | Array of signer objects, e.g. [{ id, name, email, signerType, routingOrder, fields }]. Passed straight through to Anvil. | |
| signatureEmailBody | No | Optional body text for the signature-request email. | |
| signatureEmailSubject | No | Optional subject line for the signature-request email. |
anvil_current_userCurrent Anvil userRead-onlyInspect
Get the authenticated Anvil user (from the API key) and the organizations they belong to (eid, name, slug). Good first call to discover org slugs/eids for other tools. GraphQL query: currentUser.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
anvil_fill_pdfFill a PDF templateDestructiveInspect
Fill an Anvil PDF template (cast) with data and return the finished PDF as base64. REST: POST /fill/{castEid}.pdf. Returns { filename, byteLength, pdfBase64 }. The data object's keys are the template's field aliases.
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | Object mapping the template's field aliases to values, e.g. { "name": "Sam", "date": "2026-07-16" }. | |
| title | No | Optional title embedded in the generated PDF metadata. | |
| cast_eid | Yes | The cast (PDF template) eid to fill (from anvil_get_cast). | |
| fontSize | No | Optional default font size for filled text. | |
| textColor | No | Optional default text color as a hex string, e.g. #333333. |
anvil_generate_etch_sign_urlGenerate Etch signing URLDestructiveInspect
Generate a one-time embedded signing URL for a specific signer in an Etch packet (for iframe/redirect signing flows). GraphQL mutation: generateEtchSignURL. Returns { url }.
| Name | Required | Description | Default |
|---|---|---|---|
| signer_eid | Yes | The signer eid (from the packet's documentGroup.signers). | |
| client_user_id | Yes | Your app's stable id for the signing user (ties the session to your user). |
anvil_generate_pdfGenerate a PDF from HTML or MarkdownDestructiveInspect
Generate a brand-new PDF from HTML or Markdown and return it as base64. REST: POST /generate-pdf. For type=html, pass data = { html, css? }. For type=markdown, pass data = [ { label, content }, ... ]. Returns { filename, byteLength, pdfBase64 }.
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | For html: { html: "<h1>Hi</h1>", css?: "..." }. For markdown: [ { label: "Section", content: "# Title\n..." }, ... ]. | |
| type | No | Source format. Default html. | html |
| title | No | Optional title embedded in the generated PDF metadata. |
anvil_get_castGet cast (PDF template)Read-onlyInspect
Fetch a cast — an Anvil PDF template — by its eid: title, version number, and whether it is a template. Use the returned eid as the cast_eid for anvil_fill_pdf. GraphQL query: cast.
| Name | Required | Description | Default |
|---|---|---|---|
| eid | Yes | The cast (PDF template) eid. |
anvil_get_etch_packetGet Etch e-signature packetRead-onlyInspect
Fetch an Etch e-signature packet by eid: its status, details URL, document group, and every signer (eid, aliasId, name, email, status, routing order). Use this to check signature progress. GraphQL query: etchPacket.
| Name | Required | Description | Default |
|---|---|---|---|
| eid | Yes | The Etch packet eid (returned by anvil_create_etch_packet). |
anvil_get_organizationGet organizationRead-onlyInspect
Fetch an Anvil organization and its PDF templates (casts) and workflows (welds). Provide either its slug or its eid (at least one is required). GraphQL query: organization.
| Name | Required | Description | Default |
|---|---|---|---|
| eid | No | Organization eid. Provide this OR slug. | |
| slug | No | Organization slug (from anvil_current_user). Provide this OR eid. |
anvil_get_weldGet weld (workflow)Read-onlyInspect
Fetch a weld — an Anvil workflow — by eid, including its forges (the individual form steps: eid, name, slug). GraphQL query: weld.
| Name | Required | Description | Default |
|---|---|---|---|
| eid | Yes | The weld (workflow) eid. |
anvil_get_weld_dataGet weld data (workflow submission)Read-onlyInspect
Fetch a weldData record — a single submission to a weld (workflow) — by eid: completion state, test flag, and creation time. GraphQL query: weldData.
| Name | Required | Description | Default |
|---|---|---|---|
| eid | Yes | The weldData (workflow submission) eid. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!