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.

Configurator

Export or import your answers

Export writes your answers as the wizard JSON of the tool that deploys them: Helm, CloudFormation or Terraform. Import it in another browser to carry on, or hand it to a colleague. It holds no credentials, and a file exported for a different release is refused. CloudFormation parameters and Terraform variables are shown for review before anything changes.

Import a configurator export, CloudFormation parameters or a Terraform .tfvars fileOr paste it

Start from an existing Helm values file

Nothing changes until you review and apply. Values the wizard asks about fill in its answers; everything else is kept in a separateedisyl.overrides.yaml, applied after the wizard's values and before your secrets. Credential paths are dropped, never imported, and no chart version is inferred.

Helm YAML fileOr paste Helm YAML

Imported overrides

Applied after the wizard's values. Review them before installing — any path the wizard owns uses your answers instead.

Was this page helpful?

Thanks for the feedback.