Tools

Nora's built-in tools

How agents use Nora's own MCP tools to create bots, remember things, read threads, manage tasks and change settings, and what each tool does.

What the built-in tools are

Nora runs its own MCP server, called nora, and adds it to each thread as the thread starts. It gives the agent tools to act inside Nora: ask other bots for help, keep notes, read other threads, manage the task board, create bots and change settings.

There is nothing to install or configure. The tools work with Claude Code, Codex and ACP agents that support HTTP MCP servers.

Use the tools

You don't call the tools yourself. Ask in plain language and the agent picks the right tool. Each call appears in the thread's activity line like any other tool call, so you can see what it did. For example:

Bots
“Create a release manager bot that uses Codex.” “Change Ada's instructions to focus on accessibility.”
Asking a bot
“@Ada, review the changes on this branch.” “Ask Scout what we found out about payment providers last week.”
Memory
“Remember that we use British spelling.” “What do you remember about the release process?” “Forget the note about staging.”
Threads
“What did the checkout refactor thread decide?” “List the threads that are still running.”
Tasks
“Add a task to write tests for the role picker.” “Move the login task to Done.” “Start task …” (with a task ID from a handoff).
Settings
“Switch to dark mode.” “Make new threads start with Claude Sonnet.” “Turn on settings sync.”

Most app tools are for Nora threads

Creating bots, listing workspaces and models, and reading or changing settings only work in threads with Nora, not in threads with your own bots. See which threads get which tools below.

Check the server is running

The server starts with the first Nora thread after Nora opens.

  1. Open Settings → MCP Servers.
  2. Find Nora at the top of the table, marked Built in.
  3. Check its status: Running, or Not started if no Nora thread has started yet.
  4. Click its tool count to read every tool's description.

Which threads get which tools

Each thread gets only the tools that fit it:

Nora threads
Threads with Nora rather than one of your bots. They get every tool except chat_history.
Bot threads
Threads where one of your bots is working. They get ask_bot, list_bots, memory (remember, recall, forget), list_threads, read_thread and the task tools.
Bots in a group chat
A bot answering in a group or direct chat gets chat_history and the task tools.

Bot tools

For creating, changing and finding bots.

create_bot
Creates a bot and saves it straight away; it appears in the Bots sidebar. Inputs: name (up to 40 characters), role (up to 80), instructions (up to 8,000), availability (everywhere or workspace), sharing (private or shared, which saves it as a .nora/bots file), provider and model (default: the thread's own), and optional avatar shape, colour and eyes. Nora threads only.
update_bot
Changes a bot by its id. Only the fields you pass change; instructions replaces the old instructions entirely. New threads with the bot use the changes; existing threads keep the instructions they started with. Nora threads only.
list_bots
Lists the bots available in the thread's workspace, with their id, role, model and where they are available. Nora and bot threads.

Asking another bot

ask_bot
Sends a message to a bot (by id or name) and waits for the reply. The bot answers in its own thread with its own instructions, model and permissions, and read-only access to the workspace. Asking the same bot again continues that thread. The asked bot can't see the asking thread, so the message must carry the context it needs. Nora and bot threads.

Asks can't loop

A bot can't ask itself or a bot that is already waiting on the same conversation, and a chain of bots asking bots stops after four. When that happens, the bot is told to answer with what it has.

Memory tools

Notes a bot keeps for itself across threads. You can see and edit them in the bot's info panel.

remember
Saves one self-contained note (text, up to 1,000 characters). scope is bot (every workspace, the default) or workspace (this one only). Pass a note's memory_id to rewrite it instead of adding a near-duplicate. The newest notes are included in later threads.
recall
Searches saved notes for this workspace and everywhere, best match first, with each note's id. An empty query lists the newest notes.
forget
Deletes a note by its memory_id. Agents can't change or delete notes you wrote yourself.

Don't keep secrets in memory

Notes are added to later threads as context and sent to the model, so they should never contain passwords, keys or tokens.

Chat tools

chat_history
Reads earlier messages of the group or direct chat a bot is answering in, newest last, with who wrote each. limit sets how many (default 20, up to 50) and skip pages further back. A bot's prompt only carries messages since it last spoke, so it uses this for anything older. Bots in a chat only.

Thread tools

For picking up context from earlier work.

list_threads
Lists threads newest first, with id, title, bot, status and last activity. all_workspaces includes every workspace, include_settled includes settled threads, and limit sets how many (default 30, up to 100). A bot sees only its own threads.
read_thread
Reads the latest messages of a thread by id: what you asked and the final answers, without tool output. limit sets how many messages (default 20, up to 50).

Task tools

Every thread with Nora's tools gets these, so any agent can keep the workspace's task board up to date. Tasks are referred to by a stable ID.

list_tasks
Lists the board's tasks with their stable id, path, title and column, such as Todo, In Progress or Done.
create_task
Adds a task to the first column, saved as a Markdown file in .nora/tasks. Inputs: title (up to 200 characters) and details (Markdown: goal, context and definition of done).
read_task
Reads a task's details and status by its id.
start_task
Starts or reopens a task by id: marks it incomplete and moves it to In Progress. Safe to repeat.
finish_task
Marks a task complete by id and moves it to Done. Agents are told to call it only once the task's completion criteria are met. Safe to repeat.
move_task
Moves a task, by its path, to another column (by id or title).

Workspace and model tools

Nora threads only.

list_workspaces
Lists the open workspaces with their kind, folder and Git branch, and marks the thread's own.
list_models
Lists installed providers, such as claude and codex, and the models each offers.

Settings tools

Nora threads only.

get_settings
Reads Nora's settings: appearance, general preferences, AI and voice, personalization, thread defaults and whether sync is on.
update_settings
Changes settings. Only the fields passed change, for example { appearance: { themeMode: 'dark' } }; AI, voice and terminal defaults merge, while lists replace. Default models must match an installed provider from list_models. Changes show in Settings straight away; hardware acceleration needs a restart.

Settings include saved API keys

get_settings returns everything under Settings → AI, including any OpenAI, Google or Anthropic API keys saved there, so a Nora thread that reads your settings sends them to its model. Remove keys you don't need, and avoid asking Nora to read all settings in threads where that matters.

Security

  • The server listens only on this computer (127.0.0.1), never on your network.
  • Each thread gets its own access token, and every call acts only for that thread and its workspace. Unknown tokens are refused.
  • Bots asked through ask_bot get read-only access to the workspace.
NextDownload NoraWhat’s newGet support