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.

Install & log in

edisyl runs in your own environment, so after installing the CLI you point it at your install’s API host and log in. Your edisyl admin has the host, usually https://api.<your-domain>.

  1. Install the CLI.

    Terminal window
    curl -fsSL https://cli.edisyl.com/install.sh | sh
  2. Point the CLI at your edisyl and log in.

    Terminal window
    edisyl profile create work --endpoint https://api.<your-domain> --use
    edisyl login --profile work

    The first command saves your API host as a profile and makes it active. The second opens your browser to sign in, then saves the session for future commands.

  3. Confirm who and where you are.

    Terminal window
    edisyl whoami

    This prints your user and workspace. The workspace (org) is already provisioned: you’re joining it, not creating it.

    Run edisyl help to see the main commands, or edisyl <command> --help for any one of them.

Run edisyl onboard and give your agent the output. It prints a self-contained guide to driving edisyl from the CLI: connecting a data source, teaching a pack, asking it questions, and tasking it with work. It needs no login and works offline.

There are two ways to switch:

  • Log out and log back in. Run edisyl logout, then edisyl login and sign in with a different organization. This is simplest when you only move between them occasionally.
  • Create a profile for each environment. A profile stores an endpoint, its sign-in session, and the selected org under one name. You can switch profiles without signing in again.

To add a profile for another environment, such as a staging install, create it the same way as above and log in to that profile. Order matters: a bare edisyl login authenticates default, not work.

Three ways to select a profile, highest priority first:

Selector Use when
--profile <name> / -p <name> One-off override on a single command
EDISYL_PROFILE=<name> Persistent for a shell session or in CI
edisyl profile use <name> Change the default for all future commands

Tip: capture ids from any command with -j | jq -r '.id'. Every command supports -j/--json.

Next: Connect a data source.

Report incorrect code

Please provide a detailed description of the incorrect code.