TokenPad
Building

MCP Server Config Builder

Generate a valid Model Context Protocol server configuration.

One server per line: name | command | args

133 characters2 lines0 tokensor drop a file

MCP Config BuilderExact
0Token change
Token change0no change
Input tokens0what you pasted
Output tokens0what you would send
Token cost of this result
Output tokens0
As input$0.00
× 100K requests$0.00

Everything on this page runs in your browser. Nothing you paste is transmitted, because there is no server here to transmit it to.

Result

What MCP configuration is

The Model Context Protocol lets a client connect to servers that expose tools, resources and prompts. The configuration is a JSON block naming each server, the command that starts it, and its arguments.

It is short and easy to get subtly wrong: arguments must be an array rather than a string, and a single misplaced element means the server silently fails to start.

Every server is context

Connecting a server adds its tool definitions to your context, and those are paid for on every request exactly like any other tool. A server exposing twenty tools is a substantial permanent overhead even if you use two of them.

Connect what you need. The token counter on this page is measuring the config, but the real cost is the tool surface it brings with it.

Frequently asked questions

Why must args be an array?
Because the command is spawned directly rather than through a shell. A single string is passed as one argument, which is almost never what you meant, and the failure is silent.
How should I handle secrets?
Reference an environment variable rather than writing the value into the config, since these files end up in version control. The env field here is for that indirection.

More building tools