Connect Prowl to your agent in 5 steps
From signup to your first market-intelligence report. Prowl fronts 448 tools over MCP — your agent calls them like any other tool.
Prowl is an MCP server at https://prowl.chat/mcp. Point any MCP-capable agent at it with a Bearer token and it gains a market-intelligence toolset — web scraping, 60+ search engines, SEO and backlink data, ad intelligence — plus a one-call prowl_analyze that plans, runs and writes a full report.
1 — Create your account
Sign up at prowl.chat with email and password or with Google. New accounts receive $5 in starter credit, which is enough for light testing on the basic tier.
2 — Generate an API key
In the web app open MCP Home → Set up in 3 steps → Step 1 “Generate your token” and click Generate token. The key looks like prowl_ followed by 32 hex characters.
It is shown exactly once — the panel warns “This key will not be shown again.” Copy it somewhere safe before closing it. Lost a key? Generate a new one and revoke the old.
Optional hardening at creation time: allowed and denied tool categories, a daily spend limit, a total spend limit, and an IP allowlist.
3 — Connect your client
Prowl speaks Streamable HTTP at https://prowl.chat/mcp and authenticates with an Authorization: Bearer prowl_<your_key> header. Pick your client:
Cursor
Create or merge .cursor/mcp.json in the project (make sure .cursor is git-ignored), then reload Cursor:
{
"mcpServers": {
"prowl": {
"url": "https://prowl.chat/mcp",
"headers": {
"Authorization": "Bearer prowl_YOUR_KEY_HERE"
}
}
}
}
Connecting the MCP server exposes the tools but does not create the slash skill. For that, also save the skill file to .cursor/skills/prowl/SKILL.md (project) or ~/.cursor/skills/prowl/SKILL.md (global) from /mcp/skill.md.
Claude Code
claude mcp add --transport http prowl https://prowl.chat/mcp \
--header "Authorization: Bearer prowl_YOUR_KEY_HERE"
Optionally install the plugin, then restart:
claude plugin marketplace add https://github.com/PROWL-AI/prowl-skill
claude plugin install prowl@prowl
Codex
Store the token at ~/.prowl/prowl_mcp_token with chmod 600, then add to ${CODEX_HOME:-$HOME/.codex}/config.toml:
[mcp_servers.prowl]
url = "https://prowl.chat/mcp"
[mcp_servers.prowl.headers]
Authorization = "Bearer prowl_YOUR_KEY_HERE"
Any other MCP client
Add a Streamable HTTP server pointing at https://prowl.chat/mcp and send the header Authorization: Bearer prowl_YOUR_KEY_HERE. That is the whole contract — there is no SDK to install.
Prefer to let the agent wire itself up? Give it this prompt:
Set up the Prowl MCP for this project using the install skill at
https://prowl.chat/mcp/install.md — my token is prowl_YOUR_KEY.
Write the client config plus a git-ignored token file, then verify
with prowl_list_tools.
4 — Verify the connection
Ask your agent to run prowl_list_tools. It is free and returns all 448 tools grouped by category — if you see them, you are connected.
Server health needs no auth at all:
curl https://prowl.chat/mcp/health
For an end-to-end smoke test that costs nothing, call a $0 utility tool:
prowl_call_tool
tool_name: extract_domain_from_url
params: {"url": "https://www.stripe.com/pricing"}
In the web app, Step 3 “Verify connection” watches for your agent’s first tool call and has a Check now button.
5 — Run your first report, then export it
Call prowl_analyze with a query and an execution mode. Keep the same session_id across calls to preserve context.
- basic — roughly 20–100 tool calls, about 30–90 seconds. Available on the free tier.
- deep — roughly 40–300 calls, about 3–5 minutes. Requires a plan.
- max — roughly 60–400 calls, about 5–10 minutes. Requires a higher plan.
Asking for deep or max without an active subscription does not fail — the run is downgraded to basic and you get an explicit notice before any money moves.
Long runs can go asynchronous: prowl_start_session returns immediately, then poll prowl_session_status until it completes and read it with prowl_get_session.
To export, run prowl_generate_artifact (infographic, pdf or pptx) or prowl_export_report (markdown or html). Both require a prior prowl_analyze on the same session_id — they work from that session’s cached report.
Funding your wallet
The $5 starter credit covers light testing. To add more, open MCP Home → Wallet and pick a top-up pack ($10, $50 or $200) — checkout runs through Stripe and the credit lands on your extra balance. Subscriptions add a monthly credit and unlock the deep and max tiers.
Every run reserves a hold and then settles down to what it actually used: you are billed at most the hold, never more.
Frequently asked questions
Do I need a subscription to start?
No. Every new account gets $5 in starter credit and the basic tier runs unsubscribed. The deep and max tiers require an active plan — request one without a subscription and the run is downgraded to basic with an explicit notice before anything is billed.
Does discovering tools cost anything?
No. prowl_list_tools, prowl_search_tools and prowl_tool_info are free — you are only billed for tools that actually call a provider, and for reports.
How am I billed for a report?
Each run reserves a hold sized to its tier, then settles down to actual usage. You are billed at most the hold and never more, and a run that fails to produce a report releases it.
What if my API key leaks?
Revoke it from MCP Home — the connector dies on the next call. Keys can also be scoped up front: allowed and denied tool categories, daily and total spend limits, and an IP allowlist.
Where do I see what went wrong?
Call prowl_get_error_feed. A failed async run also returns a hint pointing at it, filterable by hours, source, tool, error class and severity.
How do I keep one conversation's context?
Pass the same session_id across calls. Artifact generation and report export both require a prior prowl_analyze on that same session_id.