App requests and toolkit types

App Requests and Toolkits are two separate controls over what members can reach: which catalog applications a project is allowed to use, and which toolkit types exist on the deployment at all.

Decide an app request

A member who opens the application catalog and requests access to something their project is not configured for creates a row here — separate from the agent/skill publishing review, which is a different mechanism entirely.

1. Open App Requests

   The queue lists pending requests with who asked and for what.

2. Approve or reject

   Both record your decision and notify the requester in the same transaction.

Warning

Approving a request records the decision and tells the requester — it does not itself grant anything. Nothing in the platform reads an approved row and automatically unlocks a capability; whether the requested application actually becomes usable depends on whether its toolkit type is enabled for that project, below.

Control which toolkit types are offered

Open Toolkits. This decides, per toolkit type, whether it is enabled, disabled, or restricted to named projects — always with a reason and a recorded decider.

1. Find the type

   The table lists every catalogue type with its current availability and a worker-support indicator.

2. Change its availability

   Choose enabled, disabled, or restricted; a restricted type also lists which projects can use it. A reason is required for every choice except reverting to the default.

With no rows, every type is offered. To make the catalogue default-deny, set Configuration › Connector Catalogue › Mode to approved_only: a toolkit type or MCP server is then usable only after a connector request is approved under Connector requests, and approval writes the type’s availability for the requested projects. See Connector approval.

Note

This page does not add a new toolkit type. A pre-built MCP server becomes a type through Configuration’s MCP Servers section, and an external provider’s toolkits would arrive through Service Descriptors — a third registration path here would be a third thing to keep synchronized.

Warning

The worker column is advisory: it reports whether the toolkit type is known to run on the platform’s agent worker (the native Rust runtime), not whether the type is disallowed. A type the worker cannot build shows Unverified with the server’s reason beside it — tracked in #865. See the toolkit catalogue for which types run.