marketinque — launch plan & backlink index

com.marketinquePublished by marketinque.comOfficial publisherv46.0.0Updated Oct 24, 2026

A 361-step SaaS launch plan and 958 backlink sources as tools an agent reads, acts on and records.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that gives an assistant a 361-step SaaS launch plan and a graded index of backlink directories to work through.

What you can do
Check the connection mode and what it unlocks, and join the project waitlist after the founder confirms by email in the session. Read the launch plan outline, drill into a phase or objective, and open a single step with its target URL, prerequisites, verification method, minutes and cost. Get the next unlocked, unstarted steps and a sprint packed into a chosen number of minutes. Browse backlink directories phase by phase, and inspect one directory's domain rating, dofollow status, price, category, submission page and sign-in requirements. Fetch the submission kit: the fields directory forms ask for, plus a project's product profile and brand dossier.
When to use it
Useful when a founder is planning and executing a SaaS launch and wants an assistant to sequence steps, pick the next actions, and work through free dofollow backlink submissions in a sensible order.
Requirements
A remote streamable HTTP endpoint; no local runtime or package. Works anonymously in a read-only free tier. A project token, sent as the Authorization header in the form Bearer plus the token, unlocks project features; projects open by waitlist and the token is minted in the project console.
Before you install
The Authorization header carries a project token, so treat it as a secret. join_waitlist submits the founder's email to a third party and should only be called after they give the email and agree in the session. Directory rows may require accounts or sign-ins, and some forms cannot be driven by an agent and must be filled by the founder.

Installation

In SourceWeft

  1. Open marketinque — launch plan & backlink index in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.marketinque%2Flaunch-plan/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "marketinque-launch-plan-backlink-index": {
      "type": "http",
      "url": "https://marketinque.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

8

whoami

Who is calling

Which mode this connection is in — anonymous (read-only) or a project — and what that unlocks.

Takes no parameters.

join_waitlist

Ask for a marketinque project

Put the founder on the marketinque waitlist for a project (the idea queue, kit, dossier, signals, nightly routine — free for now, opening by waitlist). 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.

Parametersemailrequiredconfirmedrequiredproduct_url

get_plan

The launch 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.

Parametersdonenodetraitsnot_applicable

get_step

One step in full

One plan step in full: title, detail, the target URL where it happens, the play it follows, the prerequisite slugs and whether they are met (unlocked), how it verifies (self, evidence URL or an automatic signal), minutes and cost, and founder_steps when part of the step is the founder’s own (an account, a handle): the exact page and what to do there, to hand over rather than do. Read it before working a step that next_steps or get_plan returned; the slug comes from those. Read-only; no side effects.

Parametersdoneslugrequiredtraitsnot_applicable

next_steps

What to do next

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.

Parametersdonelimittraitsminutesfree_onlycheckable_onlynot_applicable

list_directories

Directories to submit to

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.

Parameterslimitphasemin_droffsetcategoryunrecorded_only

get_directory

One directory

One directory from the index: domain rating, dofollow, price, category, the submission page URL (or where to look for it), account_required (the page redirected to a sign-in when probed — most rows want a sign-in at submit anyway), founder_fills (a form an agent cannot drive), the note from the last session that worked it, and — for a project — the outcome already recorded. Read the note before opening the page. Read-only.

Parametersslugrequired

get_submission_kit

The 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.

Takes no parameters.

Version history

5
  1. v46.0.0LatestOct 7, 2026
  2. v36.0.0Sep 23, 2026
  3. v35.0.0Sep 22, 2026
  4. v22.0.0Sep 21, 2026
  5. v21.0.0Sep 21, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.