Send physical mail and turn forwarded documents into context for linked postal replies.
Integrations
Agentic MCP Server Builder
Generate a minimal MCP server scaffold and contract summary from a structured tool list.
What it does
Turn a structured list of tools into a minimal MCP server scaffold and a tool contract summary. Define the server name, tool descriptions, and clear input/output schemas, then generate a file map and review baseline contract checks before adding business logic. Starter files can be materialized when dry-run mode is disabled.
When to use it
- Starting a minimal MCP server project
- Defining MCP tool input and output schemas
- Generating a starter server file layout
- Reviewing baseline tool contract checks
The skill document
Agentic MCP Server Builder
Overview
Create a minimal MCP server scaffold and contract summary from a structured tool list.
Workflow
- Define server name and tool list with descriptions.
- Generate scaffold file map and tool contract summary.
- Optionally materialize starter files when not in dry-run mode.
- Review generated contract checks before adding business logic.
Use Bundled Resources
- Run
scripts/scaffold_mcp_server.pyto generate starter artifacts. - Read
references/mcp-scaffold-guide.mdfor file layout and contract checks.
Guardrails
- Keep tool boundaries explicit and minimal.
- Include deterministic outputs and clear input/output schemas.
Questions people ask
- What information do I need to provide?
- Provide a server name and a structured tool list with descriptions. Tool boundaries should stay explicit and minimal, with clear input and output schemas.
- What does the generator produce?
- It produces a scaffold file map and a tool contract summary. When not running in dry-run mode, it can also materialize starter files.
- Does it implement the tools’ business logic?
- No. The workflow generates starter artifacts and contract checks for review before business logic is added.
Related skills
Check MCP servers and skill files for registry risk, provenance, trust, and code findings.
Publish services, find marketplace work, manage delivery, and route non-custodial crypto payments through hosted MCP.
Form an agent identity in SOUL.md, archive it, revisit its past self, and track how it changes.
Scan agent dependencies, packages, images, and filesystems for CVEs, provenance issues, and blast radius.
Research, simulate, and supervise DeFi swaps, portfolio moves, and perps with explicit execution safeguards.