Apps and MCP
Control which apps and MCP servers members can connect, and what each action may do.
Feature Updated 19 Nov 2026What these pages control
Apps are the PandaOS apps members connect, such as Gmail or Vercel. MCP servers are outside tools members add, either from the catalog or by URL. The Apps and MCP page decides which of them members may connect, and what each single action may do. An app may be allowed while the actions that change data stay behind a question or off.
Where to find it
In the console, open Apps and MCP under Policies in the sidebar. It has two tabs: Connected apps and MCP servers. The Policy scope menu at the top switches between Whole organization and each team. Owners and admins can change it.
Choose which apps members can connect
- Open Apps and MCP. Connected apps is its first tab.
- In the Policy scope menu, choose Whole organization or a team.
- On the PandaOS Apps card, choose Allow all or Select.
Allow all includes apps added later. Switching off one app while on Allow all changes the card to Select, with every other app unchanged. - Switch each app on or off.
Optional: on the organization scope, choose Select, then click the lock to lock the list for teams. Teams can then only narrow it. - Click Publish organization, or Publish with the team's name, such as Publish Sales.
Set rules for single actions
- Click the arrow next to an app to show its actions.
- Choose Auto, Ask or Off for an action.
An action can never be looser than the Apps and integrations level on Permissions. To turn off everything that can change data, click Read-only actions only. - Optional: on the organization scope, click the lock on a rule.
Every team then gets the rule and cannot remove it. Teams can still make the action stricter. - Publish the scope.
On a team, rules are shared
A team's action rules are one list for apps and MCP servers. See Set team overrides.
Choose which MCP servers members can connect
- Open Apps and MCP, then the MCP servers tab.
- On Catalog servers, choose Allow all or Select, and switch servers on or off.
- Optional: click the arrow next to a server and set Auto, Ask or Off for its tools.
To cover tools by name, use Add a rule by name or pattern, for example*migration*. A new pattern starts on Off. - Publish the scope.
Set rules for your organization's servers
Under "Your organization's servers", the tab lists the MCP servers you published on the MCP tab of the Library. That is also where you set who gets each one. Here you set what its tools may do, the same way as for catalog servers.
Allow custom servers
- On the MCP servers tab, under "Outside the catalog", switch on Custom servers.
These are servers members add by URL. They are off until you publish. - Under Allowed custom servers, choose Any server or Only matching.
- For Only matching, choose URL, Name or Command, enter a pattern and click Add.
A server must match every part of one pattern.*matches anything. A command must match word for word, with no extra arguments. With no pattern, no custom server is allowed. - Publish the scope.
Locked patterns replace team patterns
When the organization locks its patterns for teams, they replace every team's patterns rather than narrowing them.
What members see
| Setting | In the app |
|---|---|
| An app is not allowed | The app is hidden everywhere and its actions disappear. The member's own setting for it is kept for later. |
| An action is Off | The action is hidden and refused. |
| An action is Ask | The member confirms the action before it runs. |
| A catalog server is not allowed | The server shows Not allowed, with "Your organization does not allow this server". Open chats lose it. |
| Custom servers are limited | Adding a server shows "Your organization only allows custom servers matching:" followed by your patterns. Other servers are refused. |
| Your organization's servers | Each one carries a badge with your organization's name, such as "Acme". Each one asks the member to sign in with their own account the first time. |
Action rules and custom server patterns need a current PandaOS on members' computers, see How policies work. Members get the change within about 5 minutes, and sooner when they restart PandaOS, wake their computer or click Refresh in Settings, Organization.