Your files stay on your device

MCP server configuration builder

Generate MCP server discover, initialize and list results across current and legacy protocol revisions, plus client config snippets for Claude Desktop, Claude Code and VS Code.

Name the server and the manifest builds itself as you type.

This assembles the JSON a compliant server would serve; it does not run a server or check one over the network. The JSON-RPC id fields are placeholders, so swap in real request ids when you wire the outputs into tests. Rule checks cover the MCP-specific MUSTs and SHOULDs named on this page (object capability values, object-rooted inputSchema, present names and URIs, the tool name character rule), not full JSON Schema 2020-12 validation. Envelope ids, tool results and client configs are generated in this tab and stay there.

Server setup

Protocol revisionThe current revision is stateless; the older two keep the initialize handshake

Server name

Server version

Display title (optional)

InstructionsShown to clients as guidance for the model

CapabilitiesEach is sent as an object like {} or {listChanged: true}, never bare true

More settings

Tools (JSON array)

Resources (JSON array)

Resource templates (JSON array)

Prompts (JSON array)

Cache lifetime (ms)Discover and list results on the current revision only

ttlMs

Transport

Command

ArgumentsOne argument per line

EnvironmentKEY=value per line, up to 64 lines. Secrets as ${VAR}

Config key (optional)Block name in the client configs, 1 to 64 characters. Blank derives one from the server name.

Each list holds up to 200 items and 100,000 characters. Cache lifetime sits between 0 and 1,000,000,000,000 ms. Lists need the matching capability checked, or clients will never call them.

All AI tools

Was this tool useful?

MCP server configuration builder

More AI tools