Skip to content
edisyledisyl

Search these docs from your AI tool

  • Antigravity
    {
  "mcpServers": {
    "edisyl-docs": {
      "serverUrl": "https://docs.edisyl.com/mcp"
    }
  }
}
  • Claude CodeCLI
    claude mcp add edisyl-docs https://docs.edisyl.com/mcp --transport http --scope user
  • CodexCLI
    codex mcp add --url https://docs.edisyl.com/mcp edisyl-docs
  • Cursor
    {
  "mcpServers": {
    "edisyl-docs": {
      "type": "http",
      "url": "https://docs.edisyl.com/mcp"
    }
  }
}
  • Gemini CLI
    gemini mcp add --transport http edisyl-docs https://docs.edisyl.com/mcp
  • Goose
    {
  "extensions": {
    "edisyl-docs": {
      "enabled": true,
      "name": "edisyl-docs",
      "type": "streamable_http",
      "uri": "https://docs.edisyl.com/mcp",
      "envs": {},
      "env_keys": [],
      "headers": {},
      "description": "",
      "timeout": 300,
      "bundled": null,
      "available_tools": []
    }
  }
}
  • JetBrains AI Assistant
    {
  "mcpServers": {
    "edisyl-docs": {
      "type": "http",
      "url": "https://docs.edisyl.com/mcp"
    }
  }
}

    Paste into Settings → Tools → AI Assistant → Model Context Protocol → Add → As JSON. Direct file writing isn’t supported — JetBrains stores this per-version as XML.

  • Junie (JetBrains)
    {
  "mcpServers": {
    "edisyl-docs": {
      "url": "https://docs.edisyl.com/mcp"
    }
  }
}
  • OpenCode
    {
  "mcp": {
    "edisyl-docs": {
      "type": "remote",
      "url": "https://docs.edisyl.com/mcp"
    }
  }
}
  • VS CodeCLI
    code --add-mcp '{"name":"edisyl-docs","type":"http","url":"https://docs.edisyl.com/mcp"}'
  • Windsurf
    {
  "mcpServers": {
    "edisyl-docs": {
      "serverUrl": "https://docs.edisyl.com/mcp"
    }
  }
}

    Supports both stdio and native HTTP connections.

Looking to ask a pack from your AI tool instead? That's a different server: see AI clients.

The Lexicon

The Lexicon is the set of terms a pack uses to read every question. Each term points to the exact table, value, or document that a word means. With terms, “AR” and “receivables” point to the same measure, however someone phrases the question. The Lexicon has more effect on answer quality than anything else. When a pack’s sources already contain the fact, most wrong answers come from misreading the question. A new document does not fix a misread.

Find it under Lexicon on the pack page, or with edisyl pack vocabulary in the CLI. In an AI chat client, the assistant uses the lexicon_ tools.

What a term is

Section titled “What a term is”

A term has a preferred label (“Active supplier”), the other labels people use (“live vendor”), an optional definition, and a binding. The binding is what the word means in the pack. A term can bind to:

  • a model, a measure, or a dimension in a data source,
  • one value of a dimension,
  • a topic drawn from the pack’s documents,
  • a line of steering, such as a word that dates a period.

edisyl writes most terms when it compiles your documents and data. It learns more terms from questions. The listing marks each term as confirmed (a person reviewed it) or machine-made. A later compile may reword a machine-made term. It never rewords a confirmed term, and it never brings back a term you removed.

Fix a misread

Section titled “Fix a misread”

  1. See how the pack reads the question. preview shows what each word matched and what it’s bound to, without running an ask:

    The assistant calls lexicon_preview.

    “How does the books pack read ‘AR aging for written off invoices’?”

  2. Choose the edit that fits the miss.

    Miss Edit
    A word matches nothing, or the wrong model, measure, or value create a term that points to the right element. If that element already has a term, the new word is added to it as another label.
    A term is bound to the right thing, but its name or definition is wrong rename or define
    Two terms are spellings of one thing merge
    One word is a label on two terms, and the pack asks which one you meant unlabel the word from the term it doesn’t mean
    A machine-made term is junk, such as a topic that uses a file name remove
    A word means something only beside another (“units” beside orders) create with --reads and --beside
    A verb should set the period on one date column (“shipped last quarter” uses the ship date) create with --date-event

  3. Make the edit. For example, on an accounting pack:

    The assistant calls lexicon_create.

    “In the books pack, make ‘AR’ mean the invoices amount due, and also answer to ‘receivables’.”

  4. Confirm the fix. Run preview on the question again. Check that the word now matches the term you meant. Then ask the same question again. Calibration picks up the edit automatically and regrades the questions the edit affects.

Every edit

Section titled “Every edit”

Ask for the edit in chat. The assistant calls the matching tool.

To The assistant calls
List terms, or find terms that mention a word lexicon_list
Read one term lexicon_term
Create a term or add a label lexicon_create
Rename a term or set its definition lexicon_edit
Merge two terms lexicon_merge
Take a label off a term lexicon_unlabel
Confirm a term lexicon_confirm
Remove a term lexicon_remove

“Merge ‘monthly actives’ into ‘active wallet’ in the growth-metrics pack.”

Get model and member names from show and preview. Write them exactly as the pack’s catalog writes them. The CLI refuses an element that the data source’s semantic models don’t contain. Every edit is recorded under your name. Renaming, defining, or merging into a term also confirms it. Edits need manage_pack on the pack. Without it, the CLI returns “not found”.

On a pack built from documents alone

Section titled “On a pack built from documents alone”

On these packs, every term is bound to a topic drawn from the documents. The edits that apply are rename, define, merge, unlabel, and remove. The Lexicon helps the pack recognize a reworded question it has answered before. It doesn’t control which passage an answer reads. When a document pack reads the wrong passage, point that kind of question at the right document under # Routing in PACK.md.

What doesn’t belong here

Section titled “What doesn’t belong here”
The problem Where it goes
“Last quarter” is read against today instead of the data’s last day PACK.md As of:
The tone or format of answers PACK.md # Answer style
The pack used the wrong source PACK.md # Routing
A fact no source in the pack states teach the document that states it

Don’t teach a definition as a note. A note becomes a document that answers cite. A term changes how every question that uses the word is read.

Start with the terms your team disagrees about, such as “active”, “revenue”, or “region”. A general reading most often gets these wrong.

See edisyl pack vocabulary for every flag.

Report incorrect code

Please provide a detailed description of the incorrect code.