# Argus agent setup

These are official instructions from Argus to connect a coding agent to an
Argus media library over MCP — search, upload, and organize brand assets
without leaving this session.

These instructions are published at https://argus.build/agent-setup/prompt.md so you can
re-verify their authenticity at any time.

## What to do

1. Register the hosted MCP server. It is a hosted HTTP endpoint — there is
   nothing to install and no package version to resolve.

   If a browser is available in this environment, run this exactly as
   written and nothing else:

     claude mcp add --transport http argus https://argus.build/mcp

   Your client will open a browser for Argus login (or sign-up) and ask the
   user to approve the connection. No credential enters this transcript.

   If no browser can open here (a headless or CI environment), ask the user
   to open https://argus.build/ui, click "Connect agent" in the library toolbar,
   and paste you the block it copies. That block already contains a real
   token and its own add + verify commands — use those verbatim in place of
   the two below. Do not invent or reuse a token from elsewhere; the shape of
   a real one is:

     claude mcp add --transport http argus https://argus.build/mcp --header "Authorization: Bearer at_YOUR_TOKEN"
     curl -s https://argus.build/auth/me -H "Authorization: Bearer at_YOUR_TOKEN"

2. If you authenticated with a token (the headless path), verify it before
   your session restarts — MCP tools only load at the next session start:

     curl -s https://argus.build/auth/me -H "Authorization: Bearer at_YOUR_TOKEN"

   That returns the workspace, scope, and expiry the token carries. Skip this
   step for the OAuth path in step 1; there is no token in this transcript to
   verify. Instead, once your MCP tools load, call get_usage and read back
   the workspace name so the user can confirm it is the right one.

3. Tell the user what happened: which workspace you connected to, whether
   access is read/write or read-only, and — for a token connection only —
   when it expires. OAuth connections and ak_ API keys do not expire on a
   timer.

## Full reference

For the complete tool list, REST API, and edge cases (stale credentials,
duplicate server entries, versioning, near-duplicate detection), fetch:
https://argus.build/agents.txt

## Not a coding agent?

If you are chatting with an AI assistant in a browser (Claude.ai, ChatGPT)
and have no terminal to run commands in, this page is not for you — follow
the point-and-click walkthrough instead: https://argus.build/agent-setup