Install and manage integrations

Integrations add local tool packages and, for supported services, external chat interfaces. The marketplace separates package installation, credential storage, tool selection, resource boundaries, and approval policy.

Browse the marketplace

Open Tools and then Integrations. The catalog shows available packages, installed packages, services, tool counts, and skill counts. Select a package to view its description and setup fields.

Use Reload integrations after the runtime or package catalog changes. Reloading does not install or uninstall anything by itself.

Select only required tools

Read tools are normally the safest starting point. Write tools remain off by default in first-party packages. Select only actions the agent needs, then enable connector writes when the selected write tools should be callable.

Tool selection controls runtime availability. Removing a tool removes it from the agent even if an upstream credential has broader permission.

Add credentials

Enter tokens, client IDs, secrets, URLs, or browser authorization in the connector’s dedicated setup fields. Saved secrets go to the marketplace secret store and are not exposed to the language model or returned to the frontend after save.

Do not paste credentials into chat to ask the assistant to configure itself.

Set resource boundaries

Use the connector allowlist for the smallest useful set of repositories, channels, projects, chats, or object types. Enforcement happens inside first-party adapters as well as in the agent’s tool policy.

An upstream account with broad access can still see more through another client. Pneum.ai’s allowlist constrains this agent; it does not rewrite the upstream account’s permissions.

Configure writes and approvals

Enabling connector writes makes selected write tools available, but central tool policy can still ask for approval. Keep external sends, record mutations, publication, and deletion behind a narrow approval rule.

Verify before production use

1. Run a list or read tool inside the allowlist.
2. Attempt a harmless target outside the allowlist and confirm rejection.
3. Preview a write and confirm the approval card shows the exact destination and arguments.
4. Rotate a test credential and confirm reconnect behavior.
5. If using external chat, test immutable-user admission and owner approvals separately.

Choose a connector guide from the navigation or define an HTTP, MCP, or container custom tool.