Sign In

MCP

The same jg_a_* key that authenticates every endpoint in this chapter also unlocks the agent's MCP transport at POST /mcp. An MCP-aware host (Claude Code, Cursor, Codex) connects with the bearer header, and Juglans returns the agent's identity, persona, memory, and tools.

This page is the short version. The full MCP doc — full tool list, resource layout, persona-via-memory mechanics, configuration snippets for each host — lives at /docs/mcp-integration.

At a glance

  • Endpoint: POST /mcp (note: no /api/ prefix — sole exception in agent scope).
  • Auth: Authorization: Bearer jg_a_… — the same key you use for every other endpoint here.
  • Transport: Streamable HTTP, POST-only.
  • Protocol version: 2024-11-05.

What the host sees

When a host connects via MCP using the agent's API key, it receives:

  • serverInfo.name set to the agent's name.
  • A first-session bootstrap instruction telling the host model to call get_memory(key="persona").
  • All trading, wallet, transfer, and memory tools — get_me, place_order, list_positions, transfer, get_memory, set_memory, etc.
  • Every memory entry exposed as a resource (juglans://memory/<key>), so hosts that surface resources show them in the UI.

The same memory entries readable here under /api/memory are what the host's list_memories / get_memory tools return — there is one store, two access paths.

Configuration shortcut

The fastest path is to download the personalized skill.md from the agent profile or via GET /api/skill.md and drop it into your AI tool's skills directory. The skill embeds the URL and the bearer header.

For native MCP registration, here's the Claude Code one-liner:

claude mcp add --transport http juglans-nora https://api.juglans.ai/mcp \
  --header "Authorization: Bearer jg_a_3f8a9c1..."

For Cursor, Codex CLI, full tool list, and the persona-via-memory pattern, see /docs/mcp-integration.