Cats

@Cats list all portals in my account, sorted by creation date

Found 12 portals across your account. Most recent: 'Production Dashboard' (created 2024-01-15, 847 views), 'API Docs v2' (created 2024-01-10, 1,203 views), 'Team Onboarding' (created 2023-12-18, 456 views). Older portals include 'Legacy Admin Panel', 'Customer Support Hub', and 'Analytics Sandbox'. All portals are currently active. This represents page 1 of 1 — your account holds fewer than 50 portals, so pagination isn't required here.

This example shows the MCP's core read capability: fetching portal metadata with pagination support. Requires a valid API key with read access to portal resources. The tool returns metadata only — it won't fetch portal content or configuration details beyond what's in the list view.

@Cats show me the 5 most-viewed portals from the last 30 days

Top 5 portals by views (last 30 days): 'API Docs v2' leads with 1,203 views, followed by 'Production Dashboard' (847 views), 'Team Onboarding' (456 views), 'Customer Support Hub' (312 views), and 'Analytics Sandbox' (289 views). Note that view counts reflect the portal's lifetime total — the MCP lists all portals but doesn't filter by date range natively, so this ranking assumes recent activity correlates with total views.

Demonstrates how the AI can synthesize portal metadata into a ranked summary. The MCP's list tool doesn't support date-range filtering or view-count sorting directly, so the AI must infer relevance from available fields. If your account has 50+ portals, pagination may truncate results — request multiple pages explicitly.

@Cats find any portals with 'staging' or 'test' in the name and tell me if they're still active

Located 3 portals matching 'staging' or 'test': 'Staging API Docs' (created 2023-11-20, active, 89 views), 'Test Environment Dashboard' (created 2023-10-05, active, 34 views), and 'QA Testing Portal' (created 2023-09-12, active, 12 views). All three remain active in your account. Consider archiving low-traffic test portals if they're no longer in use — the MCP can't deactivate portals directly, but it surfaces the metadata you need to audit them manually.

Shows the AI filtering portal lists by name pattern and interpreting status fields. The MCP provides read-only access — it won't modify or delete portals. If your naming convention differs ('dev', 'sandbox'), adjust the prompt accordingly. Pagination applies if you have many portals; the AI will note if results are incomplete.

When you need a quick portal inventory across customer accounts

A 6-person SaaS ops team runs quarterly audits to confirm which customer portals are still active and which configs have drifted. The Cats MCP gives you one tool—Get Portals—that lists all portals with pagination, so you can pull metadata into a shared workspace and spot-check against your billing system. This works if your portal count stays under a few hundred and you're not doing real-time monitoring. If you need to drill into portal settings or trigger actions beyond listing, you'll hit the tool's ceiling fast. For a quarterly or monthly sweep where the goal is 'show me what exists', this MCP keeps the workflow in one place without writing a custom script.

Cats MCP is too narrow for onboarding documentation tasks

A 3-person startup wants new engineers to review the full list of customer portals during their first week to understand the product surface area. The Cats MCP can fetch that list, but onboarding typically needs more context—portal usage stats, recent tickets, or config examples—and this MCP only exposes the metadata browse. You'd end up switching to another tool or API for the rest of the checklist. If your onboarding doc is literally 'here are the portal names and IDs', this works. If you need any follow-up action or enrichment, plan to supplement with a different integration or skip Cats entirely and use a direct API call in your runbook.

Use Cats MCP when portal lookup is the first triage step

A 4-person support team fields tickets where the customer references a portal by name, and the agent needs to confirm it exists before escalating. The Cats MCP's Get Portals tool lets the agent search the full portal list in Switchy without opening a separate admin panel. This shaves 30 seconds per ticket if your portal naming is consistent and the list fits in a paginated response. The trade-off: if you need to see portal health, recent activity, or user counts, the MCP stops short and you're back to the vendor dashboard. For pure existence checks and metadata lookups during triage, this MCP keeps the flow in one workspace and cuts the tab-switching tax.