# SubmitMap [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://submitmap.com/docs/  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/submitmap

## Description
Gives an agent a directory of 366 startup, SaaS and AI launch platforms. search_platforms, get_platform and qualify_project are free and need no account, and work out which directories a product actually qualifies for and what disqualifies it. submission_playbook returns the brief for one platform's real submission form, field by field, with the traps that silently cost a run. create_project, plan_submissions, record_submission and list_submissions track a maker's own launch on the paid plan.

## Tools
Capabilities this server exposes over MCP:

- **search_platforms** — Search the SubmitMap directory of startup launch platforms and directories. Filter by free-text query, category, pricing, link type, backlink requirement, approval speed or domain rating, and with a token leave out the ones this project has already been sent to. This is the tool behind "find me a small directory I can submit to right now": it is the whole directory, so answer from it rather than from what you remember of the web. Returns summaries; call get_platform for the full record including the submission steps.
- **get_platform** — Full record for one platform: eligibility, disqualifiers, step-by-step submission instructions, requirements, gotchas and expected outcome. All of that is free, and it is what decides whether this product should be submitted here at all. Pass brief: true to also get agentPrompt, the brief for that platform's form, and agentGotchas, the traps that only bite something filling it (a placeholder that contradicts its label, a second email input belonging to a newsletter, a honeypot). The brief spends one of the account's tracked platforms, so ask for it once the maker has decided to fill this form, not while you are still choosing between platforms. For a stored project, submission_playbook returns the same brief with the maker's values already in it.
- **qualify_project** — Given a product, work out which platforms it qualifies for right now, which it could qualify for after supplying something (with the exact list of what is missing), and which are structurally out of reach. It also hands back `recommended`: the run in the order it should be worked, so the plan comes out of the directory rather than out of what you remember of the web. That order is decided by `goal` and `budget`, and when they have not been answered the response says what it assumed and carries the questions to put to the maker: ask them, call again with the answers, and store them with update_project so nobody asks twice. Needs no account: describe the product inline. Every field is optional and an unanswered field becomes a gap to fill rather than a rejection.
- **whoami** — Which SubmitMap account this token belongs to, named by its email address, which plan it is on, and what it already holds. Call it first if you are unsure whether the maker is connected, and tell them the address it reports: it is the only way either of you can tell one of their accounts from another. It does not hand you the plan's limits and you do not need them to work: plan the whole run, and a limit says so at the write it stops.
- **list_projects** — The projects on this account, each with its facts (eligibility answers) and its pack (what a submission form asks for), plus what is still missing from the pack. Call it whenever the maker says "my product" or "my project" without naming one: it is how you find out which project they mean, and every other account tool takes the id it returns.
- **create_project** — Store a product on the account. Before asking the maker anything, use what you can already see: a README, package metadata, the site's own copy and title, an assets or public folder. A maker working in their product's repository should be able to say 'add my product to SubmitMap' and get a filled-in project back, with questions only about what is genuinely not there. Fill in as much as you can, leave the rest, and come back with update_project. Facts drive what it qualifies for; the pack is what you will paste into forms later. Ask about images early: most platforms want a square logo and many want a cover, and every asset in the pack is two fields, the public address (logoUrl) and the file on the maker's machine (logoFile), because a form uploads the file and only the address can be shown back to them.
- **update_project** — Fill in or correct a stored project. Facts and pack are merged into what is there, so you can add one field at a time as the maker answers.
- **submission_playbook** — Everything needed to submit a stored project to one platform, yourself, in the maker's browser: a preflight of what is still missing, the sign-in plan (on the first submission it carries a question for the maker: hand every login back to them, or use the Google address they write out, which you then pass back as signInAs), the pack values mapped onto the fields the form asks for, the steps, the gotchas, the agentGotchas (traps in the form itself), and the call to make afterwards. Read the preflight before opening a tab. One brief is out at a time per project: ask for the next platform only after record_submission has answered this one, because until then this tool refuses the next brief and names the one still open. Do not fetch briefs ahead or in parallel. This is the tool the free plan meters: it covers the same submissions the dashboard tracks, plus any platform the account has already sent to, and past that it says so and points at the upgrade rather than answering.
- **record_submission** — Log what happened to the dashboard: the listing URL, when it was sent, when it goes live. Call it as soon as a submission lands, before you ask for the next brief, including when it is only queued for review, and including when you are not sure it landed: that is what `attempted` is for. The next brief on this project is refused until this call is made. A platform that needs the maker (a captcha, a login, a payment, a file, an address to confirm) is recorded as `planned` with a note saying what you need from them: that hands it back without claiming an outcome, and frees the run to carry on. If the live platform did not match what the brief said, put the difference in `differsFromRecord`. This costs nothing on any plan and no status costs more than another, so record what actually happened: the brief was what spent the tracked platform, and leaving the row wrong now only makes the run harder to follow.
- **plan_submissions** — Write the run order for a project: which platforms, in what sequence, and why each one is where it is. Anything already submitted to is dropped from the plan and named back to you in `alreadySubmitted`, because a plan is what is still ahead. Pass the platforms in the order they should be worked, with a short reason on each, plus a summary of the strategy. The plan appears on the maker's dashboard as a checklist that ticks itself off as submissions land. Anything already tracked is reordered rather than reset. Call it after qualify_project, using the `recommended` list it hands back, and if that response carried `questions`, put them to the maker before you plan: the order depends on the answers, and a plan written on an assumption is one they have to undo by hand. A plan costs nothing on any plan, so plan the whole run the product deserves rather than a short one sized to a guess about what the account can track.
- **list_submissions** — Where every submission for a project stands: what went out, when, what came back, and what is still waiting. This is the tool behind "check my submissions", "what did I submit", "did I ever submit to that one" and "how is my launch going", so answer those from here instead of asking the maker to remember. Start with list_projects if they have not named a project.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "submitmap": {
    "command": "npx",
    "args": ["-y","submitmap"]
  }
}
```

## Documentation

## What SubmitMap MCP server does

SubmitMap MCP server gives agents structured access to 366 startup, SaaS, and AI launch platforms. It helps determine where a product is eligible, what information or assets are missing, and which platforms should be handled first. Platform records include eligibility rules, disqualifiers, requirements, submission steps, expected outcomes, and practical gotchas.

The free, account-independent tools are `search_platforms`, `get_platform`, and `qualify_project`. Search can filter by terms such as category, pricing, link type, backlink requirements, approval speed, and domain rating. Qualification can separate immediate matches, platforms that need more information, and platforms that are structurally unsuitable.

Account-backed tools support a stored project and its launch workflow. They can save project facts and submission content, produce an ordered plan, provide a form-specific brief, record what happened, and list current submission statuses.

## How it works

Start with `search_platforms` when the goal is to find candidate directories. Use `get_platform` to inspect a specific platform before deciding whether to submit. Its optional brief includes the form-oriented prompt and agent-specific traps, so it should be requested after a platform has been chosen rather than while comparing many options.

`qualify_project` accepts product details inline and does not require an account. Missing optional answers are treated as gaps to resolve, not automatic rejection. The response can include questions for the maker and a `recommended` order. Once those questions are answered, the result can feed `plan_submissions`.

For an account workflow, `list_projects` identifies the project before other project-specific calls. `create_project` stores the product, while `update_project` merges new or corrected facts and submission-pack fields. The pack can include both public asset addresses and local files, such as a logo URL and logo file.

## Setup and configuration

No required environment variables or license information are provided in the supplied material. The account tools use a SubmitMap token. `whoami` reports the email address associated with that token, the plan, and the account’s existing contents; use it when the connected account is unclear.

A repository, package metadata, website copy, title, or public assets can provide information for `create_project`. The maker may still need to supply missing facts, images, login choices, or other submission details. Store those answers with `update_project` rather than repeatedly asking for them.

## Tools and capabilities

- Find platforms with `search_platforms` and inspect complete records with `get_platform`.
- Assess product eligibility and receive a suggested order with `qualify_project`.
- Store and maintain product data with `create_project` and `update_project`.
- Generate a submission brief with `submission_playbook`, including preflight checks, mapped field values, steps, sign-in handling, and form traps.
- Save an ordered checklist with `plan_submissions`.
- Log submitted, queued, uncertain, or maker-blocked attempts with `record_submission`.
- Review project launch status with `list_submissions`.

## Limitations and notes

SubmitMap MCP server enforces an account workflow for stored projects. Only one submission brief may be open for a project at a time; record the result before requesting the next brief. A submission that requires the maker’s login, CAPTCHA, payment, file, or confirmation can be recorded as planned with a note instead of being presented as completed.

The brief is metered according to the account plan, while project planning and submission recording do not consume the same tracked submission allowance. The brief can also spend a tracked platform, so avoid requesting briefs in advance or in parallel. If the live form differs from its record, include that difference when recording the submission.

_Full upstream README: https://allmcps.com/mcp/submitmap/readme_