Skip to content

The linked workspace for your team and its AI agents.

Specs, wikis, spreadsheets, diagrams, boards and plans live on one map of linked documents, each able to carry an owner, a due date and a review. Claude, ChatGPT and Cursor read and write it with your permissions.

Shown: Saltmarrow, a sample game project documented in Nodary.

Every project is a thousand documents. Nodary keeps them in one sky.

  1. They pile up

    The spec is in a wiki, the references on a board, the numbers in a spreadsheet, the translations in another, the decisions in a chat. Nobody, person or AI, sees the whole.

  2. Every document becomes a star

    Specs, pitches, references, sheets and translations each become a document on one map, filed in clusters you can open like folders.

  3. Links say why

    Related, inspired by, blocks, depends on: a link carries its reason, and a blocker reads the right way from either end. Producers see what waits on what.

  4. Your agents see the same sky

    Connect Claude, ChatGPT or Cursor through MCP. They read the context your team keeps and write back into it, signed in your name.

Your agents work in the same workspace. With your permissions.

Nodary runs a real MCP server. Connect Claude, ChatGPT, Cursor or Claude Code and they read the documents, sheets and decisions your team keeps, then write back: create documents, fill tables, leave notes on pictures, plan a milestone.

  • Read any document, sheet or board, with its links and history
  • Write documents, fill sheets and string tables, file and link stars
  • Review art: find what waits, look at the picture, decide with a reason
  • Plan: list what is late, who is blocked, and whether the milestone lands

Agents act as the person who connected them, with the same rights. Every decision they make is signed in that name, writes can be retried safely, and nothing an agent writes can forge who decided.

Works with any MCP client, including Claude, Claude Code, ChatGPT, Cursor, VS Code.

claude mcp add --transport http nodary https://nodary.ai/api/mcp
An example session, with the real tool names
  1. Found 3 stars.

  2. 5 pictures for changes, recently changed documents first. get_image shows one, get_moodboard a whole board.

  3. Art review in this project: 0 references undecided, 7 approved, 1 rejected; 28 deliverables (image grids, single images, boards): 2 waiting for a decision, 19 approved, 5 sent back for changes, 2 rejected; tags used most: environment (2), key-art (2), colour (1), gameplay (1), lighting (1), materials (1), props (1), target (1). List what waits with find_pictures (status undecided) and decide with update_pictures.

  4. Created star "Playtest notes" inside the requested cluster.

  5. Linked the two stars ("questions").

  6. 8 items from "Crystal" weighted by "Weight" (total 10000). Rarest: Archivist's tear at 0.2% a pull, 500 pulls on average, 1151 pulls for nine players in ten. With a guaranteed Drowned lens on pull 150: 99.1 pulls on average, 150 for nine players in ten. Every item: 543.2 pulls on average, 1155 for nine players in ten (exact).

For game studios: every craft in the same graph.

Nodary was built first for game studios. The documents that make a game are not all text: Nodary has a real tool for each of them, and links them all.

Design documents that stay true

Write the game design document as linked pages: pillars, systems, characters, levels. Mark what is canon, what is exploration and what was superseded.

  • Diagrams written as text (Mermaid), rendered live
  • Live views: a table, board or timeline of any set of documents
  • Templates for GDDs, mechanic specs, tech designs and more

Truth status is set by people; nothing is marked canon automatically.

Feedback drawn on the picture, decided once, signed.

The key art for Saltmarrow went through two versions. The first was sent back with notes drawn where they apply; the second was approved. Both decisions say who made them, and the outsourcer gets one sheet with everything.

Saltmarrow key art, version 1: gothic salt towers, a leaning rusted lighthouse and a setting sun over the flats, with three harvesters on a causeway.

Changes asked by Idris Okafor, art director

  1. 1. Too busy: lose the sun, keep one lantern glow. The lantern on the walkway has to be the only warm point.Idris Okafor
  2. 2. The Gothic arches on the left compete with the lighthouse. One silhouette per plane.Maëlle Rocher
  3. 3. Cloud texture is fighting the tower tops. Calm the sky in this band.Idris Okafor
Saltmarrow key art, version 2: white salt towers and a leaning lighthouse at dusk, one lantern glow, harvesters crossing a plank causeway.

Approved by Idris Okafor, art director

See the feedback sheet

Sample art made for the Saltmarrow showcase. The pins and marks are drawn by the same code as in Nodary.

Ask the loot table what players will feel.

This is the drop-rate maths from Nodary’s spreadsheet panel, running here. Change the weight of the rare crystal or the pity rule, and read the answer in players, not percentages.

The table: salt chunk 600, brine pearl 240, tarred rope 110, tide compass 40, and the memory crystal. Exact maths for a single item, nothing simulated.

Open the free drop-rate calculator

Chance on one pull: 1.2%

Half of players have one within
58 pulls
Nine players in ten within
192 pulls
99 players in 100 within
383 pulls
After 50 pulls, 45 players in 100 have one.

Free to start. Pay per seat as you grow.

Free holds a small team and one project with no card. Pro and Studio add projects, storage and a monthly Studio AI allowance in Comets.

See every plan
Free
€02 members, 1 project, no card
Pro
€15per seat per month, billed monthly
Studio
€29per seat per month, billed monthly

Give your team one sky.

Start free with your team, or open the live demo first. No card, no installation.