Hjarni + Grok Bot
Connect Hjarni to Grok Bot
Prepare a grounded knowledge brief
Read notes with Grok Bot and Agent200. Prepare a knowledge brief through the Agent200 project’s Hjarni tools.
On this page
Overview
Identify the selected note and ask Grok Bot to use the Agent200 connection. Inspect tool activity so browser context or another app does not replace the requested read.
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
- Grok Bot · Agent app, through MCP
- Authentication
- Your Agent200 API key
- You need
- An 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.
- Grok Bot, with custom MCP servers allowed. Grok Bot comes with SuperGrok, Grok Business seats and paid Cursor plans. On a team, the admin's connector policy must allow the Agent200 server.
Connect Hjarni to Grok Bot
-
1
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 Grok Bot 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.
-
2
Step 2: Open the custom connector form
In Grok Bot, open Connect apps from the sidebar and choose Add a custom connector at the bottom.
-
3
Step 3: Fill in the server and your key
Enter the name Agent200, pick Type Remote HTTPS, enter the server URL and add one HTTP header:
Authorizationwith the valueBearerfollowed by your key. Leave Client ID empty, then choose Add plugin.Add a custom connectorMCP: Grok Bot custom connector form Name: Agent200 Type: Remote HTTPS Server URL: https://api.agent200.com/mcp/ HTTP headers: Authorization: Bearer YOUR_AGENT200_API_KEY -
4
Step 4: Attach Agent200 in a chat
In a Bot chat, type
@and attach Agent200 to the task. Custom servers are account-wide, so every Bot on the account can use it.
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.
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 Grok Bot.
Goal: connect Hjarni to Grok Bot with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/hjarni/framework/grok-bot/ 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 Grok Bot'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 Grok Bot: 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 Grok Bot'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/grok-bot.md
Hjarni tools Grok Bot can call
-
Search knowledge
Readhjarni_searchSearch notes, folders and tags available through the project’s Hjarni tools.
-
List notes
Readhjarni_list_notesFind notes available within the selected accessible scope.
-
Read a note
Readhjarni_get_noteRetrieve an identified note and its returned content.
-
List folders
Readhjarni_list_containersFind accessible containers and their returned metadata.
-
Read a folder
Readhjarni_get_containerRetrieve details of one identified container.
-
List tags
Readhjarni_list_tagsFind tags available through the project’s Hjarni tools.
No tool matches that search.
How it works
-
01
You ask Grok Bot
In your own words, for something in Hjarni.
-
02
Grok Bot picks a tool
It sees the Hjarni tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
It reaches Hjarni with your Agent200 API key, within the endpoints your project allows.
-
04
Grok Bot 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.
