Skip to main content
Glama
Forward MCP

Forward MCP

by joshfreeland

Forward MCP — get your product customers, pay per verified result

Forward is a remote MCP server your agent uses to buy growth outcomes: qualified leads, held sales meetings, published SEO content, and verified ad conversions. You pay only for results that pass your acceptance criteria — failed verification is never billed.

Listed in the official MCP registry as xyz.getforward/forward.

Connect (one line, no signup page)

# Claude Code
claude mcp add --transport http forward https://getforward.xyz/mcp

# Codex CLI (or any stdio-only client, via the mcp-remote bridge)
codex mcp add forward -- npx -y mcp-remote https://getforward.xyz/mcp
// Cursor · Windsurf · VS Code — MCP config
{ "mcpServers": { "forward": { "type": "http", "url": "https://getforward.xyz/mcp" } } }

Then just tell your agent:

"use forward to get me 20 qualified leads — CTOs at B2B SaaS companies"

The agent calls forward_signup once → gets an API key funded with $25 free starter credits. No website visit, no human signup, no OAuth. The whole purchase (brief → quote → checkout → verified results) happens inside your editor.

Related MCP server: Growaify MCP Server

Tools

Tool

What it does

forward_signup

Create an account instantly — returns api_key + $25 free credits

forward_get_catalog

Products, prices, acceptance criteria, SLAs

forward_get_quote

Free price preview (no account needed)

forward_submit_brief

Describe who you want as customers (ICP, volume, budget cap)

forward_quote

Firm quote for a brief

forward_checkout

Authorize & start delivery — prepaid credits by default, no card

forward_get_engagement

Status, spend vs. cap, results so far

forward_get_results

Verified results, each with evidence + itemized charge

forward_get_activity

Live feed of what the fleet is doing

forward_credits / forward_topup_credits

Balance / top up (x402)

Billing guarantees (machine-verifiable)

  • A charge fires only after a result passes your acceptance criteria

  • Itemized: one charge per result_id, with verification evidence attached

  • Hard budget cap enforced server-side on every payment rail

  • Idempotent (a result can never bill twice) and reversible (acceptance failure auto-refunds)

  • SLA: first verified result within the window (content 3d · leads 7d · meetings/campaigns 14d) or the engagement is free

Payment rails

credits (prepaid, default — $25 free to start) · x402 (HTTP 402 + USDC, pay-per-call) · stripe_acp (delegated token with max_charge_usd)

Use Forward in your agent framework

Ready-to-paste integrations for LangChain, the Vercel AI SDK, and OpenAI/Anthropic tool calling — see examples/. Each exposes the same four tools (forward_signup, forward_get_quote, forward_buy, forward_get_results) so an agent can get customers and pay per verified result, with $25 free credits to start.

Run the stdio server locally (optional)

This repo ships a runnable zero-dependency stdio MCP server (mcp-server.js) that talks to the hosted Forward API:

node mcp-server.js            # or: docker build -t forward-mcp . && docker run -i forward-mcp

It exposes the same tools, including self-provisioning forward_signup (the minted key is remembered for the session). The remote endpoint at https://getforward.xyz/mcp is the recommended path — no install at all.

Plain HTTP / SDKs

Everything the MCP tools do is also plain REST — OpenAPI · llms.txt · docs. Zero-dependency SDK clients for TypeScript (forward.ts) and Python (forward.py) are in this repo.

from forward import Forward
fwd = Forward.start("https://getforward.xyz")   # mints a key (+ $25 free credits)
eng = fwd.get_customers({"product": "leads", "icp": {"roles": ["CTO"]},
                         "volume": 20, "budget_cap_usd": 250})
print(fwd.results(eng["engagement_id"]))

Forward — get customers, not software. Operated by agents, built to be bought by agents. getforward.xyz

Available Tools

9 tools
forward_checkoutC

Authorize and start delivery. Pay with credits (no human), x402, or stripe_acp.

Inputs: quote_id (required), payment, webhook_url.

forward_creditsA

Get the account's prepaid credit balance.

Inputs: no named parameters.

forward_get_catalogA

List Forward's pay-per-result products, acceptance criteria, and prices.

Inputs: no named parameters.

forward_get_engagementC

Status, spend, and results-so-far for an engagement.

Inputs: engagement_id (required).

forward_get_quoteB

Price preview for a product/difficulty/volume (no commitment).

Inputs: volume (required), product (required), difficulty.

forward_get_resultsC

Collect verified results for an engagement, each with its charge.

Inputs: engagement_id (required).

forward_quoteB

Price a submitted brief. Returns quote_id, unit price, est total, ETA.

Inputs: brief_id (required).

forward_signupA

Create a Forward account instantly — returns account_id and api_key funded with $25 free starter credits. No human signup. The key is remembered for this session; suggest the user save it as FORWARD_API_KEY.

Inputs: account_name (required), ref.

forward_submit_briefC

Describe who you want as customers. Returns brief_id (+ any missing fields as needs).

Inputs: icp (required), volume (required), product (required), budget_cap_usd (required), +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: account creation, balance, catalog, quotes, brief submission, checkout, engagement status, and results. No two tools overlap in functionality.

    Naming Consistency4/5

    All tools start with 'forward_' and mostly follow a verb_noun pattern. However, 'forward_quote' and 'forward_get_quote' are slightly inconsistent (one uses direct verb, the other 'get_'), but they have different scopes (general quote vs. brief-based quote).

    Tool Count5/5

    9 tools cover the full workflow of a pay-per-result service without being excessive. Each tool addresses a necessary step in the customer acquisition process.

    Completeness4/5

    The tool set covers signup, credits, catalog, quoting, brief submission, checkout, engagement status, and results. A minor gap is the lack of operations to cancel or update an engagement or brief, but core workflows are complete.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers