Documentation

ShruggieGraph is a portable memory for your AI assistants. You store what matters once, and it stays available across chats and across the assistants you use — under your control.

This page is the front door: a plain-language overview here, connection guidance, the skill download, and a reference for the public endpoints. Each section below fills in as it ships.

Connecting an AI assistant to ShruggieGraph takes one of two paths. Both end up governed by the same scopes and permissions — nothing a connected client does can exceed what you grant.

Option 1 — Connect from claude.ai (recommended)

1. In claude.ai, open Settings → Connectors and choose Add custom connector.
2. Enter your ShruggieGraph server address with the /api/mcp path — for example https://graph.shruggie.tech/api/mcp.
3. Your browser opens a ShruggieGraph consent page. Review the requested scopes, confirm access to your personal memory, and click Allow access.

The connection then appears on your Integrations page, where you can revoke it at any time.

Option 2 — Connect a desktop client with a token

1. Sign in and create a token on the Integrations page with the scopes your client needs (search plus note-saving covers most memory use). The secret is shown once — copy it then.
2. Point your client at the MCP endpoint. Clients that speak stdio (such as Claude Desktop) use the bundled mcp-stdio adapter from the ShruggieGraph CLI, with the token supplied through the SHRUGGIE_MCP_TOKEN environment variable.
3. Start the client; the token authenticates every request.

Creating a token requires signing in — it is an account action on the Integrations page, not something done from this page.

Which assistants work today

We are honest about what we have actually verified. Claude is confirmed end to end; other MCP-capable clients may work but we have not verified them and cannot promise they connect.

The shruggie-graph-memory skill teaches an assistant to use ShruggieGraph on its own — to save durable facts as you talk and to look things up in your memory when a topic calls for it. It drives the ShruggieGraph MCP tools, which are the same across assistants, so it is a single provider-agnostic package. Connect the tools first (see above); the skill is the instructions that tell your assistant to use them.

Download the zip below, then install it into your assistant:

Install guidance

• Claude Desktop / claude.ai (verified). Add the skill through Claude's skill mechanism (a per-skill zip upload, or a symlink for a coding agent). This is the path we run and verify.
• Gemini (verified). Gemini fully accepts the currently-distributed skill package with no issues.
• Grok (verified). Grok fully accepts the currently-distributed skill package with no issues.
• ChatGPT (not yet verified). ChatGPT accepts uploadable skills (Skills → Upload from your computer), and the package includes the icon and folder layout it expects — but we have not verified this end to end yet, so treat it as experimental.
• Other assistants (not yet verified). Any client that can load a skill and speak MCP may be able to use it, but we have not verified these and cannot promise they work.

The download always reflects the current skill source — there is no separate copy to fall out of date.

The two endpoints documented here are public and need no authentication. The authenticated REST API is documented separately — see the end of this section.

GET /api/version

Reports the running service's build version. Public, no authentication. Returns 200 with the service name and its current build version (the value below is an example):

{ "name": "shruggiegraph-api", "version": "1.4.0" }

GET /api/health

A lightweight database-reachability check — it confirms the service can reach its database, not that every migration has applied or that the service is fully ready. Public, no authentication. Returns 200 with { "status": "ok" } when the database is reachable, or 503 with { "status": "unhealthy" } when it is not:

{ "status": "ok" }

Authenticated API access

There is a REST API for working with your knowledge programmatically, and it is available today. Its full interactive reference — every endpoint, its parameters, and a try-it-out client — lives at /docs inside the console. You will need to sign in to read it. Mint a token for it on the Integrations page, then send it as a bearer token.

Treat the surface as unstable while ShruggieGraph is in alpha. It currently exposes 25 read-oriented operations, it is versioned only by the build number reported above, and endpoints and response shapes may change without notice. There is no deprecation window and no compatibility guarantee between builds. If you would rather not track that, connect an AI assistant through the steps in Connect your AI assistant above instead.