Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Appmate is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Model Context Protocol server for AppMate — lets Claude / Cursor / Codex drive your retention flows via API tokens.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user appmate-mcp '--' npx -y @fil-technology/appmate-mcp
# 2 — ask your agent for something these tools do
# list_apps, get_app, create_app and 40 more
Appmate costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Appmate as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user appmate-mcp '--' npx -y @fil-technology/appmate-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
43 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List every AppMate app the API token can see. Returns id, slug, name, bundleId, deepLinkScheme, logoUrl, timestamps.
No parameter schema on file.
Fetch a single AppMate app by its cuid id or slug. Use list_apps first if you don
No parameter schema on file.
Create a new AppMate app. The slug auto-derives from the name when omitted.
No parameter schema on file.
Read the published and draft cancel flow configs. An app can have MULTIPLE cancel flows — pass flowSlug for a secondary (omit for the primary); call list_flows to see existing slugs.
No parameter schema on file.
Read the published and draft waitlist flow configs. An app can have MULTIPLE waitlists — pass flowSlug for a secondary (omit for the primary); call list_flows to see existing slugs.
No parameter schema on file.
Promote the draft waitlist config to the live published version. Pass flowSlug to publish a secondary waitlist (omit for the primary).
No parameter schema on file.
Paginated list of waitlist signups for an app. Each row: { id, email, source, country, area, approxLat, approxLon, geohash, locale, platform, appVersion, userAgent, createdAt }.
No parameter schema on file.
Return the full waitlist for an app as a CSV string (header row + one row per signup). Useful for hand-off to spreadsheet or mail merge.
No parameter schema on file.
Read the published and draft feedback flow configs for an app. Feedback flows host an open-ended message form (optional 1–5 star rating + optional reply email) at appmate.cloud/feedback/{appSlug}.
No parameter schema on file.
Promote the draft feedback config to the live published version. Visitors at appmate.cloud/feedback/{appSlug} see the new version immediately.
No parameter schema on file.
Paginated list of feedback submissions for an app. Each row: { id, message, rating, email, source, createdAt }. limit max 200, default 50; pass nextCursor back for the next page.
No parameter schema on file.
Read the published and draft report flow configs for an app. Report flows host a categorised bug/abuse/spam form (required category picker + message + optional reply email) at appmate.cloud/report/{appSlug}.
No parameter schema on file.
Promote the draft report config to the live published version. Visitors at appmate.cloud/report/{appSlug} see the new version immediately.
No parameter schema on file.
Paginated list of report submissions for an app. Each row: { id, message, category, email, source, createdAt }. Pass
No parameter schema on file.
Promote the draft crash flow config to the live published version. Visitors at appmate.cloud/crash/{appSlug} (and SDK clients) see the new version immediately.
No parameter schema on file.
Paginated list of crash reports for an app. Each row: { id, message, status, reviewedAt, exceptionName, exceptionReason, stackTrace, platform, osVersion, deviceModel, appVersion, buildNumber, crashedAt, metadata, attachments, email, source, country, userAgent, createdAt }.
No parameter schema on file.
Move a crash report through triage:
No parameter schema on file.
Read the published and draft cross-app promotion (app_promotion) config for an app. A promotion promotes OTHER apps in the same account as destinations. An app can have MULTIPLE promotion flows — one per placement — so pass flowSlug for a specific one (omit for the default
No parameter schema on file.
Promote the draft cross-app promotion config to the live published version. SDK placement requests resolve against the new version immediately. Pass flowSlug to publish a specific placement (omit for the default
No parameter schema on file.
Read the published + draft legal (privacy policy + terms) config for an app, plus the public URLs. The page is composed from structured facts (entity, processors, declarations, platform capabilities) — not free text.
No parameter schema on file.
Publish the draft legal policy. Stamps the effective date to today, freezes this version immutably (prior versions stay at /legal/{appSlug}/v/{n}), and returns both public URLs { privacy, terms }. A published page is never silently rewritten.
No parameter schema on file.
Read the published and draft contact flow configs for an app. Contact flows host a minimal inquiry form (optional name + required/optional email + optional message text) at appmate.cloud/contact/{appSlug}.
No parameter schema on file.
Promote the draft contact config to the live published version. Visitors at appmate.cloud/contact/{appSlug} see the new version live immediately.
No parameter schema on file.
Read the published and draft link-page configs for an app. A link page is a shareable
No parameter schema on file.
Promote the draft link-page config to the live published version. Visitors at appmate.cloud/p/{appSlug} see the new version immediately.
No parameter schema on file.
Paginated list of contact submissions for an app. Each row: { id, name, email, message, source, country, createdAt }. limit max 200, default 50; pass nextCursor back for next page.
No parameter schema on file.
Send a branded email reply to a contact submission, from AppMate. The email is sent from the app-branded AppMate address; Reply-To is the app
No parameter schema on file.
Promote the draft onboarding config to the live published version. Visitors at appmate.cloud/onboarding/{appSlug} see the new funnel immediately.
No parameter schema on file.
Paginated list of completed onboarding funnels for an app. Each row: { id, answers, email, source, claimed, claimedAt, country, createdAt }.
No parameter schema on file.
Return all completed onboarding funnels for an app as a CSV string (header row + one row per completion, with email + answers JSON + claim status). Useful for hand-off to a spreadsheet or mail merge.
No parameter schema on file.
Promote the draft referral config to the live published version. New share links + the invite landing use the new config immediately.
No parameter schema on file.
Paginated list of referrals for an app. Each row: { id, code, referrerUserId, status, source, refereeUserId, attributedAt, referrerRewarded, refereeRewarded, country, createdAt }. status=
No parameter schema on file.
Return the full referral graph for an app as a CSV string (one row per invite, with code, status, source (link/typed-code), referee, and reward flags).
No parameter schema on file.
Promote the draft wishlist config to the live published version. Visitors at appmate.cloud/wishlist/{appSlug} see the new version immediately. For an iOS app, surface the board natively with the SDK (RetentionFlow.presentWishlist(userId:) / WishlistView) rather than linking this URL.
No parameter schema on file.
Paginated list of wishlist ideas for an app — ALL statuses (including pending review). Each row: { id, title, body, category, status, voteCount, commentCount, pinned, author, email, source, country, createdAt }. Optional status (
No parameter schema on file.
Seed an idea onto the board as the app owner (so it isn
No parameter schema on file.
Moderate an idea: set its status and/or pin it.
No parameter schema on file.
Permanently delete an idea AND all of its votes and comments. IRREVERSIBLE — there is no undo. Prefer set_wishlist_idea_status with
No parameter schema on file.
Paginated comments on an idea (oldest-first, excludes deleted). Each row: { id, body, author, isOwner, isOfficial, createdAt }. limit max 200, default 50; pass nextCursor back for more.
No parameter schema on file.
Post an OWNER reply on an idea (shown with a Team badge). Set official:true to mark it an authoritative response. Use this to answer or expand on a user
No parameter schema on file.
Soft-delete a comment (hidden from the public board, thread continuity preserved). Use for moderation.
No parameter schema on file.
Return all wishlist ideas for an app as a CSV string (one row per idea, every status: created_at, status, title, votes, comments, category, email, author, country, body).
No parameter schema on file.
Permanently delete a short link and its recorded clicks. IRREVERSIBLE, and the code dies with it — anyone who already has the shortUrl (a printed QR, a scheduled post, an old tweet) gets a dead link, and the code may later be claimed by someone else. Prefer update_short_link with status:
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Appmate or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.15.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Appmate can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.