Repository navigation
Releases
MyGraph 0.3.1
You can now install MyGraph with one command and add it to Claude Code as a plugin. It is also listed in the official MCP Registry.
One-line install
curl -fsSL https://raw.githubusercontent.com/dieron/mygraph/main/install.sh | shirm https://raw.githubusercontent.com/dieron/mygraph/main/install.ps1 | iex- What they install. The installers download the release and the embedding model, check both against
SHA256SUMS, and install for your user only. No admin rights are needed. - Platforms. Linux x86_64 and aarch64, macOS on Apple silicon, and Windows x86_64.
- Autostart. The server starts at login and listens on
127.0.0.1:7420. It runs as a systemd user service on Linux, a launchd agent on macOS and a scheduled task on Windows. - Upgrading. Run the installer again. It keeps your data and
server.toml. - Removing.
--uninstallstops the server and removes it from autostart. The folder stays, with the program, your graphs andserver.toml. - Options.
--version,--port,--dir,--no-modeland--no-service. On Windows they are-Version,-Portand so on. Pass them to a downloaded copy of the script.
Claude Code plugin
claude plugin marketplace add dieron/mygraph
claude plugin install mygraph@mygraph- The plugin connects Claude Code to your server's MCP endpoint and installs the
mygraphskill. - It has two options: the server address (default
http://127.0.0.1:7420) and an API key, which is needed only if the server has keys.claude plugin configure mygraph@mygraphshows them, and--values-stdinsets them.
MCP Registry
MyGraph is listed as io.github.dieron/mygraph in the MCP Registry. The entry runs the Docker image as a stdio MCP server, with the graphs in a volume:
docker run -i --rm -v mygraph-data:/data ghcr.io/dieron/mygraph:latest mcp --data-dir /dataEvery release now updates the entry automatically.
Fixes
mygraph mcp --data-dir now works in the Docker image. The image's network settings (a public listen address, which needs keys) used to stop every command. Now only serve checks them, and it still refuses a public address without keys.
Upgrading from 0.3.0
Nothing changes in storage, configuration or the API.
Downloads
Download the archive for your platform and the embedding model, and unpack the model next to the mygraph binary. The installers above do this for you. Docker: ghcr.io/dieron/mygraph:0.3.1.
Full changelog: v0.3.0...v0.3.1
MyGraph 0.3.0
Your graphs can now be used from claude.ai on the web and on your phone, and from your own apps on the Claude and OpenAI APIs, while they stay on your own machine. Each graph also gets its own access: private, read-only or writable, per key.
Connect claude.ai, Claude Desktop and the phone apps (OAuth)
- The server is its own OAuth sign-in for remote MCP clients. In claude.ai, add a custom connector with
https://<your host>/mcp; MyGraph's page asks for one of your API keys, with an option to sign in read-only. The connector then works in claude.ai, Claude Desktop and the Claude phone apps. - Turn it on with the server's public address:
[oauth] public_urlinserver.toml, orMYGRAPH_OAUTH_PUBLIC_URL. - Public listener.
[oauth] listen(MYGRAPH_OAUTH_LISTEN) opens a second port that serves only/mcp,/oauth/and/.well-known/, and answers 404 to everything else. Point your reverse proxy at it, so a proxy rule that forwards too much still cannot reach the REST or admin API, the stats page or/ready. GET /admin/oauthlists the apps signed in, andDELETE /admin/oauth/grants/{id}signs one out. Removing a key signs out every app that used it.- Claude Code can connect the same way:
claude mcp add --transport http mygraph https://<your host>/mcp.
Use your graphs from cloud AI
The README's new section, Using your graphs from cloud AI, shows how a server on your laptop or home server serves AI that runs elsewhere: local clients, claude.ai, the Claude API's MCP connector and OpenAI's remote MCP tool, each with a key of its own.
Who may use a graph
- Each graph is private, public and read-only, or public and writable (the default), and single users (a key's actor) can have their own level. Set it with
POST /admin/graphs/{g}/access, or ask an agent with an admin key to use thegraphstool's newaccessaction. GET /v1/graphsand thegraphstool show each key only the graphs it may read, marking the read-only ones.- Keys that create graphs. An
agent-writekey withcreate_graphs = truemay create graphs, and keeps write access to the ones it creates. Only admins change access. - With Docker, a
server.tomlcan now be mounted (MYGRAPH_CONFIG_DIR,MYGRAPH_CONFIG), for keys with their own actors, graphs orcreate_graphs.
Stats page
The stats page shows who may use each graph ("private", "all keys: write", and each key's own level), the configured keys (actors and roles, never the keys) with the graphs each can read or write, and the apps signed in with OAuth.
Upgrading from 0.2.0
- Nothing changes unless you configure it: graphs stay public and writable for every key, and OAuth stays off. Storage is unchanged; access and sign-ins are kept in a new
<data_dir>/server.db. - Update the
mygraphbridge program on client machines to get thegraphstool'saccessaction (the bridge lists the tools itself), then restart the Claude apps. compose.yamlnow also publishes port 7421 for the public listener. If that port is taken on the host, setMYGRAPH_OAUTH_PORTin.env.
Downloads
Download the archive for your platform and the embedding model, and unpack the model next to the mygraph binary. The Quick start explains each step. Docker: ghcr.io/dieron/mygraph:0.3.0.
Full changelog: v0.2.0...v0.3.0
MyGraph 0.2.0
MyGraph can now serve HTTPS itself, so a server on your network no longer needs a reverse proxy to keep keys and data encrypted.
HTTPS
- Give the server a certificate and key, and it speaks HTTPS on its usual address:
[tls] certandkeyinserver.toml, orMYGRAPH_TLS_CERTandMYGRAPH_TLS_KEY. - A renewed certificate (from certbot, acme.sh or a NAS) is picked up within a minute, without a restart.
- The
mygraph mcpbridge acceptshttps://URLs. For a self-signed certificate or a private CA, pass--ca-cert <file.pem>or setMYGRAPH_CA_CERT. - A client that still uses
http://gets a clear error (api.https_required) telling it to switch, instead of garbled output. - With Docker,
compose.yamlmounts a certificate folder (MYGRAPH_CERTS); see.env.example. - Without a certificate, a server listening beyond its own machine logs a warning that traffic is unencrypted.
The README's new HTTPS section shows how to set this up, including a one-line command for a self-signed certificate.
Upgrading from 0.1.0
Nothing changes unless you set a certificate: the server keeps speaking plain HTTP, and storage is unchanged. If you turn HTTPS on, switch every client to https://, and update the mygraph bridge program on client machines to this version, because the 0.1.0 bridge can't connect to an HTTPS server.
Downloads
Download the archive for your platform and the embedding model, and unpack the model next to the mygraph binary. The Quick start explains each step. Docker: ghcr.io/dieron/mygraph:0.2.0.
Full changelog: v0.1.0...v0.2.0
MyGraph 0.1.0
Full Changelog: https://github.com/dieron/mygraph/commits/v0.1.0