Skip to content

MyGraph 0.3.0

Choose a tag to compare

@github-actions github-actions released this 20 Nov 05:22
· 9 commits to main since this release

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_url in server.toml, or MYGRAPH_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/oauth lists the apps signed in, and DELETE /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 the graphs tool's new access action.
  • GET /v1/graphs and the graphs tool show each key only the graphs it may read, marking the read-only ones.
  • Keys that create graphs. An agent-write key with create_graphs = true may create graphs, and keeps write access to the ones it creates. Only admins change access.
  • With Docker, a server.toml can now be mounted (MYGRAPH_CONFIG_DIR, MYGRAPH_CONFIG), for keys with their own actors, graphs or create_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 mygraph bridge program on client machines to get the graphs tool's access action (the bridge lists the tools itself), then restart the Claude apps.
  • compose.yaml now also publishes port 7421 for the public listener. If that port is taken on the host, set MYGRAPH_OAUTH_PORT in .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