Install it
Cluster prerequisites, registry access, and the Helm flags that matter, including the one that can delete your database. Start with prerequisites →
Search these docs from your AI tool
{
"mcpServers": {
"edisyl-docs": {
"serverUrl": "https://docs.edisyl.com/mcp"
}
}
}claude mcp add edisyl-docs https://docs.edisyl.com/mcp --transport http --scope usercodex mcp add --url https://docs.edisyl.com/mcp edisyl-docs{
"mcpServers": {
"edisyl-docs": {
"type": "http",
"url": "https://docs.edisyl.com/mcp"
}
}
}gemini mcp add --transport http edisyl-docs https://docs.edisyl.com/mcp{
"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": []
}
}
}{
"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.
{
"mcpServers": {
"edisyl-docs": {
"url": "https://docs.edisyl.com/mcp"
}
}
}{
"mcp": {
"edisyl-docs": {
"type": "remote",
"url": "https://docs.edisyl.com/mcp"
}
}
}code --add-mcp '{"name":"edisyl-docs","type":"http","url":"https://docs.edisyl.com/mcp"}'{
"mcpServers": {
"edisyl-docs": {
"serverUrl": "https://docs.edisyl.com/mcp"
}
}
}Supports both stdio and native HTTP connections.
One Helm chart deploys the edisyl platform, the services and the datastores they need, on a Kubernetes cluster you run. Installing for the first time? Start with the prerequisites and work down the Guides in order. Already running it? The changelog and upgrading are what you want.
Install it
Cluster prerequisites, registry access, and the Helm flags that matter, including the one that can delete your database. Start with prerequisites →
Configure your install
Answer a few questions about your cluster, what you bring and what the chart bundles, and get the values file to install with. Open the configurator →
Every value, once
The full values reference, generated from the chart’s own values.yaml so it cannot drift.
Read the values reference →
What ships in production
The exact image tag every service runs at each published chart version, and what changed between them. See the image matrix →
Was this page helpful?
Thanks for the feedback.