API reference / Apps
List the custom apps
The apps that this workspace added itself: remote MCP servers, each with its tools and the mode of each tool. Teammates call a tool with call_app_tool. A tool in the mode ask waits for the yes of an owner or admin. No key or token ever comes out.
/api/v1/custom-appsOther ways to call it
troopy custom-apps listtroopy_list_custom_appsResponse
200 · application/jsondata*array<object>12 properties
slug*stringThe id of the app, made from its name, as in acme_crm
name*stringkind*enum<string>A remote MCP server, or an OpenAPI document (Liquid SaaS)
mcpopenapi
url*stringThe Streamable HTTP address of its MCP server
auth*enum<string>How Troopy signs in: nothing, a key in a header, or the sign-in of the server
nonekeyoauth
status*enum<string>connectedneeds_sign_infailed
error*string | nulltools*array<object>5 properties
name*stringdescription*stringmode*enum<string>free: it runs. ask: it waits for the yes of an owner or admin. off: no teammate calls it
freeaskoff
args*array<string>The top-level arguments of the tool
visitor*string | nullThe argument that takes the email of a visitor of the website. Then the Support agent calls the tool for a visitor that the website proved, and Troopy fills that argument in. Null: the Support agent never calls it
listedAt*string | nullWhen an owner or admin last read its tools
connectedBy*objectWho wrote it
3 properties
type*enum<string>personagentapi
id*stringname*stringconnectedAt*stringISO 8601 date and time
signIn*string | nullThe page that starts the sign-in of the server, while it waits for one. A person opens it