## Arcmira integration

Arcmira is a search engine for the spoken web: an index of YouTube and podcast transcripts covering mentions, momentum, sponsors, and on-air recommendations.

Agen.co connects to Arcmira through Arcmira's own hosted MCP server as an **Official** connector. Each user authorizes with their own Arcmira account, and agents get read-only access to the transcript index at that account's plan level.

Prerequisites
- An Arcmira account. No app needs to be registered with Arcmira — the MCP server registers Agen.co as a client automatically, so there is no Client ID or Client Secret to copy. A reader with no account can create one from the consent screen's sign-up flow.


This server exposes two tools, not a list of commands
Arcmira's MCP server uses a code-execution pattern: instead of one tool per operation, it exposes `describe` (returns the Arcmira client's reference — methods, arguments, and worked examples) and `execute` (runs a short JavaScript program written against that client, inside a sandbox, and returns what the program prints or returns). An agent calls `describe` once to learn the client, then writes and runs `execute` programs against it. Older descriptions of Arcmira's MCP server list separate tools such as searching transcripts or reading entity counts — those are now methods called from inside an `execute` program, not tools in their own right.

### Connect Arcmira in Agen.co

1. In the Agen.co portal, go to **Connectors** → **My connectors** and click **Add connector**.
2. In the **Select connector** drawer, search for `Arcmira` and select it. The **Add Arcmira** panel opens.
3. Fill in the field:
| Field | Required | Description |
|  --- | --- | --- |
| **Instance Slug** | Yes | Prefixes each imported tool as `slug__tool`, so several instances of the connector can coexist. Prefilled with `arcmira`, or with the next free slug such as `arcmira-2` if Arcmira is already connected. Use lowercase kebab-case. You can change it later from the connector's settings. |
4. Click **Connect**. Arcmira opens in a new tab, and the panel shows **Waiting for authorization — complete it in the opened tab…**
5. On the **Connect MCP OAuth Client** screen, which reads **MCP OAuth Client is asking for access to your Arcmira account**, sign in if prompted and click **Allow**. The screen lists read access to transcripts, entity counts, momentum, channel coverage, sponsors, monitors, trackers, recommendations, and account usage — some of it gated to data available only on certain Arcmira plans, which the screen marks **Plan bound**.
6. Back in Agen.co, the panel switches to **Select the tools to import from Arcmira.** Both tools are toggled on; turn off either you don't want to import, then click **Add**.


The connector is created and its tools imported only when you click **Add**. If you close the panel before that, nothing is saved, even though the Arcmira tab reported success.

### Authorize each user

Adding the connector doesn't authorize anyone's tool calls yet. The first time each user's agent calls an Arcmira tool, the call returns an authorization link instead of a result. The user opens the link and approves the same way. After that, the user's tool calls run against their own Arcmira account, reading at whatever plan level that account has — a call that reaches data gated to a higher plan gets back an error with a link to unlock it, rather than the data itself.

Once connected, Arcmira appears under **My connectors** with 2 tools:

| Tool | What it does |
|  --- | --- |
| **describe** | Returns the Arcmira client reference: every method, its arguments and return fields, worked example programs, and common pitfalls. Takes nothing, reads nothing from the index, and never counts against usage. |
| **execute** | Runs a short JavaScript program against the Arcmira client inside a sandbox, and returns what it printed or returned. This is how every actual query — searching transcripts, reading mentions, momentum, sponsors, recommendations, and more — runs; `describe` only explains what's available. |


Enabling the Arcmira connector isn't enough on its own. Tool calls remain denied until you create a [policy](/agen-for-work/policies/overview) that grants access to the specific tools you want to expose.

### Additional resources

- [Arcmira](https://arcmira.com/)
- [Arcmira MCP server docs](https://arcmira.com/docs/mcp-server)
- [Arcmira authentication docs](https://arcmira.com/docs/authentication)