---
name: notiero
description: Save things to the user's Notiero notebook and look them up later. Use when the user says "note this", "save this", "remember this", "add to my notes", "save to Notiero", when a decision, a working fix, or a to-do list is worth keeping past this chat, at the end of a long session for a short handoff, and before answering "what did we decide about X" or "what was that command" (search first).
---

# Notiero notes

Notiero (notiero.com) is the user's own notebook. You can write to it, and with a key that may read, search what is in their **AI folder**. The user reads everything on their phone or laptop.

## Tools (from the `notiero` MCP server)

| Tool | Use it to |
|---|---|
| `write_note` (`title`, `text`, `folder?`, `tags?`, `private?`) | Save a new note. Returns an id. `private: true` for secrets. |
| `append_to_note` (`id`, `text`) | Add to the end of a note, for running logs. |
| `search_notes` (`query`) | Find notes by words. Read keys only. |
| `read_note` (`id`) | Get a note's full text. Read keys only. |
| `list_notes` | See the latest notes. Read keys only. |

No tool can delete. If the MCP server is not connected, see Setup below.

## When to save

- The user asks: "note this", "save it", "remember that".
- A decision was made. Save what was decided and **why**, in 3 to 6 lines.
- Something finally worked: the command, the fix, the config. Save it exactly.
- End of a long session: a short handoff. What changed, what is left, what to check first next time.

Do not save small talk, whole transcripts, or secrets the user did not ask you to keep.

## Secrets

When the user asks you to keep a password, API key or token, save it with `private: true` and a title like `SECRET · <project> · <what>`. Include what it is for, where it is used, and the date. Private notes stay outside the AI folder, so no key can read them back. After saving, say `Saved to Notiero (SECRET · <what>)` and never repeat the value in chat. Suggest the user opens Notiero soon so it syncs into their notebook.

## How to write a good note

- **Title:** short and searchable. `Project · topic` works well, e.g. `Website · deploy fix`.
- **Body:** markdown. Lead with the answer, then the detail. Code in fenced blocks.
- **One topic per note.** Two topics, two notes.
- **Folder:** optional subfolder inside AI, e.g. `Projects/Website`. Keep it shallow.
- **Tags:** 1 to 3, lowercase, e.g. `["work","deploy"]`.
- **Running logs:** write the note once, keep the id, then `append_to_note` with a dated line (`2026-09-25: ...`).

## Before answering from memory

If the user asks about something they may have saved ("what did we pick for the database", "what was that command"), call `search_notes` first, then `read_note` on the best hit, and say which note you used. If you get "write-only key", answer without it and mention once that a reading key can be created in Notiero > Settings > For your AI.

## After saving

Tell the user in one line: `Saved to Notiero: <title>`. The note shows up the next time the Notiero app is open. Do not paste the whole note back.

## Setup (if the tools are missing)

1. In Notiero: sign in, open **Settings > For your AI**, create a key. Pick "Add and read the AI folder" if you want me to look things up.
2. Claude Code:
   ```bash
   claude mcp add notiero -s user -e NOTIERO_API_KEY=nti_your_key -- npx -y notiero-mcp
   ```
   Claude Desktop, Cursor and others: add `npx -y notiero-mcp` with `NOTIERO_API_KEY` to the MCP config.
3. No MCP at all: `POST https://notiero.com/api/agent-note` with `Authorization: Bearer nti_...` and JSON `{"title":"...","text":"..."}`.

Guide: https://notiero.com/for-your-ai/