For AI agents · MCP

Help your agent stop subscriptions you barely use.

Cancel safely, keep a service for less, or replace only the features you need. Stackcut gives your agent the billing route, what to export first, sourced alternatives and a plan you can review. Free, no API key.

https://stackcut.io/mcp

Want no argument logging, or listing Stackcut in an app directory? Use https://stackcut.io/mcp/public: the same tools except get_my_plan, routine calls keep no arguments or answer contents. Exit tools retain only result counts, qualification flags and public evidence statuses. Explicit action reports and guide feedback retain disclosed structured fields for review, including optional offer terms or a public vendor domain. Reports remain unverified.

Connect once. Start with a real task.

Copy one of these prompts into your connected agent. It asks for the facts that change the answer, retrieves the current guidance and keeps you in control.

Cancel a subscription

Use Stackcut to help me cancel a subscription I barely use. First ask which service, who bills me and my renewal date. Get the current exit plan, show its check date and any unconfirmed details, and prepare exports and cancellation steps. I will sign in and approve the final action.

Keep it for less

Use Stackcut to help me pay less for a subscription. Ask which features I need, who bills me, my plan and actual bill. Compare documented downgrade or negotiation paths and explain unknown eligibility and commitments. Do not accept an offer or change my account.

Replace what I barely use

Use Stackcut to find a replacement for software I barely use. Ask what I pay and which features matter. Compare cheaper vendors, open source, pay per use and building only the features I need. Cite costs, setup and upkeep; label modeled savings and unresolved assumptions.

Guidance comes with source dates and evidence status. A documentation check is not a completed cancellation. If a step changes, your agent can send structured feedback for review.

Connect

Claude Code

claude mcp add --transport http stackcut https://stackcut.io/mcp

Claude (web and desktop)

Settings → Connectors → Add custom connector. Name it Stackcut and paste the URL. No sign-in step.

Cursor

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "stackcut": {
      "url": "https://stackcut.io/mcp"
    }
  }
}

VS Code

Add to .vscode/mcp.json

{
  "servers": {
    "stackcut": {
      "type": "http",
      "url": "https://stackcut.io/mcp"
    }
  }
}

Any client or a quick test

This example is a read-only evaluation and does not count as adoption. Stateless JSON-RPC over POST. Clients that only speak stdio can use npx mcp-remote https://stackcut.io/mcp.

curl -s https://stackcut.io/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -H 'X-Stackcut-Evaluation: true' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"find_alternatives","arguments":{"vendor":"Airtable","monthly_spend_usd":400}}}'

Your savings plan, in your agent

Got a Stackcut plan? Hand it to your agent and let it do the legwork: compare plans, draft cancellations, set up replacements. It reads the plan with a read-only code that expires, and asks you before any cancel or purchase.

1. Make a code

Open your plan on stackcut.io/app → Send to my agent → Make a code. It lasts 7 days; “Stop sharing” turns it off.

2. Paste the prompt

Copy the prompt it gives you into Claude, ChatGPT, Cursor or Claude Code. Your agent calls:

get_my_plan({"code": "sca_…"})

What your agent gets

Every line with its verdict and proof: the receipts or card charges behind the price, the alternative's price with a link to its pricing page, which of your ticked features it covers, the steps, checks, pros and cons, time, and a ready prompt. A saving that can't be proven is null, never a guess. No MCP in your agent? “Copy plan as Markdown” on the same card.

Choosing a stack

When you ask your agent “what's the best database for this?” or “what's the cheapest way to build this?”, choose_stack compares vendors per job at your volume. A tier counts as a fit only when its published limit covers your number; otherwise it says what to check. Open-source options are listed with their license, and your server cost is left to you, not guessed.

choose_stack({"project": "B2B SaaS MVP", "needs": [
  {"job": "database", "features": ["Postgres database", "Auth"], "volume": {"amount": 20000, "unit": "MAU"}},
  {"job": "email_transactional", "volume": {"amount": 40000, "unit": "emails_per_month"}},
  {"job": "hosting"} ]})

→ Supabase Free $0 (its published 50,000 MAU cap covers 20,000, with the note that free projects pause after 7 days idle), Amazon SES $4/mo (40,000 emails at $0.10 per 1,000), and for hosting a question: how much traffic? Add "scales": [1000, 20000, 200000] for cost curves and break-evens, or hand it a product brief with plan_stack_from_spec and it works out the jobs itself.

Audit a codebase

Your agent can see what your code actually uses: payment, email, analytics, monitoring and AI SDKs, env var names, config files and API calls. The Stackcut skill scans the repo on your machine and sends only vendor and feature names to audit_stack. No source code, no secret values, and it never opens .env.

1. Install the skill

Download it and unzip into your agent's skills folder. For Claude Code: ~/.claude/skills/ (so you get ~/.claude/skills/stackcut/SKILL.md).

Or give your agent the link: stackcut.io/agents/SKILL.md.

2. Ask your agent

"Audit the paid services in this repo with Stackcut." It runs the scanner, asks what you pay, then calls audit_stack.

node ~/.claude/skills/stackcut/scripts/detect.mjs . --latest --pretty

Baseline a team's stack

For a decision the bills alone can't settle (cut spend across several tools, consolidate apps, replace one safely), your agent calls start_audit with what it knows. Stackcut answers with the few facts that would change the answer, highest stakes first, and where people find each one: seats used, the plan, renewal dates, the features the team relies on. The agent collects those on your side and calls again until the answer is firm. Counts, prices and dates only: never names, emails or exports. How the loop works · manifest schema

What the scan sends

Only a summary like this. Rules for about 100 vendors live at /data/detect.json (also the get_detection_rules tool).

{"vendor":"sendgrid","features_used":["Transactional send","Dynamic templates"],
 "evidence":["npm:@sendgrid/mail","env:SENDGRID_API_KEY"],"monthly_spend_usd":19.95}

Cancel or pay less, with your agent

The stackcut-leave skill gets a service's exit plan from the cancel library: who bills you, the steps and what each page should say, what to export first, and cheaper ways to keep it. Your agent prepares everything and walks the flow with you. You sign in, decide on any offer and make the final click. It uses get_exit_plan on the MCP server, or the open JSON without it.

Or give your agent the link: stackcut.io/downloads/skills/stackcut-leave.zip.

Tools

ToolWhat it doesDetails
search_discoveriesSearch reviewed software discoveriesFind human-reviewed research notes about new products, replacement workflows, changed flows and build-versus-buy lessons.
search_recipesSearch replacement recipesUse when the user wants a cheaper way to do a job and names a feature or kind of tool rather than one product: 'cheaper keyword research', 'forms without Typeform', 'what can replace our CRM'.
get_recipeGet a recipeFull detail for one recipe from search_recipes: every replacement path with modeled first-year savings, monthly cost, setup time and upkeep, what is out of scope, checks to run before switching, how to leave the current vendor (cancel steps, refunds, exports, what you lose), step-by-step playbooks, sources, and Stackcut's own lab results where they exist (not customer results).
find_alternativesFind alternatives for a subscriptionUse when the user names one product they pay for and asks for something cheaper, whether it's worth it, or what to switch to: 'cheaper than Typeform?', 'is Semrush worth $139 a month for us?', 'we pay $90 for SendGrid'.
get_build_packetGet a build packet (Replace with AI)Use when the user wants to replace a tool by building their own (Replace with AI): returns SPEC.md, AGENTS.md and the runbook files a coding agent builds from, for a recipe with a build path.
search_workflow_recipesFind end-to-end workflow recipesUse for a whole operational change rather than one subscription: billing shared across projects, moving hosting or email, retiring a dormant project, cheaper AI model routing, queues, auth or storage.
get_workflow_recipeGet an end-to-end workflow recipeOne runbook from search_workflow_recipes in full: the evidence to collect, keep/downsize/consolidate/migrate/build/retire decisions, ordered steps, acceptance tests, rollout, rollback, maintenance, costs still unresolved, and scoped starter templates with their download digest.
leaderboardSavings leaderboardThe top replacement paths across the catalog by modeled first-year savings, payback months, or how often people and agents used them.
audit_stackAudit a stack (code + billing)Use when the user wants their stack checked as a whole: several subscriptions, the paid services in a codebase, or a portfolio of products ('audit what we pay for', 'what can we cut?').
get_detection_rulesGet code detection rulesRules for finding paid services in a codebase on the user's own machine: package names, environment variable name patterns, config files, API hosts and feature patterns for about 100 vendors.
get_usage_questionsUsage questions for vendorsBefore an audit: which usage numbers decide each vendor's answer (emails a month, domains, database size, seats…), where the user finds each one (dashboard page, API, export), and ready-to-ask questions.
start_auditStart a stack audit (baseline)Start here when the user wants to cut spend across several tools, consolidate apps, or replace one tool safely, and the bills alone won't decide it.
list_categoriesList categoriesThe catalog's categories with how many recipes each has and the best modeled first-year saving in each.
get_my_planGet the user's Stackcut savings planUse only when the user gives you a Stackcut agent code (it starts with sca_; they copy it from 'Send to my agent' on stackcut.io).
choose_stackChoose the most cost-effective stackUse when the user is picking vendors for something they're building: 'cheapest database for 20k users', 'Resend or Postmark at 60,000 emails a month?', 'what will auth cost at 10k MAU?'.
plan_stack_from_specPlan a stack from a product briefUse when the user shares a product brief or spec and asks what to build it with or what it will cost.
list_stack_jobsList stack jobsThe jobs choose_stack can compare (database, auth, hosting, transactional and inbound email, object storage, LLM APIs, payments, sandboxes, browser automation, queues…) with how many vendors each has, plus the volume units and aliases it accepts.
get_exit_planHow to cancel a subscriptionUse when the user wants to cancel, unsubscribe from, pause or pay less for something they subscribe to: streaming, music, news, dating, cloud storage, AI tools, apps or business software ('cancel YouTube TV', 'how do I get out of Adobe', 'stop my Audible').
prepare_negotiationPrepare a subscription negotiationFind documented existing-customer offers, cancellation-flow promotions and renewal negotiation routes for a service.
search_exitsBrowse the cancel libraryLists services in Stackcut's cancel library (streaming, music, news, dating, cloud storage, AI tools, apps and software), by name, domain or category, with the page and JSON for each.
report_exit_outcomeReport how a cancellation wentAfter the user reports what happened, count a cancellation, keeping the service for less, getting blocked, or changed steps.
report_action_outcomeReport an action outcomeRecord a minimal structured report about an attempted cancel, price reduction, negotiation, pause, downgrade, or switch.
report_guide_feedbackReport guide feedbackAfter using guidance, report a missing vendor or billing route, a mismatching step, unavailable source, incomplete instructions, unexpected fee, observed retention offer, required human handoff, or that the guide matched.
report_outcomeReport what the user didOnly after the user confirms what they did: record that they picked, switched to or reverted from a replacement path.

Try asking your agent

"Audit the paid services in this repo and tell me what to cut."

Skill scan → audit_stack → per service: eligible, needs your price, keep, or no recipe yet.

"We pay $1,000 a month for Salesforce Pro and only use contacts, one pipeline and tasks. What should we do?"

find_alternatives → Bigin Express, modeled at $10,260 saved in year one, with what it does not cover.

"Which open-source tools could replace our Semrush seat for keyword and rank checks?"

search_recipes + get_recipe → OpenSEO self-hosted or hosted, with setup hours and license notes.

"Build us a replacement for our Typeform intake flow."

get_build_packet → SPEC.md, AGENTS.md and a manifest your coding agent builds from.

"Move our background jobs off the paid queue without losing retries or approvals."

search_workflow_recipes + get_workflow_recipe → the evidence to collect, decision paths, acceptance tests and rollback, as a reviewed runbook (not a result).

"What are the biggest savings for a small team right now?"

leaderboard → the same ranking as stackcut.io/leaderboard.

"Here's my Stackcut code. Help me cancel what I don't need."

get_my_plan → your plan line by line with its proof, then the steps, asking you first.

"Figure out the most cost-effective way to build this app for 5,000 users."

choose_stack → per job: the cheapest tier whose published limits cover 5,000 users, with links.

What the server keeps

No accounts. To improve recommendations and prices, the server stores what agents send to each tool (vendor names, prices, seats, features, usage numbers, project descriptions), redacted of anything that looks like a key, token or email address, with a short summary of the answer and a caller id hashed with the date. It never stores IP addresses, and get_my_plan passes your plan through to your agent with your read-only code and keeps nothing. Each recipe view, estimate, spec download and reported switch also adds 1 to a public daily counter for that recipe (the "Most used" leaderboard). Savings are modeled, so agents are told to confirm must-have features and usage before recommending a switch. Details: privacy policy.