Wildcard Search and Saved Views

The MCP Servers, Agent Cards, and REST APIs lists share the same filter bar. Two features on that bar let you find assets fast and keep a filtered slice around for later: wildcard search (match names and descriptions with *) and saved views (store the current search and filters under a name and share it with your organization).

Both work identically on all three list pages. Wildcard search is also available through the platform MCP search_* tools.

Overview

The filter bar sits above every asset list. Its first row is a full-width search box; the second row holds the Type, Status, Published to, and Sort controls, followed by the Reset, Views, and Save view controls.

Wildcard search filters the list as you type, matching each asset’s name and description.
Saved views capture the search string plus every filter and sort selection as a named view. Views are stored per organization and shared with every member, so a teammate opening the same list sees the same views you saved.

The most common use is a repeatable, shareable scoped demo — for example, showing only the Cartier -CAR assets during a walkthrough.

Wildcard search

Type into the search box to filter the list. The placeholder tells you which list you are on — Search servers..., Search agent cards..., or Search APIs.... Matching is case-insensitive and runs against both the asset name and its description.

How matching works

No wildcard — a plain term is a contains match. weather matches Weather API and Global weather service.
With * — the * stands for “any run of characters”, and the pattern must match the name or description end to end. scr-* matches only strings that start with scr-.

* is the only wildcard character. A ? (or any other character) is matched literally, not as a wildcard.

Adding a * anchors the pattern to the whole string. A plain scr matches description (it appears somewhere inside), but scr-* matches only assets whose name or description begins with scr-. Use a plain term for “contains anywhere” and wildcards for “starts / ends / spans”.

Wildcard examples

You type	Matches	Meaning
`scr-*`	`scr-weather`, `scr-CAR-001`	Starts with `scr-`
`*-CAR`	`weather-CAR`, `orders-CAR`	Ends with `-CAR`
`risk`	`risk-engine`, `high-risk-api`	Contains `risk`
`weather*api`	`weather-api`, `weather-forecast-api`	Starts with `weather`, ends with `api`
`weather`	`Weather API`, `Global weather service`	Contains `weather` (no wildcard)

Wildcard search via the platform MCP tools

The same wildcard syntax is available through the platform MCP search_* tools, which search by name or description:

search_mcp_servers
search_agent_cards
search_rest_apis

Each accepts a query string where * acts as a wildcard, for example:

{ "query": "*-CAR" }

The tool descriptions summarize the syntax as:

Supports * wildcards: scr-* (starts with), *-CAR (ends with), *risk* (contains).

The list_mcp_servers, list_agent_cards, and list_rest_apis tools take no query — they return every asset ordered by name. Use the search_* tools when you want to filter with a wildcard.

Saved views

A view captures the current state of the filter bar so you can re-apply it in one click. Views are scoped to a single list (MCP servers, agent cards, or REST APIs) and shared with everyone in your organization.

What a view captures

The search query (including any * wildcards)
The Type filter
The Status filter (Draft / Published)
The Published to filters (A2L, Exchange)
The Sort order (name, newest, oldest)

Saving a view

Set the search and filters you want to keep.
Open the Save view dropdown and choose Save as new….
In the Save current view dialog, enter a name (for example, Cartier demo) and click Save.

View names are 1–120 characters and must be unique within that list. Saving a duplicate name shows “A view with this name already exists” — pick another name or overwrite the existing view instead.

To update a view you already applied, open Save view and choose Save “<view name>” — this overwrites that view in place with the current search and filters.

Applying a view

Open the Views dropdown (it shows the number of saved views, e.g. Views (3)) and click a view to apply its search and filters. The active view’s name appears on the dropdown trigger, and a checkmark marks it in the list.

To clear everything, click Reset (which clears the search and all filters) or pick None (clear filters) from the top of the Views dropdown.

Setting a default view

Each list can have one default view per organization. In the Views dropdown, click the star next to a view to set it as the default (click again to unset). When a default is set, it is applied automatically the next time someone opens that list with no search or filters active. If no default is set, the list opens unfiltered.

Deleting a view

In the Views dropdown, click the trash icon next to a view to delete it. Because views are shared, deleting one removes it for everyone in your organization.

Views are shared across your organization

Saved views are stored per organization, not per user. Any member of your organization can apply, overwrite, set as default, or delete any view on that list, and views persist across sessions and devices. This is what makes them useful for a repeatable, shareable scoped demo: save *-CAR as Cartier demo once, and every teammate can open that exact slice from the Views dropdown.

Next Steps

Search once, save the view, and hand your whole team the same scoped slice in a single click.

Creating Your First MCP Server Protocol Tester