Skip to content

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.

Teach & ask

With a pack connected to data, teach it what that data can’t say (definitions, canonical names, business meaning), then start asking.

For the fastest path from zero to real answers instead of a step-by-step walkthrough, see the Quickstart guide.

  1. Teach it a fact. teach takes exactly one of --text or --file, and returns a queued Action.

    Terminal window
    edisyl teach "$PACK" --text "An active wallet is any address with a swap in the last 30 days."
  2. Wait for it to be indexed. Ingestion is async (chunk → embed → index → organize): a teach is only “done” once its content is actually retrievable.

    Terminal window
    edisyl action watch <action-id>
  3. Ask your first question.

    Terminal window
    edisyl ask "$PACK" "What counts as an active wallet?" --wait

    --wait blocks until the answer is ready and prints it with its evidence. The server’s own window is ~60s; past that the CLI keeps polling up to --timeout (default 5m), so a slow data question still returns an answer instead of just an Action id.

ask is the answer layer for everything from here on: one natural-language question → one synthesized, cited answer over the pack’s knowledge, connections, data sources, and any readable upstream packs. You never choose data-vs-knowledge, and you never write SQL.

Terminal window
edisyl ask "$PACK" "How many swaps in the last 7 days?" --wait

Take the Action id and follow it instead of blocking:

Terminal window
action_id=$(edisyl ask "$PACK" "<slow data question>" --id-only)
edisyl action watch "$action_id" # narrates progress, then prints the answer
edisyl action get "$action_id" # read the final answer again, any time

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>.

You now have the whole loop: connect → teach → ask. Want to run through connecting, declaring objectives, and asking in one guided sitting next time? See the Quickstart.

Next: Closing gaps, covering what to do the moment ask comes back short.

Report incorrect code

Please provide a detailed description of the incorrect code.