Connect your AI agent to Orizu.

Quick Start

Up and running in 30 seconds — install the MCP server in Claude Code, authenticate via browser sign-in, send your first prompt. (Tabs further down cover every other supported client.)

1. Step 1

   Install the MCP server

   Run this in your terminal — no secrets in the command, so it's safe to paste into chat / screenshare.

   terminal Copy

   claude mcp add --transport http orizu "https://orizustudio.co.uk/products/ai-invoice-generator/api/mcp"

2. Step 2

   Authenticate

   Start an interactive Claude session, then trigger the OAuth flow. A browser window opens — sign in and click Allow. Token is cached locally; no copy-paste, no secrets in the transcript.

   claude-code Copy

   claude
   > /mcp
   > orizu → Authenticate
   > [browser pops · click Allow]
   > orizu — ✓ Connected

3. Step 3

   Try a tool

   Ask Claude to use orizu. The instructions string tells the assistant exactly which tool to call.

   prompt Copy

   Using orizu, draft an invoice for Acme Design Collective
   for £6,500 — brand identity refresh, due in 30 days.

   The agent calls draft_invoice, auto-fills the From: block from your saved profile, and returns the invoice number + a public share link.

Installation

Pick your client below. The MCP server URL is the same for everyone — what differs is how each client expects to be told about it.

claude mcp add --transport http orizu "https://orizustudio.co.uk/products/ai-invoice-generator/api/mcp"

Authentication

Two paths. Browser sign-in (OAuth 2.1) is recommended for interactive sessions; bearer keys exist for CI / scripted environments where popping a browser isn't feasible.

OAuth 2.1 (recommended)

Triggered automatically on the first tool call (or manually via /mcp → Authenticate in Claude Code). PKCE-only, dynamic client registration per RFC 7591, refresh-token rotation per RFC 6749 §6.

• Access token TTL: 1 hour
• Refresh token TTL: 30 days, single-use (rotated on each refresh)
• Scope: invoices:rw
• Revocation: from Developer → Connected apps

OAuth discovery endpoints (served at the host root per RFC 8414 §3.1):

/.well-known/oauth-authorization-server/products/ai-invoice-generator
/.well-known/oauth-protected-resource/products/ai-invoice-generator

Bearer key (for CI / headless)

Mint a key from Developer → API keys. Keys are scoped per integration and revocable. Pass the key in the Authorization header on every request.

curl -X POST "https://orizustudio.co.uk/products/ai-invoice-generator/api/mcp" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer ozs_live_…" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Prefixes: ozs_live_ for production, ozs_test_ for sandbox. Never paste a key into a chat transcript — use OAuth instead.

Tools Reference

33 tools, grouped by lifecycle stage. The MCP server's tools/list endpoint returns these with full JSON Schema input definitions — your client renders them as typed parameters automatically.

For a single canonical version of this list as plain Markdown, see /agents.md.

Profile auto-fill

When an agent calls draft_invoice without explicit From: fields (company, name, email, phone, address, tax/VAT number), the server pulls them from your saved profile. Set those once in Account settings and every future invoice — drafted by you, by an agent, or by a recurring schedule — uses the same letterhead.

If the profile is empty for any required From: field, the server returns a structured response with missing_from_fields and a profile_edit_url. The instructions tell the assistant to either send the user to fill out the profile OR collect the missing fields in chat and re-call with explicit your_company / your_name / your_address args — which are then auto-saved to the profile so it's a one-time ask.

Conditional discounts

Drafting prompt: “Apply a 5% discount if the deposit lands within 7 days.” The MCP records the condition on the invoice. When mark_invoice_paid is called, the server checks whether the payment landed inside the window and auto-applies the discount — recalculating totals and stamping an audit JSONB on the invoice row.

Conditions are stored in discount_conditions on the invoice row. The audit landing in discount_applied (or stays empty when the condition wasn't met) is the proof you can show a client later.

Rate limits

Per-key (or per-OAuth-token) sustained rate is 120 tool calls per minute. Combined REST + MCP monthly cap is set by your plan tier:

Live usage: get_usage returns current-period counts plus a structured breakdown of PDF API vs MCP tool calls. Rate-limit responses include a Retry-After header.

Troubleshooting