# Atmina agent setup prompt

These are the official Atmina MCP setup instructions. Follow them in order.

## 1. Connect Atmina

Atmina is your memory: shared and persistent. Use it to recall durable
context before answering and to capture decisions, findings, and notes the user
wants preserved.

MCP endpoint:

```text
https://mcp.atmina.ai/mcp
```

OAuth opens in the browser on connect or first use. No API key is required. If
the user does not have a Atmina account yet, the browser step lets them create
one or join the alpha waitlist.

If Atmina is not configured in this agent yet, use the section that matches this
client. If you cannot edit your own MCP configuration, show the user the exact
command or config to paste.

### Claude Desktop

Add a custom remote MCP connector:

```text
Name: Atmina
Remote MCP server URL: https://mcp.atmina.ai/mcp
```

### Claude Code

```sh
claude mcp add --transport http atmina https://mcp.atmina.ai/mcp
```

### Codex

```sh
codex mcp add atmina --url https://mcp.atmina.ai/mcp
codex mcp login atmina
```

### Cursor

Add this to `~/.cursor/mcp.json` or the project's `.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "atmina": { "url": "https://mcp.atmina.ai/mcp" }
  }
}
```

### OpenCode

```json
{
  "mcp": {
    "atmina": {
      "type": "remote",
      "url": "https://mcp.atmina.ai/mcp",
      "enabled": true
    }
  }
}
```

### Generic MCP client

```text
endpoint: https://mcp.atmina.ai/mcp
auth: OAuth 2.0
```

## 2. Find the memory

After OAuth succeeds, discover the user's available memories:

1. Call `whoami`.
2. Call `list_kbs`.
3. If exactly one Knowledge Base is listed, use its `Ref` value as the `kb_id`
   argument for KB tools.
4. If multiple Knowledge Bases are listed, show the user the names and
   descriptions, then ask which memory to use.
5. If none are listed, tell the user to create one in the Atmina app, then run
   `list_kbs` again.

Do not ask the user to provide a Knowledge Base identifier before trying
`list_kbs`. Do not use a bare slug by default; use the listed `Ref` value.

## 3. First action

Use exactly one first action.

### READ-FIRST

Use this for a shared KB or any KB that may already contain notes.

1. Call `list_files` with the selected `kb_id`.
2. Search the KB for onboarding or project context relevant to the user's task.
3. Summarize what you found and cite source paths.
4. Do not write yet. Wait for the user's instruction.

### WRITE-FIRST

Use this only for a new, empty KB the user owns.

1. Use `write_file` with the selected `kb_id` to create
   `notes/first-memory.md`.
2. Write:
   `Atmina is connected. Use this KB to remember durable context I explicitly ask you to save.`
3. Verify the file with `get_file_outline`.
4. Tell the user Atmina is ready.

After setup, recall from Atmina before answering questions about durable team or
project knowledge. Capture what the user asks you to remember. At a natural end
of a working session you may offer to save a short session note
(`journal/YYYY-MM-DD-<slug>.md`) — but write it only if they agree.

Public setup guide: https://atmina.ai/agent-setup
App setup: https://app.atmina.ai