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.

edisyl teach

Terminal window
edisyl teach <pack> --text "<fact>"
edisyl teach <pack> --file <path>

Teach the pack what the data can’t express: definitions, canonical names, business meaning, decisions. Takes exactly one of --text or --file, and returns a queued Action.

Flags

Section titled “Flags”
Flag Behavior
--text "<fact>" A direct statement to teach. Mutually exclusive with --file.
--file <path> A document to ingest: pdf, md, txt, and more. Mime type is inferred from the extension.
--wait Block until the Action is terminal.
--id-only Print the bare Action id for scripting.
-j, --json Machine-readable output.

What happens after

Section titled “What happens after”

Ingestion is async: chunk → embed → index → organize. The Action goes terminal when the content is actually retrievable: that’s what you wait for, not just upload success.

Terminal window
edisyl teach "$PACK" --file ./domain-notes.md
edisyl action watch <action-id>      # follow until indexed

A topic can be served entirely from knowledge, entirely from data, or a mix; that weighting is an authoring choice, not something the CLI decides for you.

Never write to a pack without confirming with whoever owns it first: a wrong page poisons every future answer. See Closing gaps for the confirm-then-teach pattern.

Undo

Section titled “Undo”
Terminal window
edisyl forget <pack> <content-record-id>

Removes one ingested document and every piece of knowledge placed from it (the true inverse of teach). The content record id comes from edisyl action trace <teach-action-id>. See forget.

Report incorrect code

Please provide a detailed description of the incorrect code.