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.

Deployment readiness checklist

What you need before installing Edisyl in your AWS environment using our Helm chart. Once the required items are ready, we’re ready to schedule your install.

Deployment details Customer information
Client
Client ID (provided by Edisyl)
Base domain
Technical contact
Target install date

1. Registry access

Section titled “1. Registry access”

Edisyl’s Helm chart and images are pulled from our private registry through an IAM role we create for you. See Registry access.

  • You send us: AWS account ID and the IAM principal ARN of the role or user that will pull images (not an SSO role).

  • We send you: Client ID, Role ARN and External ID.

2. Installer access and tools

Section titled “2. Installer access and tools”

See Prerequisites.

  • Installer access: someone with AWS and Kubernetes permissions to configure the required resources and install the Helm chart, with kubectl, Helm 3.8+ and AWS CLI available.

3. AWS infrastructure and databases

Section titled “3. AWS infrastructure and databases”

See Prerequisites and Using your own infrastructure.

  • EKS cluster: Kubernetes 1.28 or later, with a working StorageClass for any bundled services that need persistent storage.

  • RDS PostgreSQL 16: four logical databases (services, auth, inngest, bifrost), each with its own owning user.

    • These do not require four separate RDS instances.
    • The auth user needs CREATEROLE.
    • The services database needs vector, pg_trgm and pg_stat_statements enabled by an administrator before installation.

  • S3 bucket and workload IAM access: a bucket for files and documents, plus IAM permissions for S3 and Bedrock if used.

  • Redis: use the chart’s bundled Redis, or provide your own with RediSearch and RedisJSON.

4. Secrets

Section titled “4. Secrets”
  • Secrets management: choose how deployment credentials and signing keys will be stored, with access to configure them. Follow the secrets guide during setup.

5. Networking

Section titled “5. Networking”

See Prerequisites.

  • DNS, ingress and TLS: a domain with DNS you control, NGINX ingress controller or Istio (Gateway API), and certificates for edisyl.<domain>, api.<domain> and auth.<domain>.

  • Connectivity: the cluster can reach the registry, databases, storage and selected LLM provider. Intended users can reach the application, including through a VPN if required.

6. Sign-in

Section titled “6. Sign-in”

See Authentication.

  • SAML 2.0 identity provider: Okta, Entra ID, Google Workspace or similar, with an identity-provider administrator available to configure the integration.

  • Initial admin email(s): who signs in first and owns the workspace.

7. LLM provider and required models

Section titled “7. LLM provider and required models”

See The LLM gateway.

  • AWS Bedrock model access, or API keys for your LLM provider.
Model name Use
anthropic/claude-haiku-5-5 chat
anthropic/claude-sonnet-5-5 chat
anthropic/claude-opus-5-5 chat
bedrock/cohere.embed-v4:0 embeddings, 1536 dimensions

8. Email (optional)

Section titled “8. Email (optional)”

See Email.

  • AWS SES verified sender address: for invitations and notifications.

Report incorrect code

Please provide a detailed description of the incorrect code.