Connect Claude to Edka

Connect Claude to your Edka organization and ask it about your infrastructure directly: which clusters are running, what changed in a deployment, why a notification fired. With write access, Claude can also publish and install apps and create Codex environments.

What Claude can read

Every connection includes read access. Claude can look up:

• Organization details, plan, and cluster limits
• Clusters, worker node pools, and recent provisioning events
• Apps and add-ons installed on your clusters
• Deployments and their linked Git repositories
• Databases
• Notifications
• Agents, connected GitHub repositories, and Codex environments
• Custom apps your organization published

Read access also covers drafting a custom app. Claude can generate the starting files and check them for errors, and neither step stores anything.

Claude sees what your Edka role and cluster permissions allow, in one organization. Responses leave out app and add-on configuration values, deployment environment variable values, and database connection details and credentials.

What Claude can change

With write access, Claude can also:

• Publish a custom app, or a new version of one, to your organization’s catalog
• Install a catalog app on a cluster
• Move an installed custom or community app to another version
• Create and delete Codex environments

Claude acts as you. It can change only the clusters where you have write access, and publishing a custom app needs the Owner or Admin role. Claude can’t change an archived cluster. Cluster access explains how roles and cluster permissions combine.

Publishing a new version leaves installed apps on their current version until Claude or you update them. Edka deletes an environment Claude creates after 4 hours, unless Claude sets a different lifetime of up to 24 hours.

Choose read or write access

When you sign in, the consent screen lists read access as required and write access as an optional checkbox, checked by default. Uncheck it to connect with read access only. Claude then gets the read tools and none of the write tools.

A connection keeps the access you granted at sign-in. To change it, revoke Claude’s access as described under Removing access, then connect again and choose on the consent screen.

Connect from claude.ai

1. In claude.ai, go to Settings > Connectors
2. Click Add custom connector
3. Enter https://api.edka.io/mcp/platform and click Add
4. Sign in with your Edka account when prompted
5. Keep or uncheck write access, then click Authorize

In a chat, enable the Edka connector from the tools menu, then ask away.

Connect from Claude Code

Add the server:

claude mcp add --transport http edka https://api.edka.io/mcp/platform

In a Claude Code session, run /mcp, select edka, and complete the sign-in in your browser.

Other MCP clients that support Streamable HTTP with OAuth work the same way with the URL above.

Organization scope

The connection is bound to the organization that is active when you authorize it. To connect a different organization, make it active in the Edka console, then add the connector again.

Removing access

Remove the connector in claude.ai under Settings > Connectors, or in Claude Code with claude mcp remove edka.

To revoke Claude’s access from Edka, open Settings > Security in the Edka console and select Revoke next to Claude under Authorized applications. Claude loses access on its next request, and connecting it again asks for your approval.

Edka checks organization membership on every request, so removing someone from the organization ends their connection right away.