Junê

io.github.JunemindPublished by GitHub account Junemindv0.8.1Updated Oct 27, 2026

Shared, cited knowledge-graph memory for agents — ask, search, remember, keep standing instructions

Overview

AI-generated overview

Junê gives an AI assistant a shared, cited knowledge-graph memory: ask questions, search, remember facts and keep standing instructions across sessions.

What you can do
  • Ask cited questions against the bound canvas, optionally using a bring-your-own LLM key
  • Search and read the knowledge graph and pages in the canvas
  • Remember new information and maintain standing docs, skills and learnings
  • Re-inject a periodic digest of standing docs into tool results so context persists
  • Optionally export and import pages to a local directory for repo sync, and upload files for ingestion when those roots are configured
When to use it
Useful when an assistant should carry durable, citable memory between sessions or share a knowledge base with a team, rather than starting from zero each conversation. Also fits setups that want standing instructions or skills kept in one place and refreshed automatically.
Requirements
Runs locally over stdio, launched with uvx from the june-mcp PyPI package, so Python and uv are needed. Requires JUNE_BASE_URL pointing at a June endpoint (the desktop app's local engine, a self-hosted service, or a hosted Team workspace) and JUNE_CANVAS naming the canvas to bind to. JUNE_API_KEY is required unless JUNE_ALLOW_ANON=1 is set; JUNE_LLM_KEY is optional. Desktop only.
Before you install
JUNE_API_KEY and JUNE_LLM_KEY are secrets passed as environment variables; the LLM key is forwarded per request for cited answers. Write tools change stored memory and can create a canvas when JUNE_CANVAS_CREATE=1; set JUNE_READONLY=1 to hide and refuse writes. JUNE_EXPORT_ROOT enables fenced writes to a local directory and git commits, and JUNE_FILES_ROOT lets agents upload files, so only set them to directories you intend to expose.

Installation

In SourceWeft

  1. Open Junê in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

6
  1. v0.8.1LatestOct 7, 2026
  2. v0.7.0Oct 4, 2026
  3. v0.6.0Sep 25, 2026
  4. v0.5.0Sep 20, 2026
  5. v0.4.3Sep 18, 2026
  6. v0.4.1Sep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.