marketinque — launch plan & backlink index
A 325-step SaaS launch plan with prerequisites and 975 places that give a startup a backlink (95 free and dofollow, most with the submission page on record)…
What it can do
- Whoami: Which mode this connection is in — anonymous (read-only) or a project — and what that unlocks.
- Join Waitlist: Put the founder on the marketinque waitlist for a project (the idea queue, kit, dossier, signals, nightly routine — the paid tier, opening soon). Call ONLY after the founder gave you th
- Get Plan: The launch plan. With no `node`: the outline — phases and objectives with step counts. With `node` (a phase or objective slug): every step under it, with status and whether it is unlocked. A
What data it sees
Do you need an account
No: the server works without sign-in
A 325-step SaaS launch plan with prerequisites and 975 places that give a startup a backlink (95 free and dofollow, most with the submission page on record), as tools an agent reads, acts on and records against.
Free, no key. Two prompts do the work: get-backlinks submits your product to directories (it fills the forms; you sign in and press submit) and launch-plan works the next unlocked steps. Progress lives in a marketinque.json in your repository. The thinking runs on your own Claude — the server runs no model for you.
A marketinque project (opening by waitlist) adds the console, nightly listing checks, the idea queue, a brand dossier and reported signals on the same tools, with an optional Authorization: Bearer token. How it works, step by step: https://marketinque.com/mcp-for-marketing
How to connect
How to connect marketinque — launch plan & backlink index to Claude
The server address to paste into Claude settings:
https://launch-plan--zeshut-io.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect marketinque — launch plan & backlink index to ChatGPT
The server address to paste into ChatGPT settings:
https://launch-plan--zeshut-io.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect marketinque — launch plan & backlink index to Cursor
The server address to paste into Cursor settings:
https://launch-plan--zeshut-io.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (8)
Raw names from tools/list. Only developers need these.
| whoami | Which mode this connection is in — anonymous (read-only) or a project — and what that unlocks. |
| join_waitlist | Put the founder on the marketinque waitlist for a project (the idea queue, kit, dossier, signals, nightly routine — the paid tier, opening soon). Call ONLY after the founder gave you their email and said yes in this session; `confirmed` attests that. One email, no spam; they can unsubscribe from any mail. |
| get_plan | The launch plan. With no `node`: the outline — phases and objectives with step counts. With `node` (a phase or objective slug): every step under it, with status and whether it is unlocked. Anonymous callers pass `done`/`not_applicable`/`traits`; a project uses its own. |
| get_step | One plan step: what it is, why, where it happens (target), the play it follows, what unlocks it, and how it verifies. |
| next_steps | The next unlocked, unstarted steps in tree order, and a sprint packed into `minutes`. Anonymous callers pass `done`/`not_applicable` (from marketinque.json) and `traits`; a project uses its own. |
| list_directories | Places that give a startup a backlink, one phase at a time in the order that works. Default phase bl-sprint: the 95 free, dofollow, page-scoped, graded rows. Each row carries its submission page (or where to find it) and, for a project, the listing already recorded. |
| get_directory | One directory: the numbers, the submission page and what it needs, and (project) the listing recorded for it. |
| get_submission_kit | What every directory form asks for, written once. A project returns its product profile and brand dossier plus the state of the five kit steps; anonymous callers get the five steps to draft from the product site. |