Back to tracker
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
- Search Finnish Lobbied Targetsfi · Search the officials and bodies actually lobbied in the Finnish Transparency Register (derived from filed disclosures), by name or organization, with optional target_group or party filters. Returns targets ranked by how often they were contacted, with how many distinct organizations lobbied them. Use to find who is being lobbied, then fi_get_target or fi_get_target_lobbyists. NOTE: distinct from fi_search_officials, the static directory of registrable targets — this tool reflects who was actually contacted. Note: this register is Finnish-language — free-text search terms must be in Finnish to match. If the user wrote in another language, do not silently search: give your best-guess Finnish translation of the search term, ask the user to confirm or correct it, then search with the confirmed Finnish wording.Policy DoctorPolicy Doctor
PluginrequiredOperations - Search Finnish Lobbying Contactsfi · Search individual Finnish lobbying contacts (one row per official/body contacted about one topic). Filter by topic text (query/topic), organization (id or name), or target name. Returns the org, the reporting_period_id + label, the topic, the target contacted, and the communication methods used. Use fi_get_disclosure for the full filing a contact belongs to.
Reporting periods: the register splits the year into two six-month terms (Jan–Jun, Jul–Dec). To scope by activity period, pass reporting_period_id (resolve a half-year to its term_id via fi_list_reporting_periods). IMPORTANT: the from/to filter is the FILING date (disclosure_date), which lags the activity — Jan–Jun activity is filed Jul–Aug and Jul–Dec activity the following Jan–Feb — so do NOT use from/to to scope by period; use reporting_period_id instead. Note: this register is Finnish-language — free-text search terms must be in Finnish to match. If the user wrote in another language, do not silently search: give your best-guess Finnish translation of the search term, ask the user to confirm or correct it, then search with the confirmed Finnish wording.Policy DoctorPolicy DoctorPluginrequiredOperations
- Search Finnish Lobbying Officials Directoryfi · Search the DIRECTORY of registrable Finnish lobbying targets — officials and bodies that can be lobbied (organization, department, unit, job title, party, parliamentary term) — by keyword, with optional term/term_ongoing filters. This is the curated reference list; for who was ACTUALLY lobbied (from filed disclosures) use fi_search_targets instead. Finnish register only; distinct from the eu_* tools. Note: this register is Finnish-language — free-text search terms must be in Finnish to match. If the user wrote in another language, do not silently search: give your best-guess Finnish translation of the search term, ask the user to confirm or correct it, then search with the confirmed Finnish wording.Policy DoctorPolicy DoctorPluginrequiredOperations
- Search Finnish Lobbying Organizationsfi · Search the FINNISH Transparency Register for organizations registered as lobbying actors (companies, consultancies, unions, NGOs, trade bodies) by name or business_id (Y-tunnus); optionally filter by primary industry, classification, role, or a minimum number of disclosures. Returns ranked summaries — classification, a derived lobbying_role, disclosure/contact volume, distinct targets contacted — most active first. role/lobbying_role is derived from the registry classification: "consultancy" (declared lobbying for paying clients), "in_house" (a company lobbying for itself), "association" (trade/employee/other org), or "unknown" — note this is a classification, not a self-declaration, so it can be imprecise for edge entities. Use to discover or shortlist organizations, then fi_get_organization for the full profile. Finnish register only; distinct from the eu_* tools. Every row includes source_url — the organization's public avoimuusrekisteri.fi registration page (null if the org is not in the register); cite it so users can verify the data. Note: this register is Finnish-language — free-text search terms must be in Finnish to match. If the user wrote in another language, do not silently search: give your best-guess Finnish translation of the search term, ask the user to confirm or correct it, then search with the confirmed Finnish wording.Policy DoctorPolicy DoctorPluginrequiredOperations
- Create or update objectupsert · Create or update an object in a specific collection. Objects are used to model custom collections in Knock that are NOT users or tenants. If the object does not exist, it will be created. If the object exists, it will be updated with the provided properties. The update will always perform an upsert operation, so you do not need to provide the full properties each time.
Use this tool when you need to create a new object, or update an existing custom-object. Custom objects can be used to subscribe users' to as lists, and also send non-user facing notifications to.KnockKnockPluginrequiredMarketing
- Create or update tenantupsert · Creates or updates a tenant using the properties provided. Tenants in Knock are used to model organizations, teams, and other groups of users. They are a special type of object.
Use this tool when you need to create a new tenant, or update an existing tenant's properties.KnockKnockPluginrequiredMarketing
- Create or update userupsert · Creates a new user if they don't exist, or updates the user object for the given userId, including email, name, phone number, and any custom properties.
Use this tool when you need to update a user's profile.
If the userId is not provided, it will use the userId from the config.KnockKnockPluginrequiredMarketing
- Execute MAPI (read)execute · This is the Management API: workflows, channels, templates, commits, and configuration.
This session allows **read and write**. Use `execute_mapi_read` for `GET` and `execute_mapi_write` for `POST`/`PUT`/`PATCH`/`DELETE`.
Use this tool (Code Mode: `execute_mapi_read`) for **read-only** `MAPI` calls at https://control.knock.app via `mapi.request({ method: "GET", ... })`. Use `search_mapi` first to find paths and request shapes. Auth headers are added on the host. For create/update/delete, use `execute_mapi_write` instead.
**mapi.request() response shape:** does NOT return the API JSON body directly. It wraps it:
```json
{ "status": 200, "ok": true, "result": { /* actual API response body */ } }
```
Always read API fields from `res.result`, not from `res` (e.g. `res.result.entries`, not `res.entries`).
When the user asks for the "exact result," return the full `mapi.request(...)` value unless they ask for a projection.
Types:
interface RequestOptions {
method: "GET";
path: string;
query?: Record<string, string | number | boolean | undefined>;
headers?: Record<string, string>;
}
/** Wrapper returned by mapi.request() — the API body is in `result`, not at the top level. */
interface RequestResponse {
status: number;
ok: boolean;
result: unknown;
}
declare const mapi: { request(options: RequestOptions): Promise<RequestResponse> };
Your code must be a single JavaScript async arrow function (no TypeScript).
Example:
async () => {
const res = await mapi.request({
method: "GET",
path: "/v1/workflows",
query: { environment: "development" },
});
return { status: res.status, entries: res.result.entries, page_info: res.result.page_info };
}KnockKnockPluginrequiredMarketing
- Execute MAPI (write)execute · This is the Management API: workflows, channels, templates, commits, and configuration.
This session allows **read and write**. Use `execute_mapi_read` for `GET` and `execute_mapi_write` for `POST`/`PUT`/`PATCH`/`DELETE`.
Use this tool (Code Mode: `execute_mapi_write`) for **write** `MAPI` calls at https://control.knock.app via `mapi.request({ method: "POST"|"PUT"|"PATCH"|"DELETE", ... })`. Use `search_mapi` first to find paths and request shapes. Auth headers are added on the host. For `GET`, use `execute_mapi_read` instead.
**mapi.request() response shape:** does NOT return the API JSON body directly. It wraps it:
```json
{ "status": 200, "ok": true, "result": { /* actual API response body */ } }
```
Always read API fields from `res.result`, not from `res` (e.g. `res.result.entries`, not `res.entries`).
When the user asks for the "exact result," return the full `mapi.request(...)` value unless they ask for a projection.
Types:
interface RequestOptions {
method: "POST" | "PUT" | "PATCH" | "DELETE";
path: string;
query?: Record<string, string | number | boolean | undefined>;
body?: unknown;
contentType?: string;
rawBody?: boolean;
headers?: Record<string, string>;
}
/** Wrapper returned by mapi.request() — the API body is in `result`, not at the top level. */
interface RequestResponse {
status: number;
ok: boolean;
result: unknown;
}
declare const mapi: { request(options: RequestOptions): Promise<RequestResponse> };
Your code must be a single JavaScript async arrow function (no TypeScript).
Example:
async () => {
const res = await mapi.request({
method: "PUT",
path: "/v1/workflows/welcome",
query: { environment: "development" },
body: { name: "Welcome", steps: [] },
});
return { status: res.status, result: res.result };
}KnockKnockPluginrequiredMarketing
- Get Knock agent statusget · Poll an in-progress Knock agent session and return a consolidated result (agent text, tool calls, modified resources, and a Status line).
When to use:
- After start_knock_agent returns Status: running.
- When resuming after an MCP disconnect (you still have the session_id).
How to use:
1. Call with the session_id from start_knock_agent (or a prior get_knock_agent).
2. Read the Status line in the tool result — you do not parse raw events; the server consolidates them for you.
3. If Status is running, wait a few seconds and call get_knock_agent again with the same session_id.
4. If Status is complete, the run succeeded — use the agent response.
5. If Status is error, the run failed — read the Error line.
The Knock agent keeps running on the backend between your polls; each call is short-lived.KnockKnockPluginrequiredMarketing
- Get messageget · Retrieves a single message by its ID, including its current status and engagement statuses (e.g. seen, read, interacted, link_clicked). Use this tool when you need to check the delivery status or engagement state of a specific message.KnockKnockPluginrequiredMarketing
- Get message contentget · Retrieves the complete contents of a single message, specified by the messageId. The message contents includes the rendered template that was sent to the recipient. Use this tool when you want to surface information about the emails, SMS, and push notifications that were sent to a user.KnockKnockPluginrequiredMarketing
- Get message delivery logsget · Retrieves the delivery logs for a specific message. Delivery logs contain details about each delivery attempt, including any errors that occurred. Use this tool when you need to debug why a message was not delivered or to inspect delivery attempt details.KnockKnockPluginrequiredMarketing
- Get message eventsget · Retrieves the event timeline for a specific message. Events include delivery, bounce, open, click, and other engagement events. Use this tool when you need to see the full lifecycle of a message.KnockKnockPluginrequiredMarketing
- Get objectget · Get an object wihin a collection. Returns information about the object including any custom properties. Use this tool when you need to retrieve an object to understand it's properties.KnockKnockPluginrequiredMarketing
- Get tenantget · Retrieves a tenant by their ID. Tenants in Knock are used to model organizations, teams, and other groups of users. They are a special type of object.
Use this tool when you need to lookup the information about a tenant, including name, and if there are any custom properties set.KnockKnockPluginrequiredMarketing
- Get userget · Retrieves the complete user object for the given userId, including email, name, phone number, and any custom properties. Use this tool when you need to retrieve a user's complete profile.
If the userId is not provided, it will use the userId from the config.KnockKnockPluginrequiredMarketing
- Get user messagesget · Retrieves the messages that this user has received from the service. Use this tool when you need information about the notifications that the user has received, including if the message has been read, seen, or interacted with. This will return a list of messages across all of the channels.
If the userId is not provided, it will use the userId from the config.KnockKnockPluginrequiredMarketing
- Get user preferencesget · Retrieves the user's notification preferences for the given userId.
If the userId is not provided, it will use the userId from the config.KnockKnockPluginrequiredMarketing
- List environmentslist · Lists all environments available, returning the slug and name of each environment. Use this tool when you need to see what environments are available.KnockKnockPluginrequiredMarketing
- List objectslist · List all objects in a single collection. Objects are used to model custom collections in Knock that are NOT users or tenants. Use this tool when you need to return a paginated list of objects in a single collection.KnockKnockPluginrequiredMarketing
- List tenantslist · Retrieves a list of tenants. Tenants in Knock are used to model organizations, teams, and other groups of users. They are a special type of object.
Use this tool when you need to list all tenants in an environment.KnockKnockPluginrequiredMarketing
- Search MAPI OpenAPIsearch · This is the Management API: workflows, channels, templates, commits, and configuration.
This session allows **read and write**. Use `execute_mapi_read` for `GET` and `execute_mapi_write` for `POST`/`PUT`/`PATCH`/`DELETE`.
Use `search_mapi` to explore or filter the OpenAPI spec for the **mapi** API before calling `execute_mapi_read` or `execute_mapi_write`. All $ref pointers are pre-resolved inline.
Types:
// OpenAPI 3.x spec with $refs resolved inline.
interface OperationObject {
summary?: string;
description?: string;
operationId?: string;
tags?: string[];
parameters?: Array<{
name: string;
in: "query" | "header" | "path" | "cookie";
required?: boolean;
schema?: unknown;
description?: string;
}>;
requestBody?: { required?: boolean; content?: Record<string, { schema?: unknown }> };
responses?: Record<string, { content?: Record<string, { schema?: unknown }> }>;
}
interface PathItem {
get?: OperationObject; post?: OperationObject; put?: OperationObject;
patch?: OperationObject; delete?: OperationObject;
}
interface OpenApiSpec {
openapi: string;
info: { title: string; version: string; description?: string };
paths: Record<string, PathItem>;
servers?: Array<{ url: string }>;
components?: Record<string, unknown>;
tags?: Array<{ name: string; description?: string }>;
}
declare const mapi: { spec(): Promise<OpenApiSpec> };
Your code must be a single JavaScript async arrow function (no TypeScript) that returns a small, filtered result.
Example:
async () => {
const spec = await mapi.spec();
return Object.keys(spec.paths).slice(0, 20);
}KnockKnockPluginrequiredMarketing
- Search documentationsearch · Search the Knock documentation for a given queryKnockKnockPluginrequiredMarketing
- Set user preferencesset · Overwrites the user's notification preferences for the given userId. Allows setting per-workflow, per-category, or per-channel notification preferences. Use this tool when you are asked to update a user's notification preferences.
If the userId is not provided, it will use the userId from the config.
Instructions:
- You must ALWAYS provide a full preference set to this tool.
- When setting per-workflow preferences, the key in the object should be the workflow key.
- Workflow and category preferences should always have channel types underneath.
- The channel types available to you are: email, sms, push, chat, and in_app_feed.
- To turn OFF a preference, you must set it to false.
- To turn ON a preference, you must set it to true.
<examples>
<example>
<description>
Update the user's preferences to turn off email notifications for the "welcome" workflow.
</description>
<input>
{
"workflows": {
"welcome": {
"channel_types": {
"email": false
}
}
}
}
</example>
</examples>KnockKnockPluginrequiredMarketing
- Start Knock agentstart · Use Knock's hosted agent to create and update workflows, broadcasts, guides, email layouts, partials, and translations.
Prefer this tool when creating or updating those resources in a Knock account — the hosted agent has full account context and usually needs fewer tokens than calling the Management API directly. Use Management API code mode (`search_mapi` / `execute_mapi_read` / `execute_mapi_write`) when you need a specific API call, or when the user asks to use the API.
For analytics questions, the Knock agent can return high-level message and engagement data. Those queries are not available through the Management API.
Pass the user's request verbatim in prompt. Do not reinterpret or shorten it.
This tool waits up to ~45 seconds, then returns a consolidated result. Read the Status line in the response:
- Status: complete — the run finished; use the agent response and modified resources.
- Status: error — the run failed; read the Error line.
- Status: running — the run is still going; save the Session ID and poll with get_knock_agent until Status is complete or error.
Agents can support follow-up runs by passing in the returned session_id. Use a follow-up run only for related edits or questions about a resource you just modified. Otherwise, use the Management API or start a new agent session.KnockKnockPluginrequiredMarketing
- Subscribe users to objectsubscribe · Subscribe a list of users to an object in a specific collection. We use this to model lists of users, for pub-sub use cases.
Use this tool when you need to subscribe one or more users to an object where you will then trigger workflows for those lists of users to send notifications to.
Before using this tool, you should create the object in the collection using the createOrUpdateObject tool.KnockKnockPluginrequiredMarketing
- Unsubscribe users from objectunsubscribe · Unsubscribe a list of users from an object in a specific collection. We use this to model lists of users, for pub-sub use cases.
Use this tool when you need to unsubscribe one or more users from an object where you will then trigger workflows for those lists of users to send notifications to.KnockKnockPluginrequiredMarketing
- Connector howtoget · Return easy setup steps for connecting LegalScout in Claude, ChatGPT, or Gemini, plus a website snippet firms can publish so visitors ask the LLM to find them.LegalScoutLegalScoutPluginnoneOperations
- Consult with associateconsult · Talk to a firm's prospect AI associate in this chat (text intake). Pass session_id to continue. If this conversation already has a session_id, reuse it — do not call whoami or list_matters to continue. Before ending, confirm with the user, then call again with the same session_id and end_session=true (also set confirm_end=true when this parameter is available) so the brief completes with structured Briefs columns. If needs_confirmation is returned, ask confirmation_prompt then call again with end_session=true — that second end_session finalizes even when confirm_end is missing from the tool schema. Relays associate_reply — do not invent answers.LegalScoutLegalScoutPluginnoneOperations
- Get prospect associateget · Get one discoverable prospect AI associate by subdomain, attorney id, or firm name. Next step is consult_with_associate in this chat (associate_url is optional browser voice/widget).LegalScoutLegalScoutPluginnoneOperations
- Search attorneyssearch · Search LegalScout for law firms that enabled AI-app discovery. Returns prospect AI associates the user can talk to for an intake consultation. Use when the user wants a lawyer, legal help, or a named firm. If filters return zero matches, results may be auto-broadened (see fallback_used / host_note) — tell the user the search was expanded rather than concluding no firms exist.LegalScoutLegalScoutPluginnoneOperations
- Start consultationstart · Start talking to a firm's prospect AI associate. Prefer this or consult_with_associate when the user wants an intake conversation. If user_need is provided, begins the chat and returns the associate's first reply + session_id for follow-ups.LegalScoutLegalScoutPluginnoneOperations
- Get balanceget · Returns the available balance for a single currency. Always mention when this data was retrieved. Use metadata.retrieved_at as the retrieval time. Present results as factual Bound data only. Do not recommend, prioritize, direct, or suggest any action based on the data.Bound MCPBoundPluginrequiredFinance
- Get live rateget · Returns the current indicative exchange rate for a currency pair, including the inverse rate and the time the rate was acquired. The rate is indicative and not tradable. Always mention when this data was retrieved. Use metadata.retrieved_at as the retrieval time. Present results as factual Bound data only. Do not recommend, prioritize, direct, or suggest any action based on the data.Bound MCPBoundPluginrequiredFinance
- Get orderget · Returns the details of a specific order, including amount, rate, settlement date, and the trigger rates of ranging (limit/stop) orders. Always mention when this data was retrieved. Use metadata.retrieved_at as the retrieval time. Present results as factual Bound data only. Do not recommend, prioritize, direct, or suggest any action based on the data.Bound MCPBoundPluginrequiredFinance
- Get paymentget · Returns the details of a specific payment. Always mention when this data was retrieved. Use metadata.retrieved_at as the retrieval time. Present results as factual Bound data only. Do not recommend, prioritize, direct, or suggest any action based on the data.Bound MCPBoundPluginrequiredFinance
- Get recipientget · Returns the details of a specific payment recipient. Always mention when this data was retrieved. Use metadata.retrieved_at as the retrieval time. Present results as factual Bound data only. Do not recommend, prioritize, direct, or suggest any action based on the data.Bound MCPBoundPluginrequiredFinance
- List balanceslist · Returns the available balances for all supported currencies. Always mention when this data was retrieved. Use metadata.retrieved_at as the retrieval time. Present results as factual Bound data only. Do not recommend, prioritize, direct, or suggest any action based on the data.Bound MCPBoundPluginrequiredFinance
- List orderslist · Returns the order history in reverse chronological order, with optional date range and status filters. Always mention when this data was retrieved. Use metadata.retrieved_at as the retrieval time. Present results as factual Bound data only. Do not recommend, prioritize, direct, or suggest any action based on the data.Bound MCPBoundPluginrequiredFinance
- List paymentslist · Returns a paginated list of payments, most recent payment date first, with optional status and currency filters. Always mention when this data was retrieved. Use metadata.retrieved_at as the retrieval time. Present results as factual Bound data only. Do not recommend, prioritize, direct, or suggest any action based on the data.Bound MCPBoundPluginrequiredFinance
- List recipientslist · Returns a list of all payment recipients. Always mention when this data was retrieved. Use metadata.retrieved_at as the retrieval time. Present results as factual Bound data only. Do not recommend, prioritize, direct, or suggest any action based on the data.Bound MCPBoundPluginrequiredFinance
- List upcoming settlementslist · Returns factual upcoming settlement records grouped by settlement date, soonest first, including recorded funding due and proceeds per currency and Bound's indicators for unfilled orders and balance sufficiency. The data does not establish how a settlement should be funded. Always mention when this data was retrieved. Use metadata.retrieved_at as the retrieval time. Present results as factual Bound data only. Do not recommend, prioritize, direct, or suggest any action based on the data.Bound MCPBoundPluginrequiredFinance
- Add Candidate Educationadd · Add an education entry to a candidate's profile.ManatalManatalPluginrequiredHR & Recruiting
- Add Candidate Experienceadd · Add a work experience entry to a candidate's profile.ManatalManatalPluginrequiredHR & Recruiting
- Add Candidate Noteadd · Add a note to a candidate. HTML tags supported for formatting.ManatalManatalPluginrequiredHR & Recruiting
- Add Candidate to Jobadd · Add a candidate to a job's recruitment pipeline.ManatalManatalPluginrequiredHR & Recruiting
- Add Contact Noteadd · Add a note to a contact. HTML tags supported for formatting.ManatalManatalPluginrequiredHR & Recruiting
- Add Job Noteadd · Add a note to a job. HTML tags supported for formatting.ManatalManatalPluginrequiredHR & Recruiting
- Add Organization Noteadd · Add a note to an organization. HTML tags supported for formatting.ManatalManatalPluginrequiredHR & Recruiting
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.