# Connect Hjarni to Muse Prepare a grounded knowledge brief

> Read notes with Muse and Agent200. Prepare a knowledge brief through the Agent200 project’s Hjarni tools.

- Page: https://www.agent200.com/connectors/hjarni/framework/muse/
- Connector: [Hjarni](https://www.agent200.com/connectors/hjarni.md)
- Framework: Muse
- Updated: 2026-11-17

## Instructions for AI agents

Goal: connect Hjarni to Muse with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/hjarni/framework/muse/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Muse's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure Hjarni is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Muse: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Muse's exact menus or commands.
4. Check it works with this request: "Search for the Hjarni note I name, read that note, and prepare a concise knowledge brief from its returned body. Name the note and folder or space when returned. State access gaps and do not create or change notes."
   What should come back:
   - The selected note and its returned content are identified.
   - Only notes returned by the enabled Hjarni tools are used.
   - Access gaps and missing context are explicit; no note is changed.
5. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.

## Overview

Use Muse to prepare a short knowledge brief for review. Put the Agent200 key in Muse’s secure credential interface, then inspect the source before sharing the result.

Start with one identified note. Preserve the note title, body, container and source identity actually returned; report missing data and keep the workflow read-only.

Provider reference: [Hjarni MCP reference](https://hjarni.com/docs/mcp#tool-catalog).

Use the project’s Agent200 API key for this route. No separate Hjarni key is needed through Agent200.

- **Connector:** [Hjarni](https://www.agent200.com/connectors/hjarni/)
- **Works with:** Muse · Agent app, through MCP
- **Authentication:** Your Agent200 API key
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [6 tools](https://www.agent200.com/connectors/hjarni/framework/muse/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **Hjarni enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **Muse, with custom MCP servers allowed.** Muse creates custom connectors from a chat, and your key goes into its secure credentials sheet, never into the chat. Muse Code reads servers from its settings file.

## Connect Hjarni to Muse

### Step 1: Create your Agent200 API key

Create a key on the [API keys page](https://agent200.com/platform/apikeys/) and store it securely.

File `.env`:

```bash
# Keep the key out of your code, prompts and chats.
export AGENT200_API_KEY="paste-your-key-here"
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Create the custom connector

Connect to `https://api.agent200.com/mcp/` over Streamable HTTP with an Authorization: Bearer header. Enter the key in Muse’s secure credential interface.

File `Muse chat`:

```text
Create a Custom Connector for the Agent200 remote MCP server and connect to it:
Name: Agent200
Transport: remote streamable HTTP
URL: https://api.agent200.com/mcp/
Auth: API key sent in the Authorization header as "Bearer <key>"
Open the secure credentials store so I can enter the API key there, not in this chat.
Then list its tools to confirm the connection works.
```

### Step 3: Inspect read tools

Confirm the Hjarni operations and schemas advertised by the connection.

### Step 4: Enable the Hjarni tools

Use the project’s Agent200 API key and inspect the Hjarni read tools advertised by the runtime. No separate Hjarni key is needed through Agent200.

## Test your connection

Ask: "Search for the Hjarni note I name, read that note, and prepare a concise knowledge brief from its returned body. Name the note and folder or space when returned. State access gaps and do not create or change notes."

What should come back:

- The selected note and its returned content are identified.
- Only notes returned by the enabled Hjarni tools are used.
- Access gaps and missing context are explicit; no note is changed.

Check project tool enablement, selected note ID and result scope. Do not infer that an unreturned note does not exist.

## Hjarni tools Muse can call

- **Search knowledge** (`hjarni_search`, read): Search notes, folders and tags available through the project’s Hjarni tools.
- **List notes** (`hjarni_list_notes`, read): Find notes available within the selected accessible scope.
- **Read a note** (`hjarni_get_note`, read): Retrieve an identified note and its returned content.
- **List folders** (`hjarni_list_containers`, read): Find accessible containers and their returned metadata.
- **Read a folder** (`hjarni_get_container`, read): Retrieve details of one identified container.
- **List tags** (`hjarni_list_tags`, read): Find tags available through the project’s Hjarni tools.

## How it works

1. **You ask Muse.** In your own words, for something in Hjarni.
2. **Muse picks a tool.** It sees the Hjarni tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** It reaches Hjarni with your Agent200 API key, within the endpoints your project allows.
4. **Muse answers.** It gets the result back from the MCP server and uses it in its reply or its next step.

**Permissions at every level.** Your project settings decide which services and endpoints the agent may use.

## Troubleshooting

### The source cannot be read

Check the project’s Hjarni tool availability, selected note ID and pagination. Treat a missing or refused note as an access or scope result, not as evidence that it never existed.

## FAQ

### How do I verify this result?

Compare the named note and returned note title, body, container and source identity actually returned with the source. Treat missing information as missing, not as a fact.

## Use Hjarni with another framework

- [Hjarni + Claude](https://www.agent200.com/connectors/hjarni/framework/claude.md)
- [Hjarni + ChatGPT](https://www.agent200.com/connectors/hjarni/framework/chatgpt.md)
- [Hjarni + Claude Code](https://www.agent200.com/connectors/hjarni/framework/claude-code.md)
- [Hjarni + Grok Bot](https://www.agent200.com/connectors/hjarni/framework/grok-bot.md)
- [Hjarni + OpenAI Dots](https://www.agent200.com/connectors/hjarni/framework/openai-dots.md)
- [Hjarni + Claude Duet](https://www.agent200.com/connectors/hjarni/framework/claude-duet.md)
- [Hjarni + Hermes Agent](https://www.agent200.com/connectors/hjarni/framework/hermes-agent.md)
- [Hjarni + OpenClaw](https://www.agent200.com/connectors/hjarni/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
