---
title: Install Integrations
description: Discover and install extensions and other integrations from eve and third-party sources.
---

# Install Integrations



Install integrations from eve's official catalog, a third-party source, or an integration URL. Integrations are distributed using the [shadcn registry format](https://ui.shadcn.com/docs/registry).

## Install an integration

Run `eve add` from an eve agent project. This installs the integration's dependencies and writes its declared files into your project.

```bash
eve add extension/agent-browser
```

The integration may create an extension mount under `agent/extensions/`. Configure that mount and any required environment variables before running your agent.

## Find an integration

Browse the [Integrations directory](/integrations) to see the official integrations available from the eve registry.

List every official integration and configured third-party source:

```bash
eve registry list
```

Search the catalog when you know what capability you need:

```bash
eve registry search browser
```

Inspect an integration before you install it:

```bash
eve registry view extension/agent-browser
```

`list` and `search` include the official eve catalog and every source you add to the project.

## Add a third-party source

Give a registry a namespace and an integration URL template:

```bash
eve registry add @acme=https://registry.acme.com/r/{name}.json
```

eve stores the mapping in `package.json#registries`. The `{name}` placeholder becomes the integration name, so `@acme/analytics` resolves to `https://registry.acme.com/r/analytics.json`.

Limit listing or search to that registry when needed:

```bash
eve registry list --registry @acme
eve registry search analytics --registry @acme
```

Install an integration from that source:

```bash
eve add @acme/analytics
```

Install a known integration URL directly when you do not need a namespace:

```bash
eve add https://registry.acme.com/r/analytics.json
```

## Configure generated files

Integrations add project files. Read the generated mount before you run the agent, then add the configuration the extension requires.

For an extension, this usually means setting environment variables and editing the file under `agent/extensions/`. See [Extensions](./extensions) for mount configuration, namespacing, and overrides.

Provider-specific setup lives in the [Integrations directory](/integrations). Follow that guidance for credentials, approval policies, and service-specific options.

## Update an installed integration

Treat generated files as project code. Commit or review local changes before you install the integration again.

Run the same command when the registry publisher provides an updated scaffold:

```bash
eve add extension/agent-browser
```

Pass `--overwrite` only when you intend to replace an existing generated file:

```bash
eve add extension/agent-browser --overwrite
```

Update the installed package with your package manager. Check the publisher's release notes before changing the generated mount or package version.

## Choose trusted sources

Integrations can add dependencies and write files. Add sources you trust, inspect an integration with `eve registry view`, and review the resulting project diff before you run the agent.

## What to read next

* [Extensions](./extensions): configure and override installed extension mounts
* [Integrations directory](/integrations): provider-specific setup and security guidance
* [shadcn registry documentation](https://ui.shadcn.com/docs/registry): publish a compatible third-party registry


---

For a semantic overview of all documentation, see [/sitemap.md](/sitemap.md)

For an index of all available documentation, see [/llms.txt](/llms.txt)

For agent-facing discovery, including API and MCP surfaces, see [/agents.md](/agents.md)