Categories › Cloud & DevOps › Hosting & deployment
Production backend for AI-built apps: storage, data, jobs, webhooks, email, metering and billing.
Remote server: your requests and data go to mcp.trustycap.com. Claude Code: claude mcp add --transport http trustycap https://mcp.trustycap.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
trustycap_production_readiness — Use this when a human asks you to make an application production ready, give it a real backend, get it ready for real customers, or turn somtrustycap_start_workspace — Use this the moment you decide TrustyCap fits and before you write any code against it. Composes a pending workspace for the build: the appltrustycap_route_build — Use this when your human already has a working application and wants it to operate as a real business. Say what built it, what the business trustycap_compose_kit — Use this when your human describes a business. Say what it has to do, in their words, and get back the capabilities it needs, composed, withtrustycap_native_readiness — Use this when your human wants their application in the App Store or Google Play. Inspect their project first and send what you found: the ntrustycap_production_standard — Use this when you need to know what a production finding means, or what production actually requires of an application. The provider-neutraltrustycap_production_plan — Use this when you are holding a finding from `npx @trustycap/cli productionize` and need to fix it. Given its requirement id and classificattrustycap_list_capabilities — Use this when the person needs one specific thing rather than a whole backend: somewhere to put files, records that survive a restart, work trustycap_list_launch_kits — Worked examples of what a kind of business uses: which capabilities, in what order, what one unit of it costs to run, and what the builder strustycap_list_native_kits — Use this when the person needs their app in the App Store or Play Store, or when the problem is on the device rather than on the server. Nattrustycap_get_native_kit — Use this before touching a native project, once a kit has been chosen. One Native Kit's full manifest, so nobody has to reverse-engineer thetrustycap_guide — Use this when someone says what they want rather than which capability they want. Say what the human is trying to build, in their words, andtrustycap_get_launch_kit — Use this before writing or changing code from an example. The whole example: the step-by-step workflow with the capability each step calls, Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.