App Management and Pairing

Ansight Studio MCP tools for known app registration, linked app metadata, and signed pairing config management.

Use these Ansight Studio-owned MCP tools when an agent needs to understand which apps Ansight Studio knows about, create a new app entry, or manage the signed pairing configs used by development builds.

These tool names are the MCP tools/call names exposed by Ansight Studio.

Tool	Capability
`ansight_list_apps`	List apps known to Ansight Studio, including linked codebases and live session counts.
`ansight_get_app`	Return one app known to Ansight Studio, including linked codebase, counts, and last-seen metadata.
`ansight_register_app`	Register a new app entry in Ansight Studio so it can be tracked, linked to a codebase, and used for pairing config issuance.
`ansight_issue_pairing_config`	Issue a new signed, expiring pairing config for an app.
`ansight_list_pairing_configs`	List cached pairing configs known to Ansight Studio, optionally filtered by app and status.
`ansight_get_pairing_config`	Return one cached pairing config.

Typical Use

Use this group at the start of a workflow:

Call ansight_list_apps or ansight_get_app to find the app entry.
Call ansight_register_app if the app has not been registered yet.
Call ansight_issue_pairing_config for a short-lived pairing config.
Use ansight_list_pairing_configs or ansight_get_pairing_config to inspect cached config state.

Pairing configs are local Ansight Studio records. They are meant for development and internal testing workflows, not public release builds.