Willform Agent

ai.willformPublished by willform.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Deploy containers on Kubernetes with x402 billing. 9 workload types and source builds.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Willform Agent is a remote MCP server that lets an assistant deploy containers on Kubernetes, with x402 billing and nine workload types including source builds.

What you can do
Deploy containers onto Kubernetes through the assistant, choosing among nine workload types and source builds. Billing runs through x402. The manifest lists no individual tools, so the exact operations are not documented in the supplied material.
When to use it
Worth considering when you want an assistant to handle Kubernetes container deployments and source builds without wiring up your own deployment tooling, and when x402-based billing fits how you pay.
Requirements
A remote streamable HTTP endpoint at agent.willform.ai. A Willform API key (wf_sk_...) is required and sent as a bearer token in the Authorization header. No packages or environment variables are declared.
Before you install
The server requires a Willform API key in the Authorization header, so treat it as a secret. Deployments change infrastructure and billing runs through x402, which may involve spending money; confirm costs and scope before letting an assistant deploy.

Installation

In SourceWeft

  1. Open Willform Agent in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.willform%2Fwillform-agent/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "willform-agent": {
      "type": "http",
      "url": "https://agent.willform.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.