MCP server
A remote MCP server over Streamable HTTP at https://api.outlevo.com/mcp. Each tool calls the same API route a client would, with your key: its scopes, rate limits and spend caps all apply.
Connect
Create a test key at app.outlevo.com → Developers and keep it as OUTLEVO_KEY. Then:
Claude Code:
claude mcp add --transport http outlevo https://api.outlevo.com/mcp --header "Authorization: Bearer $OUTLEVO_KEY"Cursor (.cursor/mcp.json):
{ "mcpServers": { "outlevo": { "url": "https://api.outlevo.com/mcp", "headers": { "Authorization": "Bearer ${env:OUTLEVO_KEY}" } } } }Other clients that take a JSON config:
{ "mcpServers": { "outlevo": { "type": "http", "url": "https://api.outlevo.com/mcp", "headers": { "Authorization": "Bearer ${OUTLEVO_KEY}" } } } }Tools
| Tool | What it does |
|---|---|
get_context | Read the organization's business context (approved facts), optionally one topic or a search. |
get_icp | Read the ICPs with their current approved version. Pass icp_id for its versions, or version_id for one version in full. |
list_companies | List companies with their qualification status, newest first. Filter by status, domain or your own external_id; pass next_cursor back as cursor for more. |
get_company | Read one company: status, assessments, evidence and research runs. |
list_revenue_actions | List Revenue Actions and their approval and execution status. |
get_job | Read a job started by another tool (status, result, error). |
estimate_credits | Credits an operation would cost, without running it. Free. |
qualify_company | Qualify a company against the approved ICP. Metered: returns an estimate unless confirm is true. |
research_company | Research a company (standard or deep). Metered: returns an estimate unless confirm is true. |
discover_contacts | Find decision makers at a qualified company. Metered: returns an estimate unless confirm is true. |
verify_contact | Verify a contact's email. Metered: returns an estimate unless confirm is true. |
propose_revenue_action | Propose a Revenue Action. It is only a proposal: a person or an approved policy decides, never this tool. |
ask_outlevo | Talk to the Outlevo assistant in plain language ("add acme.com and qualify it", "how is the RevOps campaign doing?"). It does the work with this key's permissions and keeps the conversation (workspace thread, or a campaign's). Returns its reply, cards (tables; confirm cards whose calls spend credits only after a person agrees), suggested answers and what changed. |
Credits are quoted first
Metered tools (qualify, research, discover and verify) answer { "status": "confirmation_required", "credit_estimate": … } and spend nothing. Called again with confirm: true, they run. With a live key, a call whose estimate is above the key's per-call maximum is refused. estimate_credits is free.
What the tools cannot do
No tool approves, launches, starts, sends or pushes. propose_revenue_action records a proposal; a person or an approved policy decides. Outlevo does the sending, within the workspace's daily limits and suppressions.
Setup for each tool: Claude Code, Cursor.