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 login, whoami & profile

Terminal window
edisyl login [--profile <name>]
edisyl whoami
edisyl profile create <name> --use
edisyl profile use <name>
edisyl api-keys create

Profiles

Section titled “Profiles”

A profile bundles endpoint + auth + selected org under one name: it’s the only thing that actually switches environments, because each environment has its own auth session. -e/--env is an endpoint URL shortcut and does not switch auth; pointing it at an environment you haven’t logged into fails with unauthenticated.

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

A bare edisyl login authenticates default, not any profile you’ve created; pass --profile explicitly if you’re not working against default.

Non-interactive / CI

Section titled “Non-interactive / CI”

Set EDISYL_API_KEY (and optionally EDISYL_API_URL). No profile needed. Mint keys with edisyl api-keys create.

Global flags

Section titled “Global flags”
Flag Behavior
-j, --json Machine-readable output on every command.
--quiet Drop hints and banners on action/schedule read commands, keep the data.

<command> --help is authoritative for anything not covered here.

Permissions

Section titled “Permissions”

The CLI enforces nothing client-side: it calls the endpoint and shows you what came back, including a 403. What you’re allowed to do depends on your org role and your capabilities on the target pack. Treat a 403 as “not your permission,” not a broken command or a bad argument: don’t retry with different flags.

pack context (PACK.md writes) has a related but different failure mode: without owner access, the API answers “not found” rather than “forbidden.”

Report incorrect code

Please provide a detailed description of the incorrect code.