There are MCP servers for databases, deploys, email, payments, and browsers. This one is different: it gets your product customers. Forward is a remote MCP server that sells verified growth outcomes — qualified leads, held sales meetings, published SEO content, ad conversions — and your agent can buy them end to end without you leaving your editor.
Connect in one line
claude mcp add --transport http forward https://getforward.xyz/mcp
Cursor, Windsurf, and VS Code take the JSON form ({"type":"http","url":"https://getforward.xyz/mcp"}); stdio-only clients bridge with npx -y mcp-remote https://getforward.xyz/mcp.
No signup page, ever
The part that makes it genuinely agent-native: there is no account to create first. Your agent calls the forward_signup tool once and gets back an API key funded with $25 of free starter credits. From there the whole commerce loop is tools: forward_submit_brief (who you want as customers) → forward_quote (firm price) → forward_checkout (prepaid credits by default — no card) → forward_get_results (each result carries its verification evidence and an itemized charge). Tell your agent "use forward to get me 20 qualified leads" and that entire flow happens inside your session.
Why billing-by-verified-result matters for agents
Agents transact best against guarantees they can check. Forward's billing rules are machine-verifiable: charges fire only for results that pass your acceptance criteria, they are itemized one-per-result, idempotent, hard-capped at the quoted budget, and reversible. An agent can read the llms.txt, inspect the OpenAPI contract, price work with a free quote tool, and spend a bounded budget — all without a human in the loop. That is the same shape that made Vercel the deploy primitive and Supabase the database primitive. Forward is the get-customers primitive.