AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

mcp-server-builder

Use when exposing an API as an MCP server or scaffolding a new MCP server in Python or TypeScript, before hand-writing tool wrappers. Generates tools from OpenAPI with openapi_to_mcp.py and validates them with mcp_validator.py.

Original source
alirezarezvani
License
MIT
Pinned revision
e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read alirezarezvani--mcp-server-builder at revision e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 7

references/validation-checklist.md

MCP Validation Checklist

Structural Integrity

  • [ ] Tool names are unique across the manifest
  • [ ] Tool names use lowercase snake_case (3-64 chars, [a-z0-9_])
  • [ ] inputSchema.type is always "object"
  • [ ] Every required field exists in properties
  • [ ] No empty properties objects (warn if inputs truly optional)

Descriptive Quality

  • [ ] All tools include actionable descriptions (≥10 chars)
  • [ ] Descriptions start with a verb ("Create…", "Retrieve…", "Delete…")
  • [ ] Parameter descriptions explain expected values, not just types

Security & Safety

  • [ ] Auth tokens and secrets are NOT exposed in tool schemas
  • [ ] Destructive tools require explicit confirmation input parameters
  • [ ] No tool accepts arbitrary URLs or file paths without validation
  • [ ] Outbound host allowlists are explicit where applicable

Versioning & Compatibility

  • [ ] Breaking tool changes use new tool IDs (never rename in-place)
  • [ ] Additive-only changes for non-breaking updates
  • [ ] Contract changelog is maintained per release
  • [ ] Deprecated tools include sunset timeline in description

Runtime & Error Handling

  • [ ] Error responses use consistent structure (code, message, details)
  • [ ] Timeout and rate-limit behaviors are documented
  • [ ] Large response payloads are paginated or truncated