Forward
Buy growth outcomes from inside the editor — leads, meetings, published content, ad conversions — and pay only for results that pass your own acceptance test.Read full description
joshfreelandLABSCO SUMMARY
Automatic refunds on failed jobs is the billing behaviour a credit-metered generator ought to have.
Agents retry, and generation fails for reasons that are not the caller's fault. Refunding automatically means a retry loop cannot silently drain credits — the failure costs nothing. Research being free is the other sensible split: exploration should not be metered, generation should. Both are in beta, so treat the terms as provisional.
What it is
Harbor's endpoint for their SEO content product, in beta. Their documentation counts 11 tools — research, generation single and bulk, landing pages, reworks, job status, site management and account.
What you get
- Generating SEO articles, landing pages and rewrites
- Topic research
- Site management, job status and account
Requirements
An API key. Credit-based: one article credit per generation, research costs nothing, and a failed job refunds automatically. API and MCP access are in beta.
Setup effort
Paste a URL with a key — add the endpoint to your client
USE CASES
01
Researching before writing
Topic research costs no credits, so exploring is free.
02
Producing an article
One credit per generation, refunded if the job fails.
03
Rewriting existing pages
Rewrites are part of the same surface as new articles.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- A Harbor API key (it starts hrb_live_), minted on the Devs page of your Harbor dashboard and sent as the header Authorization: Bearer followed by that key
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
ENDPOINT URL
https://outgoing-oyster-428.convex.site/mcpRequirements
- A Harbor API key (starts hrb_live_), minted on the Devs page of your Harbor dashboard and sent as the header Authorization: Bearer hrb_live_…; the claude.ai connector, which cannot send a header, takes the key in the URL instead
MCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --transport http harbor \
https://outgoing-oyster-428.convex.site/mcp \
--header "Authorization: Bearer <YOUR_TOKEN>"Claude.ai
CLAUDE.AI · URL
https://outgoing-oyster-428.convex.site/mcp/<YOUR_API_KEY>Add a custom connector with no authentication and this URL. The connector cannot send a header, so the key goes in the URL; treat that URL like a password, and revoke the key on the Devs page if it leaks.
