MCP

The @nesso-how/mcp package is a Model Context Protocol server that gives AI clients access to Nesso documentation and the full relation-type vocabulary. Once connected, models can answer questions about how Nesso works and use the correct relation names when you build graphs yourself in the app or in JSON.

Setup

Claude Desktop

Open claude_desktop_config.json. On macOS it lives at ~/Library/Application Support/Claude/claude_desktop_config.json; on Windows at %APPDATA%\Claude\claude_desktop_config.json.

Add a nesso entry under mcpServers:

{
  "mcpServers": {
    "nesso": {
      "command": "npx",
      "args": ["-y", "@nesso-how/mcp"]
    }
  }
}

Save the file and restart Claude Desktop. The Nesso tools will be available to the model automatically.

Cursor

Open Settings -> MCP and add a new server with command npx and args ["-y", "@nesso-how/mcp"].

Other MCP clients

Any client that speaks the stdio MCP transport works. Run npx -y @nesso-how/mcp as the server command. No other configuration is required.

What it can do

Once connected, you can ask your AI client things like:

• “What relation types does Nesso support?” (uses get_relation_types)
• “Show me the Nesso getting started guide” (uses get_nesso_docs)

You can build graphs in app.nesso.how yourself, or paste graph JSON from the model via Graph menu → Import JSON when it follows the shape below.

Tools reference

get_nesso_docs

Fetches documentation pages from this site. Call it without a slug to get a table of contents, or with a slug (e.g. "guides/getting-started") to get the full page content.

get_relation_types

Returns the complete list of relation types with their category, line style, symmetry, and semantic coefficients (transitive, inverse, strength, polarity, cardinality). Use this whenever you need valid type names for graph JSON or explanations for the learner.

Graph JSON (Import JSON)

Paste this JSON shape into Graph menu → Import JSON in the web or desktop app (or construct it elsewhere and import the file). Import keeps structure (nodes, edges, display, elaboration) and resets FSRS / review fields to fresh defaults — personal scheduling from another user is not applied. Export JSON from the graph menu is share-safe the same way (no review history). Desktop workspace autosave is separate and retains your full progress.

{
  "name": "Graph title",
  "nodes": [
    {
      "id": "n1",
      "type": "concept",
      "position": { "x": 0, "y": 0 },
      "data": {
        "text": "Concept label",
        "stability": 0,
        "difficulty": 0,
        "reps": 0,
        "lapses": 0,
        "fsrsState": 0,
        "due": 0,
        "lastReview": 0,
        "lastRating": 0
      }
    }
  ],
  "edges": [
    {
      "id": "e1",
      "type": "nesso",
      "source": "n1",
      "target": "n2",
      "sourceHandle": "out",
      "targetHandle": "in",
      "data": { "type": "causes" }
    }
  ]
}

Call get_relation_types before inventing data.type values so they match Nesso.