Veröffentliche Client-Produkte auf bis zu 100 Verzeichnissen mithilfe von KI-Assistenten wie Claude, ChatGPT oder Cursor.
Auch bekannt als submitator/submitator-mcp, submitator-mcp
- Stars
- 0
- Tools
- 4
- Downloads, 30 Tage
- —
- Neueste Version
- 0.1.4
- Letzter Commit
- 15. Nov. 2026
- Lizenz
- MIT
Was ist Submitator MCP?
Submitator ist ein MCP server. Veröffentliche Client-Produkte auf bis zu 100 Verzeichnissen mithilfe von KI-Assistenten wie Claude, ChatGPT oder Cursor. Er stellt 4 Tools bereit, etwa whoami, preview_launch, launch_project.
Zusammenfassung generiert aus dem README des Projekts
Über Submitator MCP server
Agenturen, die mehrere Client-Produkte verwalten, können diese auf bis zu 100 Verzeichnissen mithilfe von KI-Assistenten wie Claude, ChatGPT oder Cursor veröffentlichen. Dieser Server verbindet deinen Assistenten über einen Agency-Key mit der Submitator API, sodass du Client-Projekte direkt über ein Chat-Interface verwalten kannst. Du kannst Projekte aus einer URL erstellen, Screenshots verwalten und Listings verfolgen, während sie live gehen.
Nutzer können dies für den vollen Funktionsumfang lokal via npx ausführen, einschließlich des Hochladens lokaler Bilder und des Speicherns von PDF- oder XLSX-Reports auf der Festplatte. Alternativ steht ein Remote-Server für webbasierte Clients wie Claude.ai und ChatGPT zur Verfügung, die OAuth für die Authentifizierung nutzen. Das System unterstützt sowohl Test-Keys für kostenloses Experimentieren als auch Live-Keys für echte Einreichungen.
Spezielle Tools wie preview_launch ermöglichen es dir, einen Dry Run durchzuführen, um die Anzahl der Verzeichnisse und die Kosten zu sehen, bevor du den Prozess startest. Der Server bietet zudem Tools zur Erstellung von Client-Fortschrittsberichten und zur Verwaltung von Brand-Badges. Zur Sicherheit nutzt der Server destructive hints, um sicherzustellen, dass Assistenten um Bestätigung bitten, bevor sie Aktionen wie launch_project ausführen, die Credits verbrauchen.
Was du damit machen kannst
- 1Automatisierte Product-Directory-LaunchesStarte den Prozess, ein Client-Projekt mit einem einzigen Befehl in mehreren Verzeichnissen einzureichen.
- 2Kosten- und Reichweitenabschätzung vor dem LaunchFühre einen Dry Run durch, um zu prüfen, wie viele Verzeichnisse erreicht werden und wie hoch die Gesamtkosten sein werden.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Submitator MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenSubmitator MCP in Claude Code installieren
$ claude mcp add --env 'SUBMITATOR_API_KEY=<YOUR_SUBMITATOR_API_KEY>' submitator-mcp -- npx -y submitator-mcpSubmitator MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"submitator-mcp": {
"command": "npx",
"args": [
"-y",
"submitator-mcp"
],
"env": {
"SUBMITATOR_API_KEY": "<YOUR_SUBMITATOR_API_KEY>"
}
}
}
}Submitator MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"submitator-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"submitator-mcp"
],
"env": {
"SUBMITATOR_API_KEY": "<YOUR_SUBMITATOR_API_KEY>"
}
}
}
}Submitator MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"submitator-mcp","type":"stdio","command":"npx","args":["-y","submitator-mcp"],"env":{"SUBMITATOR_API_KEY":"<YOUR_SUBMITATOR_API_KEY>"}}'Submitator MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"submitator-mcp": {
"command": "npx",
"args": [
"-y",
"submitator-mcp"
],
"env": {
"SUBMITATOR_API_KEY": "<YOUR_SUBMITATOR_API_KEY>"
}
}
}
}Submitator MCP in Codex installieren
$ codex mcp add submitator-mcp --env 'SUBMITATOR_API_KEY=<YOUR_SUBMITATOR_API_KEY>' -- npx -y submitator-mcpSubmitator MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.submitator-mcp] command = "npx" args = ["-y", "submitator-mcp"] [mcp_servers.submitator-mcp.env] SUBMITATOR_API_KEY = "<YOUR_SUBMITATOR_API_KEY>"
Submitator MCP in Gemini CLI installieren
$ gemini mcp add -s user -e 'SUBMITATOR_API_KEY=<YOUR_SUBMITATOR_API_KEY>' submitator-mcp npx -- -y submitator-mcpSubmitator MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"submitator-mcp": {
"command": "npx",
"args": [
"-y",
"submitator-mcp"
],
"env": {
"SUBMITATOR_API_KEY": "<YOUR_SUBMITATOR_API_KEY>"
}
}
}
}Submitator MCP tools 4
Erkannt aus dem READMEwhoamipreview_launchlaunch_projectadd_directories
| whoami | — | |
| preview_launch | — | |
| launch_project | — | |
| add_directories | — |
Konfiguration
SUBMITATOR_API_KEYErforderlichSecretAgency API key from the Submitator agency console (sbm_live_ or sbm_test_)
SUBMITATOR_FILES_DIR
| Name | Beschreibung | Typ |
|---|---|---|
| SUBMITATOR_API_KEY | Agency API key from the Submitator agency console (sbm_live_ or sbm_test_) | ErforderlichSecret |
| SUBMITATOR_FILES_DIR | — |
Automatisierte Checks
Geluften am 12. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbarBestanden
- Open Source Lizenz (OSI)Bestanden
- Commit oder Release im letzten JahrBestanden
- Package-Name ähnelt keinem populären PackageBestanden
- Remote Endpoint nutzt HTTPSBestanden
- Destruktive Tools sind markiertBestanden
- Keine versteckten Anweisungen an das ModellBestanden
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenBestanden
README
Auf GitHub ansehenSubmitator MCP server
Launch your clients' products on up to 100 directories each from Claude, ChatGPT, Cursor or VS Code.
This MCP server is for agencies on Submitator's white label plan. Your assistant creates a client project from a URL, shows which directories it would reach, launches it once you agree, and follows the listings as they go live. The badge, the report and the client page carry your agency's brand. It calls the Submitator API with your agency key and does nothing the API does not.
What you need
- An agency account: app.submitator.com/agency/start.
- An API key from Developers in the agency console. With claude.ai or ChatGPT, the sign-in creates
one (see Remote server).
- A
sbm_test_key is free from the day you create the agency. It runs in test mode: projects and listings are test data, nothing is submitted, and its test launches are not bought ones. - A
sbm_live_key comes with your first purchase. Eachlaunch_projectspends one launch.
- A
Install
The package runs on your machine with npx (Node.js 20 or newer). Keep the key in your user-level
config, never in a file that lives in a repository.
Claude Code (user scope, so the key stays out of the project's .mcp.json)
claude mcp add --scope user submitator --env SUBMITATOR_API_KEY=sbm_test_... -- npx -y submitator-mcp
Cursor (~/.cursor/mcp.json, the user-level file)
{
"mcpServers": {
"submitator": {
"command": "npx",
"args": ["-y", "submitator-mcp"],
"env": { "SUBMITATOR_API_KEY": "sbm_test_..." }
}
}
}
VS Code (.vscode/mcp.json): VS Code asks for the key and keeps it out of the file.
{
"inputs": [
{ "type": "promptString", "id": "submitator-key", "description": "Submitator API key", "password": true }
],
"servers": {
"submitator": {
"type": "stdio",
"command": "npx",
"args": ["-y", "submitator-mcp"],
"env": { "SUBMITATOR_API_KEY": "${input:submitator-key}" }
}
}
}
Claude Desktop (claude_desktop_config.json): the same block as Cursor, under mcpServers. Claude
Desktop starts servers in the disk root, so add "SUBMITATOR_FILES_DIR": "/path/to/client/images" to env
if you want to upload local images.
Devin Desktop (formerly Windsurf), Cline and other MCP clients: run npx -y submitator-mcp with
SUBMITATOR_API_KEY in its environment, or use the remote server below.
Remote server
The remote server at https://mcp.submitator.com/mcp needs no install. There are two ways in:
claude.ai and ChatGPT sign in to Submitator, and other clients send an agency key in a header.
claude.ai: sign in
- In claude.ai, open Customize > Connectors, press + Add, then Add custom connector.
- Enter the name
Submitatorand the URLhttps://mcp.submitator.com/mcp, then press Continue. Check the settings it found and press Continue again. - Under Authentication pick Sign in now, keep Use Claude's published identity (Recommended) as the OAuth client, leave Request headers empty and press Add.
- Submitator's sign-in opens: log in to the agency console. The consent page names the client and its host (Claude, claude.ai). Pick Test or Live and Full or Read only, then press Allow Claude.
- In a chat, open +, then Connectors, and switch Submitator on.
This link opens the dialog of step 1 with the name and the URL filled in.
The sign-in creates a key labelled MCP: Claude on the console's Developers page. Revoke it there
to disconnect: the next call asks to sign in again. Live needs an agency that has bought launches, so a
new agency gets Test only, and test mode submits nothing.
On Team and Enterprise plans an Owner adds the connector first, under Organization settings > Connectors: Add, Custom, Web. Members then press Connect under Customize > Connectors, and each of them signs in.
ChatGPT: sign in
- In ChatGPT on the web, open Plugins (chatgpt.com/plugins), press the plus button, then Add custom MCP server.
- Enter the name
Submitatorand, under Connection, the Server URLhttps://mcp.submitator.com/mcp. - For authentication pick OAuth with a Client ID Metadata Document (CIMD), and enter no client ID or secret: Submitator's sign-in reads ChatGPT's published client document and needs no client registration.
- Review the risk warning, select I understand and want to continue, then Create as a plugin.
- Install the plugin, then in a chat type
@and pick it.
When ChatGPT sends you to Submitator's sign-in, log in to the agency console, pick Test or Live
and Full or Read only on the consent page, and allow ChatGPT. As with claude.ai, the sign-in
creates a key whose label starts with MCP: on the console's Developers page (revoke it there to
disconnect), and a new agency gets Test only.
OpenAI's documentation says ChatGPT
asks for confirmation before write actions by default and treats a tool without readOnlyHint as a
write. Here the tools that only read carry readOnlyHint: true, and every other tool false. In a
workspace, its permissions and security settings apply to adding and using custom MCP servers.
Claude Code, Cursor, VS Code and other clients: a key in a header
URL: https://mcp.submitator.com/mcp
Header: Authorization: Bearer <your key> (X-API-Key: <your key> works too)
Claude Code
claude mcp add --transport http submitator https://mcp.submitator.com/mcp \
--header "Authorization: Bearer $SUBMITATOR_API_KEY"
Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"submitator": {
"url": "https://mcp.submitator.com/mcp",
"headers": { "Authorization": "Bearer sbm_test_..." }
}
}
}
VS Code (.vscode/mcp.json): VS Code asks for the key and keeps it out of the file.
{
"inputs": [
{ "type": "promptString", "id": "submitator-key", "description": "Submitator API key", "password": true }
],
"servers": {
"submitator": {
"type": "http",
"url": "https://mcp.submitator.com/mcp",
"headers": { "Authorization": "Bearer ${input:submitator-key}" }
}
}
}
Other clients that connect over HTTP take the same URL and header.
The remote server keeps nothing between requests: it passes the key, from the header or from the
sign-in's access token, on to the Submitator API and forgets it. Files cannot be read or saved there,
so save_report_file and local image paths work only with the npx package.
Tools
| Tool | What it does |
|---|---|
whoami |
The agency and mode behind the key, its permissions, launches left and the hourly budget |
list_projects, get_project |
Find client projects; read one in full |
create_project, update_project, delete_draft |
Create a project from a URL, change its fields, delete a draft |
set_logo, add_screenshot, remove_image |
Images from a public URL, or a local file with the npx package |
preview_launch |
Free dry run of a launch or an add with the same arguments: how many directories, what is missing, the cost, plus the top and median DR of the auto pick |
find_directories, project_directories |
Search the catalog; see one project's directory choices |
launch_project |
Start submissions. Spends one launch; refuses unless confirm_selected equals the count preview_launch shows for the same arguments |
add_directories |
Reach more directories from a launched project's free allowance, with the same check |
list_listings, list_events |
Follow listings and what changed since a given time |
get_badge, verify_badge |
The badge install code for the client's site, and a check that it is there |
create_report, get_report, save_report_file |
Build a PDF or XLSX report; save it to disk with the npx package |
get_share_link, create_share_link, delete_share_link |
The client's progress page (live keys) |
advance_test_listing, set_test_launches |
Test mode helpers (test keys) |
Prompts: launch_client_project walks through a launch, and client_progress_update drafts a note for
your client that does not name Submitator.
Keys and safety
- Keep your client's approval prompt on for
launch_project,add_directoriesandupdate_projectinstead of allowing them always: a launch spends money. These three, like every tool that overwrites or deletes data or submits to directories, carrydestructiveHint: true, so clients that read the hint ask before each call. Tools that only add or check, such ascreate_project,add_screenshotandverify_badge, carryfalse. With a live key, clients that support questions to their user (MCP elicitation) also ask you before a launch or an add, and the answer never passes through the model. The remote server keeps no session, so there this question reaches only clients on MCP protocol 2026-07-28. - The
npxpackage reads the key from its environment and sends it only tohttps://api.submitator.com. - Local images are read only from
SUBMITATOR_FILES_DIR(or the folder the client starts the server in), only real PNG, JPEG, GIF or WebP files, and never through a link. Reports are saved to Downloads by default and never over an existing file; reports that include logins are not saved here. - A read-only key fits an assistant that only checks status: projects, listings, events and existing reports. Building a report or a client page link needs a key with full permissions.
- Logins and their passwords are not exposed through this server. Read them in the agency console.
- Every call shows up in Developers, Request log with a request id that starts with
mcp-. Revoke a key there at any time. - Report a vulnerability by email to vlad@submitator.com, not in a public issue (SECURITY.md).
Development
npm install
npm test # unit, contract and protocol tests
npm run build
npm run sync:openapi # refresh openapi/v1.json and src/v1.d.ts from the public contract
npm run check:pack # pack, install in an empty folder, run the stdio handshake
When the API ships a new release, npm run sync:openapi and npm test show which new operations need
a tool or a line in EXCLUDED (src/tools/index.ts).
License
MIT
Submitator MCP Fragen
Wie füge ich Submitator MCP zu Claude Code hinzu?
Führe claude mcp add --env 'SUBMITATOR_API_KEY=<YOUR_SUBMITATOR_API_KEY>' submitator-mcp -- npx -y submitator-mcp in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Submitator MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Welche Tools bietet Submitator MCP?
Er stellt 4 Tools bereit, darunter whoami, preview_launch, launch_project, add_directories.
Was ist der Unterschied zwischen sbm_test und sbm_live Keys?
Ein sbm_test_ Key ist kostenlos und läuft im Testmodus, in dem Projekte und Listings Testdaten verwenden, ohne dass echte Einreichungen erfolgen. Ein sbm_live_ Key wird für echte Launches verwendet und mit deinem ersten Kauf erworben.
Kann ich lokale Bilder in meine Projekte hochladen?
Ja, aber du musst das npx-Package anstelle des Remote-Servers verwenden, um lokale Dateipfade zu verarbeiten.
Wie verhindere ich versehentliche Ausgaben während eines Launches?
Du kannst den Client-Approval-Prompt für Tools wie launch_project aktiviert lassen. Diese enthalten einen destructive hint, um eine Bestätigung sicherzustellen, bevor Credits für einen Launch verbraucht werden.