How to submit an MCP server to AIBase MCP

By Jonah EasePublished Last checked
AIBase's submit page is five fields and two buttons. Four of the fields are easy. The fifth, Service Configuration, asks for JSON in a shape you are unlikely to have seen, and it is why this directory takes servers that other people reach by URL and not ones that need installing[1].
What the form asks for
| Field | Notes from the page |
|---|---|
| Name | Text. |
| Type | A drop-down that starts at "Please select type". |
| URL | Your project's address. |
| MCP logo | Upload. "Recommended image size within 500kb, supporting formats jpg/jpeg/png/gif." |
| Service Configuration | A text box with a "View Example" link and placeholder JSON, shown below. |
Read from the page while signed out on [1]. Two buttons sit at the bottom: Cooperation and Submit. I did not press either, and the page does not say what Cooperation does.
The service configuration, filled in
The box's placeholder is a template with instructions in braces: enter sse or streamableHttp for the type, an English name for your server, and a service address, with an optional headers object for an authorization value and a params object for extras[1]. With the braces replaced it looks like this:
{
"type": "streamableHttp",
"config": {
"mcpServers": {
"Your Server Name": {
"type": "streamableHttp",
"url": "https://your-server.example.com/mcp",
"headers": {
"Authorization": ""
}
}
}
}
}streamableHttpis the current MCP transport. The older HTTP+SSE transport it replaced is still a choice here, and the specification calls it deprecated[4].- The same type appears twice, once at the top and once inside the server entry. Keep them equal.
- The template gives three places for a credential: a
?key=on the address in its example, anAuthorizationheader, and aparamsobject[1]. Use only what your server really needs, and think twice before pasting a live secret into any form. - A server that only runs locally, over stdio or from npm, has no address to put in the box, so this directory is not the one for it.
Before you paste it, try the address in AIBase's own debugging tool, which tests an MCP server from the browser[3].
Where the form catches people
- Leaving the template text in. Phrases such as
{Enter sse or streamableHttp}are instructions, not values, and each one has to be replaced. - A logo in the wrong format. The page lists JPG, JPEG, PNG and GIF within 500 KB. WebP and SVG are not on that list[1].
- Naming the wrong transport. The type has two choices and they are different protocols, so write the one your server speaks. The debugging tool above is a quick way to check[3].
By hand, and the sign-in
- Create or sign in to an AIBase account. The page shows a Join Now button in its header.
- Open the submit page, then fill in the name, type, URL and logo.
- Paste the service configuration, and you click Submit.
The account and the click are yours, and so is the logo file. What follows the click is not described on the page I read.
Current status,
The home page counted 121,231 services listed, which is a number the site prints about itself and not one I measured[2]. The submit form was open with the five fields above.
Sources
- AIBase MCP: Submit MCP · checked
- AIBase MCP: home page · checked
- AIBase MCP: MCP Debugging Tool · checked
- MCP specification 2025-11-25: Transports · checked
ManyCP is not affiliated with, endorsed by or sponsored by any directory, Docker, OpenAI, Anthropic or GitHub named here. Names are used to say which service a fact is about.
Or skip all of that
Or let ManyCP fill it in for you
ManyCP writes every answer and opens the right page. You send it yourself. It needs your own signed-in AIBase account.
ManyCP prepares
- The service configuration JSON
- Name, URL and logo, with a warning when the logo will be refused
You do
- Sign in
- Upload the logo file
- Click Submit