Server Catalog
Filesystem
OfficialRead, write, and manage files and directories on the local filesystem.
GitLab
OfficialInteract with GitLab repositories, merge requests, issues, and pipelines.
BrowserTools
Capture browser screenshots, console logs, and network activity for debugging.
Puppeteer
OfficialControl headless Chrome for screenshots, PDF generation, and web automation.
Sequential Thinking
OfficialBreak down complex problems into sequential reasoning steps for better analysis.
PostgreSQL
OfficialQuery and manage PostgreSQL databases with read-only or read-write access.
Slack
OfficialSend messages, search channels, and manage Slack workspace interactions.
Everything
OfficialReference MCP server demonstrating all protocol features and capabilities.
Server Catalog
Filesystem
OfficialRead, write, and manage files and directories on the local filesystem.
GitLab
OfficialInteract with GitLab repositories, merge requests, issues, and pipelines.
BrowserTools
Capture browser screenshots, console logs, and network activity for debugging.
Puppeteer
OfficialControl headless Chrome for screenshots, PDF generation, and web automation.
Sequential Thinking
OfficialBreak down complex problems into sequential reasoning steps for better analysis.
PostgreSQL
OfficialQuery and manage PostgreSQL databases with read-only or read-write access.
Slack
OfficialSend messages, search channels, and manage Slack workspace interactions.
Everything
OfficialReference MCP server demonstrating all protocol features and capabilities.
MCP Config Generator
Build a valid MCP server configuration from a form instead of hand-writing the JSON.
What this is for
MCP server configuration is a small JSON file that is easy to get subtly wrong: a misplaced brace, an argument array where a string was expected, an environment variable in the wrong object. The client then fails to start the server and usually tells you very little about why.
This builds that file from a form, so the shape is correct by construction. You fill in the server name, command, arguments and environment, and get valid config out. Everything happens in the page.
More detail
Things that trip people up
- Arguments are a list, not a single string.
npx -y some-serveris three entries, not one. Putting the whole command in one string is the most common reason a server never starts. - The command has to be resolvable by the client's environment, which is not necessarily your shell's. An absolute path removes the guesswork when a bare command works in a terminal but not from the client.
- Environment variables belong in the server's own env object. Values there are your API keys, so treat the generated file as a secret and do not paste it into a public issue.
Sharing a config
The share button encodes the configuration into a link. Since a real config usually contains credentials, strip them before sharing: replace the value with a placeholder so the recipient can see the structure without receiving your keys. Anyone with the link can read what is in it.
Questions
Does my configuration leave the browser?
Not unless you share it. The form and the generated JSON live entirely in the page. Clicking Share uploads a copy and returns a link that anyone can open.
My server will not start. What is usually wrong?
Nine times out of ten the arguments were written as one string instead of a list, or the command is not on the path the client actually uses. Try an absolute path to the executable and split every argument into its own entry.
Where does the generated file go?
That depends on the client. Each one reads its MCP configuration from its own location, and this tool produces the JSON rather than installing it. Check your client's documentation for the path, then paste the output there.
Is it safe to put API keys in here?
The values stay in your browser while you are editing, so filling them in is fine. What is not fine is sharing that link afterwards, because the credentials travel with it. Replace them with placeholders before you share.