# Publishing on Faro

Faro fronts your existing MCP server with auth, billing, and discovery. You bring the server; Faro brings the buyers.

## What you ship

- An MCP-compatible HTTP endpoint (`https://mcp.yourdomain.com`) implementing the tools you want to monetize.
- A `faro.yaml` manifest declaring the namespace, listing copy, tools, and pricing.

## Path

```
pip install askfaro-cli
faro auth login

faro publisher register --display-name 'Acme'
faro ns quick-setup --namespace acme --mcp-url https://mcp.acme.dev
faro init acme                  # generates faro.yaml + README.md
$EDITOR faro.yaml               # description, tags, example_prompts, pricing
faro ns check acme              # local validation
faro push --publish             # save + submit for review
```

## Pricing

Set `pricing_mode: fixed_per_request` with a credit cost per tool group, or `tool_returned` to let your tool report its own cost (token-priced tools, etc.). 1,000 credits = $1.00 USD. Faro's margin is bundled into the price the buyer sees — don't reference your gross or our cut in user-facing copy.

## Upstream auth

Buyer-side, every request to Faro carries a single `faro_` Bearer. Faro forwards your upstream credentials (stored once as a Faro `connection`) as headers when proxying to your MCP server. Buyers never see them.

## Reviews

Every listing goes through a human review before going public. Use `faro ns check` first — it flags missing copy, broken schemas, and obvious smoke-test failures.

## Reference

- Full publisher API docs: https://api.askfaro.com/docs/
- CLI reference: https://askfaro.com/llms/cli.md
- Marketplace: https://askfaro.com/search