Submit Map

What Submit Map MCP server does

Submit Map MCP server connects an MCP client to SubmitMap, a hosted directory of product launch platforms and startup directories. It provides structured records instead of bare links. Each record can include accepted products, disqualifying conditions, submission instructions, requirements, expected approval timing, backlink type, and other practical details.

The service supports two workflows. Unauthenticated read tools help an agent research opportunities and determine whether a product is eligible. Account tools let an agent keep a reusable project profile, map its submission materials to platform forms, plan a sequence of submissions, and track what has been sent.

How it works

The server is available at https://submitmap.com/api/mcp using streamable HTTP and protocol version 2025-06-18. There is no local process or package in this repository; requests go to the hosted endpoint.

Three tools are available without an account. search_platforms can filter the directory by query, category, pricing, link type, backlink requirements, or approval speed. get_platform returns the detailed record for one platform. qualify_project accepts a product description inline and separates platforms into currently eligible options, options that become available after specified missing information is supplied, and options that are out of reach.

Account-enabled operations use a bearer token beginning with smap_. Submit Map MCP server also advertises OAuth metadata at /.well-known/oauth-protected-resource, with client-specific OAuth instructions available in the SubmitMap documentation.

Setup and configuration

Configure the hosted HTTP endpoint in an MCP client with the following server entry:

{
  "mcpServers": {
    "submitmap": {
      "type": "http",
      "url": "https://submitmap.com/api/mcp"
    }
  }
}

No package installation or local runtime is required. Read-only research works without credentials. To use project and submission-management tools, create a token at https://submitmap.com/app/tokens and provide it as an Authorization: Bearer smap_... header. The project documentation describes the OAuth setup for clients that use that flow.

Tools and capabilities

Submit Map MCP server exposes these operations:

• Search and filter launch platforms with search_platforms.
• Retrieve eligibility rules, disqualifiers, steps, requirements, gotchas, and expected outcomes with get_platform.
• Check a product against platform requirements using qualify_project.
• Inspect the authenticated account and remaining free-tier allowance with whoami.
• Create, edit, and list stored projects with create_project, update_project, and list_projects.
• Produce a platform-specific browser submission guide with submission_playbook, including missing information, sign-in rules, mapped form values, steps, and gotchas.
• Generate a submission run order with plan_submissions.
• Record and review submission status with record_submission and list_submissions.

The playbook supports work performed in the maker's own browser; the provided material does not describe direct submission or browser-control functionality.

Limitations and notes

The hosted service divides capabilities by authentication. Searching, retrieving records, and inline qualification do not require an account, while project storage and submission tracking require an account token. The directory data is described as hand-walked rather than scraped, but the material does not specify update frequency or coverage. The repository contains registry metadata, not a locally runnable implementation, so an MCP client must be able to connect to the remote HTTP endpoint.