Metadata-Version: 2.4
Name: qonoro-mcp
Version: 0.2.0
Summary: MCP server exposing Qonoro's x402 intelligence agents as tools for any MCP-compatible AI agent client.
Project-URL: Homepage, https://qonoro.ai
Project-URL: Repository, https://github.com/QonoroAI/qonoro-mcp-server
Author: Qonoro
License: MIT
Keywords: agents,intelligence,mcp,qonoro,x402
Requires-Python: >=3.10
Requires-Dist: httpx>=0.28.1
Requires-Dist: mcp>=1.0.0
Requires-Dist: x402[mcp]>=2.12.0
Provides-Extra: dev
Requires-Dist: pytest-asyncio>=0.21.0; extra == 'dev'
Requires-Dist: pytest>=7.0.0; extra == 'dev'
Description-Content-Type: text/markdown

# qonoro-mcp-server

MCP (Model Context Protocol) server that exposes Qonoro's production x402
intelligence agents as tools, so any MCP-compatible AI agent client can
discover and call them directly -- no custom HTTP/x402 client code needed.

This server is a thin, stateless protocol bridge. It contains no business
logic and no payment validation of its own: every call is forwarded to the
real `https://api.qonoro.ai` endpoint, and Qonoro's existing production
`payment_guard` validates and settles payment exactly as it does for any
direct HTTP/Bazaar caller today.

## Tools exposed

| Tool | Qonoro endpoint | Price |
|---|---|---|
| `qonoro_company_enrich` | `POST /v1/company/enrich` | $0.25 USDC |
| `qonoro_company_research` | `POST /v1/company/research` | $2.00 USDC |
| `qonoro_competitors_analyze` | `POST /v1/competitors/analyze` | $0.50 USDC |
| `qonoro_sales_signals_find` | `POST /v1/sales-signals/find` | $0.75 USDC |
| `qonoro_person_enrich` | `POST /v1/person/enrich` | $1.25 USDC |
| `qonoro_revenue_qualify` | `POST /v1/revenue/qualify-lead` | $0.75 USDC |
| `qonoro_intent_signals_find` | `POST /v1/intent-signals/find` | $0.75 USDC |

## How payment works

1. Call the tool with your normal arguments.
2. If the tool result contains `"payment_required": true`, it includes the
   exact price, network, and `pay_to` address Qonoro requires.
3. Sign an x402 payment for that amount/network/address with your own
   wallet (Qonoro never sees or needs your private key).
4. Call the tool again with the same arguments plus `payment_signature` set
   to your signed value. The server forwards it to Qonoro, which validates
   and settles it, then returns the real result.

No wallet key, API key, or secret is required to run this MCP server
itself -- the only configuration is which Qonoro base URL to call
(defaults to production).

## Local Development

```powershell
conda create -n qonoro-mcp python=3.12 -y
conda activate qonoro-mcp
pip install -e ".[dev]"
copy .env.example .env
pytest
qonoro-mcp
```

This repo has its own Conda environment (`qonoro-mcp`), same as every other
Qonoro backend repo — see `docs/01_PROJECT_SETUP_GUIDE.md`. Do not install
this into a shared/base environment; it isolates the `mcp`/`x402` SDK
versions from whatever other Qonoro repos have installed.

Or point an MCP client (Claude Desktop, Cursor, etc.) at:

```json
{
  "mcpServers": {
    "qonoro": {
      "command": "qonoro-mcp"
    }
  }
}
```

## Configuration

See `.env.example`. There are no secrets to fill in -- `QONORO_BASE_URL`
defaults to `https://api.qonoro.ai` and only needs overriding for local
testing against a dev server.

See `AGENTS.md` for the payment-bridge design rationale and the checklist
for adding a new Qonoro agent to this server.
