Integrations
============

Integrations are tools that agents can call at runtime to interact with external systems, retrieve live data, execute code, or trigger actions. Like all Foundry resources, integrations are created and configured once at the workspace level and then made available to any agent.

.. image:: /images/foundry-integrations-inhouse.png
   :alt: Integrations page — In-House Tools tab
   :align: center
   :width: 100%

|

OneByZero Neo supports three categories of integration, accessible from three tabs on the Integrations page:

* **In-House Tools** — prebuilt integrations to common services and utilities, ready to use with minimal or no configuration.
* **Custom Tools** — integrations you define from an OpenAPI specification, connecting agents to your own APIs and internal systems.
* **MCPs** — tools exposed by MCP (Model Context Protocol) servers, either platform-managed or user-deployed.

**Access control**

The `canViewTools`, `canViewInhouseTools`, `canViewCustomTools`, `canCreateCustomTools`, and `canViewMcpServers` permissions control which tabs are visible and whether users can create custom tools.

**In this section:**

.. toctree::
   :maxdepth: 1

   in_house_tools
   custom_tools
   mcp_servers