Kordi

What is Kordi?

Kordi is a subscription intelligence platform. This MCP (Model Context Protocol) server lets any MCP-speaking AI client (e.g., Claude Desktop, Cursor, Raycast) read a user’s tracked subscriptions, score their billing health, surface savings, generate cancel/pause links, and push newly discovered subscriptions into the platform. It is a hosted, remote server—no local installation required—connecting via Streamable HTTP with Bearer token authentication.

How to use Kordi?

Obtain a 90‑day API token at kordiapp.com/token. Then configure your MCP client to use https://kordiapp.com/mcp as the endpoint with an Authorization: Bearer <token> header. For Claude Desktop, add the server to claude_desktop_config.json using type streamable-http. Alternatively, call the endpoint directly with curl passing the Bearer token. Tokens are scoped to your own subscriptions and can be rotated at any time.

Key features of Kordi

• List all tracked subscriptions with pagination (kordi_list_subscriptions).
• Score billing health 0–100 (kordi_analyze_billing_health).
• Generate deep links to cancel or pause services (kordi_get_cancellation_route).
• Push newly discovered subscriptions via kordi_ingest_subscription (dedupes by name).
• See cross‑user popularity of shows (kordi_get_top_shows).
• Proactive billing‑health snapshot via the kordi://subscription-pulse resource.

Use cases of Kordi

• Ask “What am I paying for each month?” and get an itemised list.
• “Which subscriptions could I pause to save money?” — identify savings candidates.
• “Do I have any price hikes or trials ending soon?” — scan for alerts.
• “I just signed up for Apple TV+ at $9.99/mo — track it.” — ingest a new subscription.
• “Show me the cancellation link for Netflix.” — get a signed, expiring deep link.

FAQ from Kordi

How do I get an API token?

Sign in at kordiapp.com and generate a token at kordiapp.com/token. Tokens are valid for 90 days and grant read/write access only to your own subscriptions. You can rotate them at any time.

What authentication and transport does the server use?

It uses Streamable HTTP transport with Bearer token authentication (Authorization: Bearer <token>). A legacy query‑string ?token=<token> form is also accepted for backward compatibility.

What are the rate limits and response size limits?

The server allows 20 tool calls per 60 seconds per session. Over the limit, tools return a back‑off message. Large list responses are capped at roughly 25,000 characters; use offset/limit pagination for large accounts.

Can I cancel or pause subscriptions via this server?

Yes. kordi_get_cancellation_route generates a signed deep link to cancel or pause a service, but should only be called when the user explicitly asks. The returned cancellation link expires after 7 days.

How are sensitive payment details handled?

Sensitive card fields (PAN, CVV, expiry, raw tokens) are never returned in any response. They are stripped server‑side and never leave the server.