# Set up Arcmira for this agent

Connect this agent to the Arcmira MCP server at https://mcp.arcmira.com/mcp, which provides tools to read indexed YouTube and podcast transcripts and to set up monitors. Keep the user's current question and use only the instructions for the actual host.

## 1. Find your host
Identify your host from the available tools and configuration. First check for Arcmira tools and try one small read. Reuse an existing working connection. A connection made before monitor writes existed can read but not change monitors; reconnect it when the user wants monitor changes. If an existing arcmira entry uses a different URL, explain the conflict instead of replacing it. Ask which host only when its identity remains unclear.

## 2. Add the server and sign in
Use the host steps below only when a connection is missing; the rule step after them applies either way. Edit only configuration you can access on the actual host, and preserve other servers. A hosted chat sandbox cannot configure that app. Hand sign-in and consent to the user. Prefer their existing Arcmira account.
### ChatGPT
If you cannot operate this host’s connector settings with your available tools, give the user these steps: In ChatGPT on the web, open Plugins, select the plus button, then Add custom MCP server. Enter Arcmira as the name. Under Connection, enter the server URL. `https://mcp.arcmira.com/mcp` Choose OAuth for authentication. Review the risk warning, select I understand and want to continue, then select Create as a plugin. Find Arcmira in your plugins, install it, and sign in with your Arcmira account. In a new chat, type @ and select Arcmira.
### Codex
Add the server from your terminal. `codex mcp add arcmira --url https://mcp.arcmira.com/mcp` Codex opens the Arcmira sign-in in your browser. Complete it, then start a new Codex session. If the sign-in did not open, run codex mcp login arcmira. Codex CLI, the IDE extension, and the desktop Codex experience share config.toml on the same host. ChatGPT web uses a separate plugin connection.
### Claude
If you cannot operate this host’s connector settings with your available tools, give the user these steps: Open Customize, then Connectors, and choose Add custom connector. Some versions place it under +. Name it Arcmira and enter the server URL. Leave the headers empty, keep Sign in now and Use Claude’s published identity selected, then choose Add. `https://mcp.arcmira.com/mcp` Complete the Arcmira sign-in. In a conversation, open +, then Connectors, and enable Arcmira.
On Team and Enterprise plans, an owner adds the connector in Organization settings → Connectors. Each member then connects their own account and enables it in the conversation.
### Claude Code
Add the server from your terminal. `claude mcp add --transport http --scope user arcmira https://mcp.arcmira.com/mcp` Run /mcp in the session and follow the browser sign in. The tools show up in the same session. No restart, no config file to edit by hand. Or install the Arcmira plugin: the same server plus six skills (the client reference, and sponsor research, company watch, quotes, person research, show comparison).
```bash
claude plugin marketplace add arcmira/mcp
claude plugin install arcmira@arcmira
```
Turn on auto-update, since Arcmira ships weekly and Claude Code leaves it off for third-party marketplaces: run /plugin, open Marketplaces, pick arcmira, and choose Enable auto-update. Update now with claude plugin update arcmira@arcmira.
### Cursor
Install it in one click and confirm the Arcmira server in Cursor. One click install link for your human: cursor://anysphere.cursor-deeplink/mcp/install?name=arcmira&config=eyJ1cmwiOiJodHRwczovL21jcC5hcmNtaXJhLmNvbS9tY3AifQ%3D%3D Or install it from the Customize page, or write the file yourself. Use .cursor/mcp.json for one project, ~/.cursor/mcp.json for every project, and keep your other servers.
```json
{
  "mcpServers": {
    "arcmira": {
      "url": "https://mcp.arcmira.com/mcp"
    }
  }
}
```
Use a url entry without a type field. Complete Cursor’s OAuth sign-in when prompted, then open Agent and try an Arcmira read.
### VS Code
Add the server from your terminal. `code --add-mcp '{"name":"arcmira","type":"http","url":"https://mcp.arcmira.com/mcp"}'` In VS Code, run MCP: List Servers, choose arcmira, then Start Server, and complete the Arcmira sign-in. Open Chat in Agent mode and ask your first question.
### OpenCode
Merge this arcmira entry into mcp in your project’s opencode.json or the global ~/.config/opencode/opencode.json. Keep existing servers.
```json
{
  "mcp": {
    "arcmira": {
      "type": "remote",
      "url": "https://mcp.arcmira.com/mcp"
    }
  }
}
```
Sign in through your browser. `opencode mcp auth arcmira` Open a session and ask OpenCode to make a small Arcmira read.
### Hermes Agent
Add the server with OAuth, in the terminal on the machine running Hermes. `hermes mcp add arcmira --url https://mcp.arcmira.com/mcp --auth oauth` Complete sign-in when Hermes opens your browser. Use the login command below only if the connection still requires authentication. `hermes mcp login arcmira` In Hermes, run /reload-mcp or start a new session, then ask for a small Arcmira read.
### Grok
If you cannot operate this host’s connector settings with your available tools, give the user these steps: Open Grok connectors, choose New Connector, then Custom. Enter the server URL and complete Arcmira sign-in when prompted. `https://mcp.arcmira.com/mcp` Use the discovered Arcmira tools in a conversation and verify a small read.
### Gemini
If you cannot operate this host’s connector settings with your available tools, give the user these steps: In Gemini on the web, open Settings, then Connected Apps. If needed, open Personal Intelligence first. Under Custom apps or Custom apps for Spark, choose Add a custom app and paste the server URL. `https://mcp.arcmira.com/mcp` Choose Next and complete the Arcmira sign-in. In a supported chat or Spark task, type @ and select Arcmira.
### Gemini CLI
Add Arcmira to your user configuration from your terminal. `gemini mcp add --scope user --transport http arcmira https://mcp.arcmira.com/mcp` In Gemini CLI, run /mcp auth arcmira and complete the Arcmira sign-in in your browser. Run /mcp to check the tools, then ask your first question.
### Another AI
Add a remote HTTP MCP server in your AI’s settings with this URL. Use OAuth if the host supports it. `https://mcp.arcmira.com/mcp` If the host reads an mcpServers object, merge this entry into its documented MCP config instead. Keep other servers.
Use the same entry shown above.
Complete sign-in when prompted, then ask your first question.
### Add the Arcmira rule
On Claude Code, Codex, Cursor or OpenCode, offer the Arcmira rule even when the connection already worked, so you call Arcmira for spoken questions without being asked. Hosted hosts skip this step. Fetch https://arcmira.com/agent-setup/rule.md. It runs from the open line <!-- arcmira rule v1 --> to the close line <!-- /arcmira rule -->.
Before you write, show the user the rule and the file named below, and say the rule applies to every later session, or on Cursor to every chat in that project. Ask once. Write only on a yes, unless the user already asked you to add the rule.
Then write it by what the file holds now. An open line is <!-- arcmira rule v1 --> or the same line with another version number.
- No file: create it with the rule.
- An open line with a <!-- /arcmira rule --> line after it: replace the lines from that open line to the first close line after it, both included, with the rule. Keep every other line.
- An open line with no <!-- /arcmira rule --> line after it: stop, change nothing, and tell the user the old block has no close line.
- No open line: keep every line, and add a blank line and the rule at the end. Cursor differs, below.
- Claude Code: ~/.claude/CLAUDE.md.
- Codex: AGENTS.md in the folder $CODEX_HOME names, or in ~/.codex when CODEX_HOME is not set. If AGENTS.override.md in that folder exists and is not empty, write there instead.
- Cursor: .cursor/rules/arcmira.mdc in the project. A new file starts with the front matter lines ---, alwaysApply: true, ---, then the rule. If the file has no Arcmira open line, it is someone else's rule, so leave it alone and tell the user.
- OpenCode: ~/.config/opencode/AGENTS.md. If it does not exist and ~/.claude/CLAUDE.md does, do not create it: tell the user that some OpenCode versions read ~/.claude/CLAUDE.md only while ~/.config/opencode/AGENTS.md is missing, so they can add the rule by hand.

## 3. When the host cannot sign in
Prefer the sign in above. Never create an account your human did not ask for.
If OAuth is unsupported, use an existing ARCMIRA_API_KEY through the host's documented environment reference or secure credential field. Never print a credential or ask the user to paste a password, key, or token into chat. The JSON below shows the header shape; YOUR_ARCMIRA_API_KEY is a placeholder, not a universal environment reference.
```json
{
  "mcpServers": {
    "arcmira": {
      "url": "https://mcp.arcmira.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ARCMIRA_API_KEY"
      }
    }
  }
}
```
- Codex: Export ARCMIRA_API_KEY in the shell that runs Codex, then add the server with the variable name. `codex mcp add arcmira --url https://mcp.arcmira.com/mcp --bearer-token-env-var ARCMIRA_API_KEY`
- Claude Code: Add the server with the header. Export ARCMIRA_API_KEY in the shell first. `claude mcp add --transport http --scope user arcmira https://mcp.arcmira.com/mcp --header "Authorization: Bearer $ARCMIRA_API_KEY"`
- Cursor: Write the file with the header. Use .cursor/mcp.json for one project, ~/.cursor/mcp.json for every project. `{"mcpServers":{"arcmira":{"url":"https://mcp.arcmira.com/mcp","headers":{"Authorization":"Bearer ${env:ARCMIRA_API_KEY}"}}}}` Set ARCMIRA_API_KEY in the environment inherited by Cursor. Keep the environment reference in the file; do not paste your key into chat or commit it.
- OpenCode: Set ARCMIRA_API_KEY in OpenCode's environment, then merge this entry into its configuration. `{"mcp":{"arcmira":{"type":"remote","url":"https://mcp.arcmira.com/mcp","oauth":false,"headers":{"Authorization":"Bearer {env:ARCMIRA_API_KEY}"}}}}`
- Hermes Agent: Add the server with header auth. Hermes asks for the key, stores it in ~/.hermes/.env, and sends it as Authorization: Bearer. `hermes mcp add arcmira --url https://mcp.arcmira.com/mcp --auth header`
If no key is configured, direct the user to https://arcmira.com/dashboard/api and ask them to store it securely in their host. Only with explicit signup authorization, use POST https://api.arcmira.com/v1/signups and POST https://api.arcmira.com/v1/signups/verify. Store the returned key securely without displaying it. Do not create an extra account, buy credits, or upgrade a plan.

## 4. Verify
Inspect the exposed tool schemas and confirm authenticated access from the host status and returned access metadata without exposing credentials. The server exposes six tools: `arcmira_describe`, `arcmira_execute_read`, `arcmira_execute_write`, `arcmira_youtube_search`, `arcmira_youtube_transcript` and `arcmira_feedback`. Call `arcmira_describe` once, then call `arcmira_execute_read` with `return await arcmira.status({});` to check the account. This setup check must not start a Premium transcript, create a monitor or submit feedback. A public resolution alone does not prove account access. Filters take ids, never names: resolve a name with `arcmira.resolve` first. Report the actual result without credentials, and name the rule file you wrote, or say the user declined the rule. If the host needs a reconnect or new chat, give that next step and preserve the question. Configuration alone is not success. Arcmira ships weekly: The MCP server is remote, so its tools and the `arcmira_describe` reference are current on every call. Skills and plugins are local copies: if the user has the Arcmira plugin in Claude Code, tell them to turn on auto-update (run /plugin, open Marketplaces, pick arcmira, choose Enable auto-update); in Codex, `codex plugin marketplace upgrade arcmira` updates it. Details: https://arcmira.com/docs/mcp-server#stay-up-to-date.

## 5. Gates
Use the returned cutoff and the client reference from `arcmira_describe`. If an error includes `error.retry.set` or `error.retry.omit`, apply every change together and retry once. Inside a program a gate throws an ArcmiraError whose `code` and `unlock.url` name the gate. Label historical coverage. Explain any remaining gate and its returned `unlock.url`. Never bypass a gate with another key or invent missing results.

Docs: https://arcmira.com/docs/mcp-server.
This prompt is published at https://arcmira.com/agent-setup/prompt.md, so you can re-fetch it to confirm it is genuine.