Enhanced MCP server for Limitless Pendant with advanced conversation analysis, meeting detection, action item extraction, and comprehensive
Free
Nothing to run from here
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.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
Model Context Protocol server for AppMate — lets Claude / Cursor / Codex drive your retention flows via API tokens.
Quickstart
# 1 — run it from where its publisher ships it
npx -y @fil-technology/appmate-mcp
# 2 — ask your agent something
> Model Context Protocol server for AppMate — lets Claude / Cursor / Codex drive your retention flows via API tokens.
Appmate is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
FIAll 2 servers
@fil-technology2 servers
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add appmate-mcp -- npx -y @fil-technology/appmate-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
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.
What you approve
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.
Takes no parameters.
Example callreturns →
Fetch a single AppMate app by its cuid id or slug. Use list_apps first if you don
Takes no parameters.
Example callreturns →
Create a new AppMate app. The slug auto-derives from the name when omitted.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Promote the draft waitlist config to the live published version. Pass flowSlug to publish a secondary waitlist (omit for the primary).
Takes no parameters.
Example callreturns →
Paginated list of waitlist signups for an app. Each row: { id, email, source, country, area, approxLat, approxLon, geohash, locale, platform, appVersion, userAgent, createdAt }.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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}.
Takes no parameters.
Example callreturns →
Promote the draft feedback config to the live published version. Visitors at appmate.cloud/feedback/{appSlug} see the new version immediately.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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}.
Takes no parameters.
Example callreturns →
Promote the draft report config to the live published version. Visitors at appmate.cloud/report/{appSlug} see the new version immediately.
Takes no parameters.
Example callreturns →
Paginated list of report submissions for an app. Each row: { id, message, category, email, source, createdAt }. Pass
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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 }.
Takes no parameters.
Example callreturns →
Move a crash report through triage:
Takes no parameters.
Example callreturns →
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
Takes no parameters.
Example callreturns →
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
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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}.
Takes no parameters.
Example callreturns →
Promote the draft contact config to the live published version. Visitors at appmate.cloud/contact/{appSlug} see the new version live immediately.
Takes no parameters.
Example callreturns →
Read the published and draft link-page configs for an app. A link page is a shareable
Takes no parameters.
Example callreturns →
Promote the draft link-page config to the live published version. Visitors at appmate.cloud/p/{appSlug} see the new version immediately.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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
Takes no parameters.
Example callreturns →
Promote the draft onboarding config to the live published version. Visitors at appmate.cloud/onboarding/{appSlug} see the new funnel immediately.
Takes no parameters.
Example callreturns →
Paginated list of completed onboarding funnels for an app. Each row: { id, answers, email, source, claimed, claimedAt, country, createdAt }.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Promote the draft referral config to the live published version. New share links + the invite landing use the new config immediately.
Takes no parameters.
Example callreturns →
Paginated list of referrals for an app. Each row: { id, code, referrerUserId, status, source, refereeUserId, attributedAt, referrerRewarded, refereeRewarded, country, createdAt }. status=
Takes no parameters.
Example callreturns →
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).
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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 (
Takes no parameters.
Example callreturns →
Seed an idea onto the board as the app owner (so it isn
Takes no parameters.
Example callreturns →
Moderate an idea: set its status and/or pin it.
Takes no parameters.
Example callreturns →
Permanently delete an idea AND all of its votes and comments. IRREVERSIBLE — there is no undo. Prefer set_wishlist_idea_status with
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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
Takes no parameters.
Example callreturns →
Soft-delete a comment (hidden from the public board, thread continuity preserved). Use for moderation.
Takes no parameters.
Example callreturns →
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).
Takes no parameters.
Example callreturns →
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:
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Appmate costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 99 / 100
Release 0.13.0 · scanned 25 Aug 2026
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.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digestfca7cfec46a612c8916605ef80bfb3b11cd42826227362ece20254e27ea8af47
Score vectorthreat 100 → client 99
| 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 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
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. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
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
Integrityfirst-seen
Surface digestfca7cfec46a612c8
Scanned2026-08-25
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
Pinned to 0.13.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
0.13.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Appmate in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
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 an account with 50 real tool calls against it.