Aarna MCP server — 138 tools for AI agent integration. Hosted by Junct.
Aarna MCP server — 138 tools for AI agent integration. Hosted by Junct. Exposed over MCP by the aarna mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Hosted at aarna.mcp.junct.dev/mcp. Free to use. No auth. No API key required.
This MCP server is deterministically generated from the Aarna API specification. Every tool maps 1:1 to a real API endpoint — no hallucinated endpoints, no phantom tools.
Everything the assistant can do here goes through one of these:
Protocol — ** AarnaEndpoint — ** https://aarna.mcp.junct.dev/mcpTransport — ** Streamable HTTPAuth — ** None requiredDocumentation — ** aarna.mcp.junct.dev/llms.txtBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Aarna's toolset — Protocol, Endpoint, Transport and 2 more — is a fair guide to whether it matches your workflow. It is maintained by junct-bot; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Protocol | ** Aarna |
| Endpoint | ** https://aarna.mcp.junct.dev/mcp |
| Transport | ** Streamable HTTP |
| Auth | ** None required |
| Documentation | ** [aarna.mcp.junct.dev/llms.txt](https://aarna.mcp.junct.dev/llms.txt) |
{
"mcpServers": {
"aarna": {
"url": "https://aarna.mcp.junct.dev/mcp",
"transport": "streamable-http"
}
}
}Configuration as documented by the project. Restart the client after saving.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.