Summary
Two tools, and the second is what makes the first precise.
list_integrations returns the values the integrations filter on list_servers accepts, so the sequence that works is read them, then filter — rather than guessing at a label and getting an empty page. What you get is a directory search: whether a server already exists for some system, answered inside the session instead of in a browser tab, which is the moment the question actually comes up.
What it is
A two-tool lookup over the PulseMCP directory: servers with filtering and paging, and the integration list that supplies the filter values.
What you get
- list_servers with a free-text query, an integrations filter, a per-page count and an offset
- list_integrations, returning every integration available as a filter value
Requirements
Nothing — no account, no key.
Setup effort
One command — npx -y pulsemcp-server
