Plugin tracker

Tools

Explore what tracked Claude Connectors and ChatGPT Plugins can actually do. Search by tool, Plugin, Brand, category, verb, or access requirement.

Latest snapshot2026-09-12USmethodology registry-public-v1

Searchable tools

113,018

Authless tools

7,424

Auth required

100,766

Described tools

61,167

113,018 tools

Confirm File Uploadconfirm · Step 2 of attaching a file: call this AFTER POSTing the bytes to the upload.url from request-file-upload. It verifies the object actually landed in storage and records it on the memo (file_id, name, type, size), returning the recorded file. Use the same memo_id and file_id you got from request-file-upload. Anyone with access to the memo can later download the file via a short-lived get-file-url link — there is no public/permanent link. Requires write access to the memo.MemocoreMemocorePluginrequiredAI
Create Private Memocreate · Save a PRIVATE memory to memocore ("mc") — visible only to you, never shared. Use for personal facts, preferences or notes. Keep ONE coherent topic per memo; split unrelated topics (e.g. overview, tech stack, pricing) into separate memos. Before saving, run search-memo: if a memo on this topic already exists, merge the new facts into it with update-private-memo instead of creating a duplicate — save a new memo only when none fits. Always fill `meta` with retrieval cues and `preview` with a short public summary. To tag, first run search-tag (create-tag only if none fits) and pass its id — private memos may use only your private tags. For a shared project, use create-project-memo instead. The response includes a `share_url` field; for a private memo it explains there is no link (private memos cannot be shared) — never build one from `id`. The response may carry a `recommendation` with `similar` (near-duplicate memos in this scope — if any is truly the same, consolidate: merge into one, delete the extras with delete-memo) and `suggested_tags` (fitting tags for this memo — add the relevant ones, especially if it has none yet).MemocoreMemocorePluginrequiredAI
Create Projectcreate · Create a project — a shared space whose memories are visible to all members (you become its owner). First run search-projects and reuse a matching one — create only when none fits, to avoid duplicates. Give a clear `description` of what belongs in it: search-projects shows it and uses it to route future memories here. To create it INSIDE a company (corporate, shared with the whole team, not just you), pass `company_id` from search-companies; omit it for a personal project. Returns the new project, including its id.MemocoreMemocorePluginrequiredAI
Create Project Memocreate · Save a memory into a SHARED memocore project — visible to, and editable by, every member. Keep ONE coherent topic per memo; split unrelated topics (e.g. overview, tech stack, pricing) into separate memos. Before saving, run search-memo scoped to the project: if this topic already exists, merge the new facts into it with update-project-memo instead of creating a duplicate — save a new memo only when none fits. Always fill `meta` with retrieval cues and `preview` with a short summary. NOTE: `preview` is PUBLIC — it is shown in search results and may be exposed via public share links (even outside the project), so it must never contain sensitive data. To tag, first run search-tag (create-tag only if none fits); a project memo may use only this project's tags. Before calling you MUST: (1) Scan `content` for personal or sensitive data (private contacts, secrets, credentials, health/financial info). If any is present, proceed only on the user's explicit confirmation to store it in a shared project. (2) Be certain which project this belongs to: match the memory against each project's description from search-projects, and if not 100% sure, ask the user — never guess. Set `privacy_reviewed` and `target_confident` to true only once both checks genuinely pass. For private/personal notes use create-private-memo instead. The response includes a `share_url` field — for a just-created memo it is a hint, not a link (a memo has no public link until you call set-memo-sharing). If the user wants a link, follow that hint; never build one from `id`. The response may carry a `recommendation` with `similar` (near-duplicate memos in this project — if any is truly the same, consolidate: merge into one, delete the extras with delete-memo, staying within this project) and `suggested_tags` (fitting project tags for this memo — add the relevant ones, especially if it has none yet).MemocoreMemocorePluginrequiredAI
Create Tagcreate · Create a tag for labelling memories. First run search-tag and reuse a fitting tag — create only when none fits, to avoid duplicates. Omit `project_id` for a PRIVATE tag (only yours); pass it for a SHARED tag of that project. Returns the tag, including its id.MemocoreMemocorePluginrequiredAI
Delete Filedelete · Remove a file attached to a memo — deletes it from storage and detaches it from the memo. Use the memo_id and the attachment's file_id. Requires write access to the memo (its private owner, or a member of its project).MemocoreMemocorePluginrequiredAI
Delete Memodelete · Delete a memory the user can access — their own private memo, or any memo in a project they belong to. Two-step by design, so a delete stays recoverable for 45 days. Default call (no `permanent`): ARCHIVES the memo — it instantly disappears from every search and list, and is scheduled for permanent erasure 45 days later. Pass a short `reason` for why you are removing it; it is written to the memo's change history and shown in the project activity feed. Within those 45 days it can be brought back with restore-memo. Calling delete-memo again on an already-archived memo WITHOUT `permanent` returns an error — set `permanent: true` to erase it forever now (irreversible; no history written). `permanent: true` on an active memo skips the archive and erases it immediately. Use the default (archive) flow whenever the user asks to delete or forget something; reserve `permanent` for an explicit "delete forever / permanently".MemocoreMemocorePluginrequiredAI
Delete Tagdelete · Delete a tag the authenticated user can access — their own private tag, or a tag of a project they belong to. The tag is also detached from every memo that used it.MemocoreMemocorePluginrequiredAI
Get File Urlget · Get a short-lived download URL for a file attached to a memo (expires in ~15 min). Returns { url, expires_in }. Files have no standing link, so call this whenever the user needs the bytes (e.g. to render an image). Find the file_id in the memo's `files` (from get-memos). Requires access to the memo (its private owner, or a member of its project).MemocoreMemocorePluginrequiredAI
Get Memo Historyget · Read the change history of ONE memo by id — a timeline (newest first) of every edit: who changed it, when, and a short `changes` note of what changed and why. Use this to show or review how a memo evolved. Not loaded by get-memos/search-memo (which return only the current memo), so fetch it here when the history itself is what you need.MemocoreMemocorePluginrequiredAI
Get Memosget · Fetch the FULL content of specific memos by their ids — including each memo's `files` attachment list (file_id, name, type, size). search-memo only flags `has_files`, so come here for the actual list. Files carry no standing `url` — call get-file-url with the memo_id + file_id to mint a short-lived download link when the user needs the bytes (render an inline image for image/* types, otherwise a markdown link). Use after search-memo to read the memos you picked from the preview list (search-memo returns only the short public `preview` summary, not the full `content` or the `meta` cues). Takes memo IDS ONLY — to open a memo from a `memocore.ai/m/…` share link, use open-memo-link instead, not this tool. Each returned memo carries a `share_url`: the public /m/ link when it is ALREADY shared, otherwise a short hint. When the user wants a link to a memo, use `share_url` — if it is a hint (not a URL), follow it (call set-memo-sharing); NEVER build a link from `id`. Returns { items, recommendation }; only memos you can access are returned — ids that do not exist or that you cannot access are omitted and reported in `recommendation`.MemocoreMemocorePluginrequiredAI
Get Projectget · Read one project you belong to, by id (from search-projects). Returns the full project, including its `instruction` — the rules its team set for what memos saved here must look like. Call this whenever search-projects shows `has_instruction: true` for the project you are about to write into: read the instruction, apply it to the memo you are saving, then pass instruction_reviewed: true to create-project-memo / update-project-memo. Skipping this is refused, and the rules come back in the error anyway — reading them first just saves the round trip. Followers who walked in through a public link cannot read a project this way.MemocoreMemocorePluginrequiredAI
List Memo Historylist · Read a cross-memo change FEED (newest first) — recent edits across many memos, each entry carrying the memo title, who changed it, when, and the agent's `changes` note. With no scope it returns YOUR private memos' history; pass `project_id` for one shared project, or `company_id` for a whole company (the projects you can see in it). Use this for a "what changed recently" activity view; for the full timeline of a single memo use get-memo-history.MemocoreMemocorePluginrequiredAI
Open Memo Linkopen · Open a memocore memo from its share link. Use this WHENEVER the user gives you a `memocore.ai/m/…` link — even on its own, and even if they say "look at this page/site/link". Do NOT fetch it as a web page. Always returns the memo's title + preview; the content and its attachments are added when the link lets you read it (a MEMBER of the memo's project, or public → anyone, company → members of the owning company) — VIEW only, never edit. Returns { memo } with whatever the link grants, or { memo: null, recommendation } when the link is unknown or revoked.MemocoreMemocorePluginrequiredAI
Request File Uploadrequest · Step 1 of attaching a file to a memo. Returns a short-lived upload ticket ({ file_id, upload: { url, token }, max_size, expires_in }). The file BYTES are uploaded over plain HTTP straight to storage — they must NOT pass through this tool or the model context (never base64 the file into a tool argument). Flow: (1) call this with the target memo_id and the file's content_type; (2) HTTP POST to upload.url as multipart/form-data with exactly two fields — `token` set to upload.token, and `file` containing the bytes (read the file FROM DISK, e.g. `curl -F "token=<token>" -F "file=@/path/to/file" <url>`; size between 1 and max_size); (3) call confirm-file-upload with the same memo_id and file_id to record the file on the memo. Only text, media, PDF and office documents are accepted (text/*, image/*, audio/*, video/*, application/pdf, Word/Excel/PowerPoint, OpenDocument), up to max_size bytes (the per-file cap of the memo owner's plan). The ticket expires in ~15 min. If the byte upload fails because the network sandbox blocks it, the host shown in upload.url must be on the client's network allowlist — surface that exact host to the user to allow (in Claude Code it is also offered for one-click approval on first use); if it cannot be allowlisted (e.g. plain chat clients), hand the user the ready-to-run curl command so they upload it themselves from an unsandboxed terminal. Requires write access to the memo (its private owner, or a member of its project).MemocoreMemocorePluginrequiredAI
Restore Memorestore · Restore a memo that was deleted (archived) with delete-memo, while it is still within the 45-day window before permanent erasure. Clears the archive flag so the memo is active, searchable and listed again. Find restorable memos with search-memo using archived: true. After 45 days the memo is erased for good and can no longer be restored.MemocoreMemocorePluginrequiredAI
Search Companiessearch · List the companies (teams / organisations) the authenticated user belongs to. Returns { items, recommendation } where each item is { id, name, role ("owner" | "member"), active }. Use it to resolve a company name to its id before creating a corporate project (pass the id as create-project's `company_id`) or listing a company's projects (pass it as search-projects' `company_id`). `active` is whether the team subscription still grants access — a company project can only be created or used while it is true. With a `query`, filters by name; without, lists every company you belong to.MemocoreMemocorePluginrequiredAI
Search Memosearch · Search or recall memories from memocore (the user's persistent memory, also called "mc") — their own private memos and every project they belong to. Every search is HYBRID: `query` (a natural-language description of what you seek) drives meaning-based vector recall, `keywords` (the distinctive terms) drives keyword matching against the heavily-weighted `meta` cues, then title, preview and content; the two rankings are fused. Both are required — write them as two views of the SAME need, not two different questions. Results are LIGHTWEIGHT: each item shows only `title`, the short public `preview` summary, a `has_files` boolean, and where it lives — `project` and `company` as { id, name } and `tags` as [{ id, name }], so you can name the source and reuse the ids without a second lookup — but NOT the full `content`, the `meta` search cues, or the file list. Fetch the full content, meta and attachment list for the ids you need with get-memos. Returns `items` in relevance order plus a `recommendation` — READ THE RECOMMENDATION before trusting anything: it states how solid the results actually are, because a search ALWAYS returns a full page of nearest memos even when the memory holds nothing on the subject. It tells you which items (if any) both sides agreed on and are genuinely on topic, which merely share a word, and when the honest answer is that nothing was found and you should answer from scratch. Narrow with `scope` (private / a specific project), `tags` (only memos carrying ALL given tags) and `exclude_tags` (drop memos carrying ANY of them). With no `scope`/`company` the search spans EVERYTHING you can access (your private memos + every project you belong to, personal and company) and is billed to you; when you are confident which project or company holds the answer, pass its `scope` or `company` to focus there instead (more precise, and billed to that owner). Use to recall what the user or their projects previously stored.MemocoreMemocorePluginrequiredAI
Search Projectssearch · Search or list the projects the authenticated user belongs to. Returns { items, recommendation } where each item is { id, name, description, company_id } (company_id is set for a corporate/company project, absent for a personal one); read `recommendation` to decide which project to act on. With a `query`, filters by name/description; without, returns all your projects. Pass `company_id` (from search-companies) to list only that company's projects. Use to resolve a project name to its id, and match a memory against each project's description to decide which project it belongs to, before saving or searching memories in a project.MemocoreMemocorePluginrequiredAI
Search Tagsearch · Search or list tags the authenticated user can access — their private tags and the tags of every project they belong to. Returns { items, recommendation }; read `recommendation` to decide whether to reuse a match or create a new tag. With a `query`, ranks tags by relevance (matched against name and context). Without a `query`, returns a paginated list. Use to find an existing tag (by name or by what it is for) before creating a new one, or to resolve a tag id for tagging or filtering memos.MemocoreMemocorePluginrequiredAI
Set Memo Sharingset · Turn public sharing on/off for a PROJECT memo and set its visibility. `access` controls WHO may open the link: "project" (default — only project members), "company" (any member of the owning company; company-project memos only), or "public" (anyone with the link, no sign-in). At EVERY level the link exposes only the memo's title + preview — never its full content. Returns a ready public `url` (/m/<token>) plus a `recommendation`. Hand the user that `url` as-is; never build a link yourself. Built for forwarding: the title/preview unfurl as a card (Telegram etc.). PRIVATE memos cannot be shared. Requires the Max plan or a team plan (else 402). Revoke by calling again with shared=false (or by deleting the memo). Because title + preview become visible to the chosen audience, make sure they carry no sensitive data first. Requires write access to the memo (a member of its project).MemocoreMemocorePluginrequiredAI
Update Private Memoupdate · Update one of YOUR PRIVATE memos (visible only to you). Use this to actualize or merge into an existing memo instead of creating a near-duplicate. Only the provided fields change, and each REPLACES the old value wholesale — so to merge, fetch the current memo first (get-memos) and send the combined `content`, not just the new fact. Passing `tags` replaces the memo's tags (your private tags only). For a memo that lives in a shared project, use update-project-memo instead. The response includes a `share_url` field; for a private memo it explains there is no link (private memos cannot be shared) — never build one from `id`. The response may carry a `recommendation` with `similar` (near-duplicate memos in this scope — if any is truly the same, consolidate: merge into one, delete the extras with delete-memo) and `suggested_tags` (fitting tags for this memo — add the relevant ones, especially if it has none yet).MemocoreMemocorePluginrequiredAI
Update Projectupdate · Update a project you belong to — rename it or change its description. Only the provided fields change. Keep the `description` accurate: search-projects shows it and uses it to route future memories to the right project. Requires write access: owners and editors may update it, a viewer cannot. Membership and roles do not change here — manage members from the app. Returns the updated project.MemocoreMemocorePluginrequiredAI
Update Project Memoupdate · Update a memo that lives in a SHARED project (visible to, and editable by, every member). Use this to actualize or merge into an existing memo instead of creating a near-duplicate. Only the provided fields change, and each REPLACES the old value wholesale — so to merge, fetch the current memo first (get-memos) and send the combined `content`, not just the new fact. Passing `tags` replaces the memo's tags (this project's tags only). Editing a shared memo can leak data into the project just like creating one, so before calling you MUST scan whatever you are writing (`content` / `title` / `meta`) for personal or sensitive data (private contacts, secrets, credentials, health/financial info). If any is present, proceed only on the user's explicit confirmation. `preview` is PUBLIC (shown in search results and exposable via public share links even outside the project), so it must never contain sensitive data. Set `privacy_reviewed` to true only once that check genuinely passes. For your own private memos use update-private-memo instead. The response includes a `share_url` field: the public /m/ link if the memo is already shared, otherwise a hint. If the user wants a link, use that field (or follow the hint via set-memo-sharing); never build one from `id`. The response may carry a `recommendation` with `similar` (near-duplicate memos in this project — if any is truly the same, consolidate: merge into one, delete the extras with delete-memo, staying within this project) and `suggested_tags` (fitting project tags for this memo — add the relevant ones, especially if it has none yet).MemocoreMemocorePluginrequiredAI
Update Tagupdate · Update a tag the authenticated user can access — their own private tag, or a tag of a project they belong to. Only the provided fields are changed.MemocoreMemocorePluginrequiredAI
Whoamiwhoami · Return the profile of the memocore account this MCP connection is authenticated as (id, name, email, status). Use to confirm which user the AI client is acting on behalf of.MemocoreMemocorePluginrequiredAI
Archive affiliate networksarchive · Archives affiliate network(s). This tool takes a request body: you MUST call get_schema("archive_affiliate_networks") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
Archive campaignsarchive · Archives campaign(s). This tool takes a request body: you MUST call get_schema("archive_campaigns") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
Archive flowsarchive · Archives flow(s). This tool takes a request body: you MUST call get_schema("archive_flows") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
Archive landersarchive · Archives lander(s). This tool takes a request body: you MUST call get_schema("archive_landers") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
Archive offersarchive · Archives offer(s). This tool takes a request body: you MUST call get_schema("archive_offers") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
Archive traffic sourcesarchive · Archives traffic source(s). This tool takes a request body: you MUST call get_schema("archive_traffic_sources") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
Bulk create landers from CSVbulk · Creates landers from csv fileVoluumVoluumPluginrequiredMarketing
Bulk create offers from CSVbulk · Creates offers from csv fileVoluumVoluumPluginrequiredMarketing
Bulk update campaigns from CSVbulk · Updates campaigns from csv fileVoluumVoluumPluginrequiredMarketing
Bulk update landers from CSVbulk · Updates landers from csv fileVoluumVoluumPluginrequiredMarketing
Bulk update offers from CSVbulk · Updates offers from csv fileVoluumVoluumPluginrequiredMarketing
Check custom domain statusvalidate · Validate custom domainsVoluumVoluumPluginrequiredMarketing
Check whether any affiliate network existsany · Checks if at least one affiliate network has been created.VoluumVoluumPluginrequiredMarketing
Check whether any campaign existsany · Checks if at least one campaign has been created.VoluumVoluumPluginrequiredMarketing
Check whether any flow existsany · Checks if at least one flow has been created.VoluumVoluumPluginrequiredMarketing
Check whether any lander existsany · Checks if at least one lander has been created.VoluumVoluumPluginrequiredMarketing
Check whether any offer existsany · Checks if at least one offer has been created.VoluumVoluumPluginrequiredMarketing
Check whether any traffic source existsany · Checks if at least one traffic source has been created.VoluumVoluumPluginrequiredMarketing
Clear integration mappingsclear · Clear all manual mappings for an integration and reset its execution infoVoluumVoluumPluginrequiredMarketing
Count event log entriesget · Retrieves number of event log entries. Event log enables you to browse changes that were made in your account.VoluumVoluumPluginrequiredMarketing
Create affiliate networkcreate · Creates an affiliate network. This tool takes a request body: you MUST call get_schema("create_affiliate_network") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
Create campaigncreate · Creates a campaign. A campaign must belong to a workspace. Although `workspace` is optional in the request schema, set `workspace.id` to a workspace id from the account's session context (`get_session_context` — omitting it fails with WORKSPACE_VALIDATION_ERROR ('Workspace not valid'). The workspace must also be consistent with the entities the campaign references (traffic source, flow, offers, landers): a campaign in one private workspace cannot reference entities in a different private workspace. This tool takes a request body: you MUST call get_schema("create_campaign") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
Create custom columnscreate · Creates a custom columns configuration This tool takes a request body: you MUST call get_schema("create_custom_column") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing
Create flowcreate · Creates a flow. This tool takes a request body: you MUST call get_schema("create_flow") and build the body to match it before calling — do not guess fields.VoluumVoluumPluginrequiredMarketing

Tool Explorer FAQ

What is Tool Explorer?

Tool Explorer indexes the callable tool names and descriptions attached to public registry profiles. It is useful for seeing what agents can actually invoke, not just which profile exists.

How do category and verb filters work?

Category filters use the live registry category rollup. Verb filters use the public tool insights rollup, so the page stays backed by the same read models as the tracker charts.

Why do auth requirements matter?

Auth requirements show whether a tool is likely usable without account connection, requires authentication, is private, or is unknown in the current snapshot.