> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/mcp-and-ai-reference/tools/credentials-search.md).

# credentials\_search — Find connection records

**Declared contract — reviewed 21 October 2026.** This page describes the tool exposed by the Autom Mate New connection in the inspected 71-tool profile. It does not establish support on every build or prove runtime success. Check the active connection and [installed product version](https://docs.autommate.com/userguide/start-here/documentation-scope-and-product-versions.md). Historical examples retain their original observation dates. Logical tool names may have a client-specific namespace prefix.

Find stored application-connection records, such as their names, application and active flag. This tool returns metadata, not secrets, and does not test connectivity.

## Declared request signature

The following is the exposed 21 October declaration; request types do not define an exhaustive response schema.

```ts
declare const tools: { mcp__codex_apps__autom_mate_new_credentials_search(args: { application?: string; cursor?: string; only_active?: boolean; page_size?: number; query?: string; status?: "active" | "inactive"; }): Promise<CallToolResult>; };
```

## Parameters

| Parameter     | Type                   | Required | Meaning                                                                                                                                                  |
| ------------- | ---------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `application` | string                 | No       | Application filter.                                                                                                                                      |
| `query`       | string                 | No       | Connection search.                                                                                                                                       |
| `only_active` | boolean                | No       | Optional active-record filter declared by this connection; precedence if combined with `status` is not documented, so do not supply conflicting filters. |
| `status`      | `active` or `inactive` | No       | Stored-record status filter.                                                                                                                             |
| `page_size`   | number                 | No       | Requested page size.                                                                                                                                     |
| `cursor`      | string                 | No       | Returned pagination cursor.                                                                                                                              |

## Minimal request

Replace the search placeholder with the stored connection name. Do not put a password, token or API key into the query.

```json
{
  "query": "<stored connection name>"
}
```

## Read the result

* `active` describes the stored record. It does not establish that authentication to the destination currently succeeds.
* A `scope_note` can restrict results to connections created by the caller. No visible match does not establish that no connection exists for another user or tenant.
* For an action's test credential, filter by application and let the user select or confirm the returned connection. Keep an already-set credential. A Work Item's runtime credential uses an App Connector input variable referenced by `sys_app_connector_input`; choose the runtime tenant credential through `deployments_list_credentials`, not this general search.
* Use actual execution-error evidence when investigating a connection problem. Connection metadata alone cannot prove an expired token, invalid password or remote outage.
* For another page, keep the same filters and pass the returned cursor unchanged. Treat the cursor as opaque; stop when no continuation is returned. The first page need not be the complete result set.

## Permissions and retries

Read-only metadata lookup within the caller's permitted scope. Do not request or expose secrets to compensate for a missing record. An access refusal is not an empty connection list. Repeating this read cannot validate destination authentication.

## Present a requested result

When the user asked to see this result, pass the returned `result_ref` to `show_result` once for the final requested answer. Do not show cards for intermediate lookups. A result reference expires after 15 minutes; read again if it has expired. This presentation step neither executes nor verifies a business action.

## Continue

* Next tools: [`runs_get_latest_error`](https://docs.autommate.com/userguide/mcp-and-ai-reference/tools/runs-get-latest-error) · [`automs_search`](https://docs.autommate.com/userguide/mcp-and-ai-reference/tools/automs-search).
* Workflow: [Discovery tool contracts](https://docs.autommate.com/userguide/mcp-and-ai-reference/discovery-tool-contracts.md).
* Worked reference: [Read discovery results and pagination](https://docs.autommate.com/userguide/mcp-and-ai-reference/read-discovery-results-and-pagination.md).
* [MCP tool reference](https://docs.autommate.com/userguide/mcp-and-ai-reference/tools).
