Hjarni + Muse

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.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. Hjarni tools
  7. How it works
  8. Troubleshooting
  9. FAQ

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.

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

Connector
Hjarni
Works with
Muse · Agent app, through MCP
Authentication
Your Agent200 API key
Tools
6 tools
MCP server
https://api.agent200.com/mcp/

Before you start

  • An Agent200 API key. Create one on the API keys page 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

  1. 1

    Step 1: Create your Agent200 API key

    Create a key on the API keys page and store it securely.

    .env
    Conceptual example
    Store the Agent200 API key as an environment variable
    # Keep the key out of your code, prompts and chats.
    export AGENT200_API_KEY="paste-your-key-here"
  2. 2

    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.

    Muse chat
    MCP: message that asks Muse to create the custom connector
    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.
  3. 3

    Step 3: Inspect read tools

    Confirm the Hjarni operations and schemas advertised by the connection.

  4. 4

    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

Run one request to check everything is wired up.

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.

Get your API key

Create a key in the Agent200 dashboard. It reaches Hjarni and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Hjarni to Muse.

Agent brief
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.

The whole guide is also available as Markdown, for agents and LLMs: /connectors/hjarni/framework/muse.md

Hjarni tools Muse can call

  • Search knowledge

    Read
    hjarni_search

    Search notes, folders and tags available through the project’s Hjarni tools.

  • List notes

    Read
    hjarni_list_notes

    Find notes available within the selected accessible scope.

  • Read a note

    Read
    hjarni_get_note

    Retrieve an identified note and its returned content.

  • List folders

    Read
    hjarni_list_containers

    Find accessible containers and their returned metadata.

  • Read a folder

    Read
    hjarni_get_container

    Retrieve details of one identified container.

  • List tags

    Read
    hjarni_list_tags

    Find tags available through the project’s Hjarni tools.

How it works

  1. 01

    You ask Muse

    In your own words, for something in Hjarni.

  2. 02

    Muse picks a tool

    It sees the Hjarni tools on the Agent200 MCP server and calls the one the request needs.

  3. 03

    Agent200 runs the call

    It reaches Hjarni with your Agent200 API key, within the endpoints your project allows.

  4. 04

    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

200 OK

Hjarni, connected to Muse.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)