Marketing

marketinque.com

An MCP server that provides a founder's launch plan with step-by-step tasks, prerequisites, verification details, and next-step guidance, plus waitlist access for a marketing tool.

1 endpoint8 known toolsFirst detected September 22, 2026Last detected September 22, 2026

ENDPOINT 1

https://marketinque.com/mcp

No auth detected

MCP server metadata

Name: marketinque
Version: 22.0.0

Capabilities

tools.listChangedprompts.listChangedresources.listChanged

Server instructions

marketinque gives an agent a SaaS launch plan (326 steps in a tree with prerequisites) and a directory index (975 places that give a startup a backlink; 95 free and dofollow, most with the submission page on record) as tools. This connection is the FREE tier: read the plan and the index, and keep the founder's progress in marketinque.json in their repository (pass its done/not_applicable lists to next_steps). Project features (the idea queue, kit, dossier, signals, nightly routine) are for marketinque customers and open by waitlist; join_waitlist puts the founder on it, only with their explicit yes. Two jobs, two prompts: get-backlinks (submit the product to directories) and launch-plan (work the next unlocked steps). Run one; each says exactly what to do and what never to do in the browser: no accounts, no passwords, no CAPTCHAs, no final submit — those are the founder's.

Known tools 8

whoami

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

Inferred read-only

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

Inferred read-only

get_plan

The launch plan.

Inferred read-only

get_step

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.

Inferred read-only

next_steps

The next unlocked, unstarted steps in tree order, and a sprint packed into `minutes`.

Inferred read-only

list_directories

Places that give a startup a backlink, one phase at a time in the order that works.

Inferred read-only

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

Inferred read-only

get_submission_kit

What every directory form asks for, written once.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.marketinque]
url = "https://marketinque.com/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: marketinque
Remote MCP URL: https://marketinque.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "marketinque": {
      "url": "https://marketinque.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "marketinque": {
      "type": "http",
      "url": "https://marketinque.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "marketinque",
  "transport": "streamable-http",
  "url": "https://marketinque.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.