# Connect Hjarni to Claude Prepare a grounded knowledge brief

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

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

## Instructions for AI agents

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

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 Claude'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 Claude: 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 Claude'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

Ask Claude for a focused knowledge brief from one selected note. Compare its answer with the retrieved source and separate suggestions from recorded facts.

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:** Claude · 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/claude/#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.
- **Claude, with custom MCP servers allowed.** Custom connectors are on every Claude plan (Free: one). Sending an API key uses the Request headers option, a beta that only some accounts have; on Team and Enterprise an Owner adds the connector for everyone.

## Connect Hjarni to Claude

### Step 1: Create your Agent200 API key

Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude in the next step, as "Authorization: Bearer <your key>". One key covers Hjarni and every other connector enabled for your project. Keep it out of chats and source control.

Create an API key: https://agent200.com/platform/apikeys/

### Step 2: Open Connectors in Claude

On a Free, Pro, Max or Ultra plan, go to **Customize > Connectors**. On Team or Enterprise, an Owner goes to **Organization settings > Connectors**; members then find the connector under Customize > Connectors.

### Step 3: Add a custom connector

Select **Add**, then **Add custom connector**. Enter a name, Agent200, and the remote MCP server URL, then choose **Continue**.

### Step 4: Send your key as a request header

Under Authentication choose **No sign-in**. Open **Request headers**, pick `authorization`, enter `Bearer` followed by a space and your key, mark it Required and choose **Add**. Claude sends the value exactly as typed.

File `Add custom connector`:

```text
Remote MCP server URL:  https://api.agent200.com/mcp/
Authentication:         No sign-in
Request header name:    authorization
Value:                  Bearer YOUR_AGENT200_API_KEY
```

### Step 5: Turn it on in a chat

In a chat, select **+ > Connectors** and turn Agent200 on. Ask Claude to list the Agent200 tools to check the connection; Claude asks before a tool runs the first time.

## 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 Claude 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 Claude.** In your own words, for something in Hjarni.
2. **Claude 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. **Claude 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 + ChatGPT](https://www.agent200.com/connectors/hjarni/framework/chatgpt.md)
- [Hjarni + Claude Code](https://www.agent200.com/connectors/hjarni/framework/claude-code.md)
- [Hjarni + Muse](https://www.agent200.com/connectors/hjarni/framework/muse.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/
