Submitator MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUBMITATOR_API_KEY | Yes | Your Submitator agency API key from the Developers section of the agency console. A sbm_test_ key runs in test mode; a sbm_live_ key spends launches. Keep it in your user-level config, never in a repository file. | |
| SUBMITATOR_FILES_DIR | No | Directory from which local client images may be read (e.g. /path/to/client/images). Required for local image uploads when the client starts the server in the disk root (Claude Desktop). Defaults to the folder the client starts the server in. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | Shows the agency and mode (live or test) behind the key, its permissions, launches left and the hourly request budget. Call it first. |
| list_projectsA | Lists the agency projects, newest first. Find one by name or URL with q, or by your own external_id. |
| get_projectB | One project in full: status, what it waits for, progress counts, allowance, readiness, texts, images and the image candidates found on its site. |
| create_projectA | Creates a project for a client's product from its URL. Name, tagline and description are filled from the site in the background when left out. Costs nothing: a launch is spent only by launch_project. |
| update_projectA | Changes project fields. Send only what changes; null clears a field, and a list replaces the whole list. contact_email cannot change after launch, and after launch an edit reaches only the listings not yet sent to their directory. |
| delete_draftA | Deletes a project that was never launched. A launched project cannot be deleted. |
| set_logoA | Sets or replaces a project's logo. A URL is fetched right away (a failed fetch answers image_unreachable); with the npx package a local file inside SUBMITATOR_FILES_DIR (or the folder the server started in) works too. |
| add_screenshotA | Adds one screenshot to a project (5 at most), from a public URL or, with the npx package, a local file. Each call adds another one, so do not repeat a call that succeeded. |
| remove_imageA | Removes the logo ("logo") or one screenshot (its img_ id). A launched project keeps at least its logo and one screenshot. |
| preview_launchA | Free dry run of launch_project (or of add_directories on a launched project) with the same arguments: how many directories it would submit to, top and median DR, what is missing, what would unlock more, and what it costs. Show the numbers to the user before launching. |
| find_directoriesA | Searches the directories Submitator submits to, highest Domain Rating first, or reads one by id. Before the agency first buys launches, only the top 20 are shown. |
| project_directoriesA | Every catalog directory as seen by one project: suggested (the auto pick), open, locked (with what unlocks it), excluded or listed. Shows suggested, open and locked by default; the counts cover all. |
| launch_projectA | Starts submissions and spends one launch of the agency (a test launch with a sbm_test_ key). Call preview_launch with the same arguments first and get the user to agree; confirm_selected is the count they agreed to. With a live key, clients that can ask their user get a confirmation question too. |
| add_directoriesA | Submits a launched project to more directories from its free allowance (no launch is spent). Call preview_launch with the same arguments first and get the user to agree. An include longer than the free allowance answers allowance_exhausted; a directory already listed answers invalid_directories. |
| list_listingsA | A project's listings, one per directory, highest DR first, with status and the live link once published. Or one listing in full by its id. |
| list_eventsA | Changes to projects and listings. The feed keeps 90 days and reads oldest first, so one call scans up to 1,000 events from the cursor (or from the start) and returns the newest ones since |
| get_badgeA | The agency-branded badge some directories require on the client's site: its status, a message to forward to the client, and install code for one platform. Call without platform to see the platforms. |
| verify_badgeA | Checks the client's site for the badge now. Up to 10 checks an hour per project, so check once after the client says it is installed. |
| create_reportA | Builds a PDF or XLSX report of a project, branded for the agency. Building takes a moment: then call get_report. |
| get_reportC | Whether a report is ready, and how to get the file. |
| save_report_fileA | Downloads a ready report and saves it to a local folder (Downloads by default). Never overwrites a file. Returns the path. |
| get_share_linkC | The project's client page link (a read-only progress page in the agency's brand), with its views. |
| create_share_linkA | Gives the project's client page link. Returns the current link when there is one; replace: true issues a new link and turns the old one off. |
| delete_share_linkA | Turns the project's client page link off. Anyone holding it sees nothing afterwards. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| launch_client_project | Walks through a client's launch: create, fill, preview, confirm, launch. |
| client_progress_update | Drafts a short progress note for the agency's client, without naming Submitator. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
Most tools target clearly distinct resources and actions across projects, directories, listings, reports, badges, images, share links, and events. A few boundaries are softer, especially get_share_link versus create_share_link and find_directories versus project_directories, but the descriptions generally make the intended use clear.
The set mostly follows a predictable snake_case verb_noun convention such as create_project, get_report, delete_share_link, and list_listings. Minor deviations include whoami, the noun-only project_directories, and delete_draft naming a draft while acting on a project.
With 24 tools, the surface is heavy even for a complex submission workflow. Most tools earn their place, but the lifecycle is split into many granular operations, putting it at the upper edge of reasonable scoping.
The tool set covers the core domain well: project creation and editing, launch preview and execution, directory discovery, listings, reports, share links, badges, images, and event tracking. Minor gaps exist around managing generated reports or listings after submission, but no major workflow dead end is apparent.