Setup
Two steps to connect, one to describe your product, and the first of the three vanishes if your client can authorise for itself. About a minute in total, and you do it once. What your agent needs on its side, a browser it can drive and ideally your product's folder, is the page before this one.
1. Create a token, unless your client authorises
Claude Desktop and the Codex app have no step here at all: they run the OAuth flow from their own Connect button, and Hermes will too if you ask it to. For the clients that read a header out of a config file, open Connect your agent in the dashboard and create a token. It is shown once, because only a hash of it is stored, so copy it before you close the page.
Connect your agent2. Add SubmitMap to your client
Pick your client below and follow its few lines. Anything that speaks MCP over HTTP will work: where there is a config file the token goes in an Authorization header, and where there is a dialog you press Connect instead.
- 01In Claude Code, the terminal tool. Run this from anywhere.
claude mcp add --transport http submitmap \ https://submitmap.com/api/mcp \ --header "Authorization: Bearer smap_your_token_here"
Add --scope user to make it available in every project rather than this one. Drop the --header line to connect without an account and keep the three public tools.
- 01In the Claude app, open Customize, then Connectors.
- 02Choose Add custom connector.
- 03Fill the two boxes with these, and save.
- 04Press Connect on the connector and approve it.
- Name
- SubmitMap
- URL
- https://submitmap.com/api/mcp
No token for this one: skip that step entirely. The dialog has nowhere to paste one and does not want one, because Connect runs the OAuth flow and the app gets a key of its own. Approve it and every tool is there, including the ones that store a project and record what you sent; until you do, the connector answers with the three that need no account. The same steps work on claude.ai in a browser, since it is one setting shared by the app and the site.
- 01Open ~/.codex/config.toml, or .codex/config.toml in a project to keep it to that one.
- 02Add this at the end, with your own token, and start Codex again.
[mcp_servers.submitmap]
url = "https://submitmap.com/api/mcp"
http_headers = { "Authorization" = "Bearer smap_your_token_here" }Codex reads TOML, so this is the same server in its own shape. To keep the token out of the file, drop the http_headers line and put bearer_token_env_var = "SUBMITMAP_TOKEN" in its place, with that variable set in your shell. Run codex mcp list to see whether it connected.
- 01Open Settings, then MCP servers, then Add server.
- 02Name it, choose Streamable HTTP, give it this URL, then save and Restart.
- 03Go to Plugins, then MCPs, press Authenticate next to SubmitMap and follow the prompts.
- Name
- SubmitMap
- URL
- https://submitmap.com/api/mcp
No token for this one either, so skip that step. Do not skip the last one, though: by URL alone you get the three tools that need no account, and Authenticate runs the OAuth flow that gives the app a key of its own, after which the rest of the tools turn up with nothing to copy. The CLI tab is the one that reads a token from a file instead.
- 01Create .cursor/mcp.json in your project, or ~/.cursor/mcp.json to have it everywhere.
- 02Paste this, with your own token.
{
"mcpServers": {
"submitmap": {
"type": "http",
"url": "https://submitmap.com/api/mcp",
"headers": {
"Authorization": "Bearer smap_your_token_here"
}
}
}
}Cursor picks the file up without a restart. The green dot next to the server name means it connected.
- 01Open the command palette and run MCP: Add Server, then pick HTTP.
- 02Or write .vscode/mcp.json yourself. Note the key is "servers", not "mcpServers".
{
"servers": {
"submitmap": {
"type": "http",
"url": "https://submitmap.com/api/mcp",
"headers": {
"Authorization": "Bearer smap_your_token_here"
}
}
}
}- 01Open ~/.hermes/config.yaml.
- 02Add this under mcp_servers, with your own token.
- 03Run /reload-mcp in a chat session. There is nothing to restart.
mcp_servers:
submitmap:
url: "https://submitmap.com/api/mcp"
headers:
Authorization: "Bearer smap_your_token_here"A url on its own means streamable HTTP in Hermes, so there is no transport line to get wrong. To keep the token out of the file, drop the two header lines, put auth: oauth in their place, and run hermes mcp login submitmap; it opens a browser and waits for you to approve. A tools block with include or exclude under the server narrows what the agent sees of ours, if you would rather it saw only some of them.
- 01Any client that speaks MCP over HTTP and lets you set a header will work. Most of them take this shape.
{
"mcpServers": {
"submitmap": {
"type": "http",
"url": "https://submitmap.com/api/mcp",
"headers": {
"Authorization": "Bearer smap_your_token_here"
}
}
}
}Some clients call this transport streamable-http rather than http; the two names mean the same thing here. If yours has a UI for adding a remote server, the URL alone is enough to get the public tools.
3. Add your product
Start the session in your product's folder and ask. Your agent already has the README, the package metadata, the site copy and whatever is in your assets folder, so it can fill the project in from what it can see rather than from what you retype. Describe it yourself if you would rather, or use the dashboard form.
"Add my product to SubmitMap."
From inside the product that is the whole prompt. Somewhere else, or when the repository is not the product, say it instead:
"Add my product to SubmitMap. It is called {NAME}, it lives at
{URL}, it is a {WHAT IT DOES} for {WHO}, pricing is {FREE /
FREEMIUM / PAID}, and it is {LIVE / PRE-LAUNCH}."Then what
Ask what you qualify for, and let it submit. The guides are the prompts for both, written in the order the tools want to be called. If a tool refuses, limits and errors says what the message means.
NextGuides