Start with the job
Search by what you want the AI client to accomplish—not by a package name you are expected to know.
- Task-based collections
- Client compatibility badges
- Copy-ready install commands
Free MCP server directory + stack builder
Build your MCP stack without the config hunt.
For developers connecting AI clients to real tools: find free MCP servers by task, check what each one can access, and generate a copy-ready configuration in your browser.
Free email updates Unsubscribe anytime Email only
Configuration stays local
Permission summary included
Directory & builder
Choose the task. See the access. Build the config.
Search the directory, compare compatibility and permission requirements, then add only the servers you need. Your resulting configuration is generated entirely on this device.
Less guesswork, safer setup
Everything you need before you paste a command.
Package names alone do not tell you what a server touches. Launchpad puts the decision-making details beside the install path.
Understand the access
See a plain-language permission summary before adding a server to your local configuration.
- Filesystem and database scope
- Required tokens highlighted
- Local-only tools identified
Leave with valid JSON
Combine selected servers and turn your choices into a formatted configuration you can copy or download.
- Editable paths and credentials
- Multiple client formats
- No configuration upload
Three practical steps
From “I need a tool” to a usable MCP stack.
The builder keeps discovery, permission review, and configuration in one continuous workflow.
Search by task
Choose Files, Coding, Research, Data, Knowledge, or Automation. Add a client filter if you already know where the server will run.
Review permission scope
Check whether the server reads a local folder, connects to a database, opens a browser, or requires a service token.
Generate and verify
Enter your own local values, generate JSON, and review the finished file before placing it in your MCP client configuration.
MCP directory FAQ
Know what happens before you connect anything.
What is an MCP server?
An MCP server exposes tools or data through the Model Context Protocol so a compatible AI client can use them. A server may connect to local files, a database, a browser, an API, or another defined resource.
Does MCP Launchpad upload my configuration or credentials?
No. Search, stack selection, field editing, JSON generation, and file download in this builder run through client-side JavaScript. The builder does not send the configuration to a server.
Are all listed MCP servers free?
The listed server packages can be installed without paying MCP Launchpad. Some integrations connect to third-party services that may require an account, API token, or paid service plan. Check the provider’s terms before use.
Does a generated configuration guarantee compatibility?
No. The builder produces commonly used MCP configuration structures, but client requirements and server packages can change. Review the current documentation for your client and every selected server before installing or granting access.
Where should I store API tokens?
Use your client’s recommended secret-management method where available. Avoid committing tokens to Git, sharing configuration files, or granting broader permissions than the server needs.
Why should I limit filesystem and database access?
Restricting a server to the smallest necessary folder, database, or account reduces accidental exposure and limits the impact of an incorrect tool call. Start narrow and expand only when a real task requires it.
Can I use the builder without registering?
Yes. The directory and stack builder work without registration. Free email registration is only for update notifications and downloadable configuration templates.
Keep your MCP stack current—without checking every package yourself.
Get directory updates and limited configuration templates by email. The directory and browser-based builder remain free to use without an account.
Free Email only Unsubscribe anytime