SubmitMap

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.