Ekbasis — Claude Code MCP server: what it does, how to install
Ekbasis estimates the likely results of commands and multi-step edits. It is useful when an agent is about to change Git state or run a risky action.
claude mcp add --env EKBASIS_URL=<EKBASIS_URL> --env EKBASIS_API_KEY=<EKBASIS_API_KEY> --transport stdio ekbasis -- uvx ekbasisWhat Ekbasis does
Ekbasis takes the current project state together with a proposed action and returns probability estimates for its outcome. It can assess whether a command will fail, discard work, or leave a particular state afterwards. The result is produced in one model pass without generated prose.
You can run the MCP server with uvx ekbasis and configure EKBASIS_API_KEY or EKBASIS_URL. Its training combines synthetic scenarios with actual Git command runs in disposable repositories, so the prediction is tied to observed action outcomes rather than an agent’s explanation.
The selected server receives text describing each check. Git checks include repository state, changed-file names, and commit subjects; file contents are not sent. Secret redaction covers several common patterns, but a short or unusual secret can slip through. MCP setup needs uvx, and the connection needs either a server URL or an API key.
What it helps with
- estimate whether a Git action can lose work
- check if a proposed command is likely to fail
- predict repository state after a multi-step change
- give an agent a probability for an action’s consequences
Example prompts for the agent
- Ask Ekbasis whether this Git command could discard the current changes before running it.
- Use Ekbasis to estimate the chance that the proposed multi-step edit will fail.
- Have Ekbasis predict the repository state after this action and return the relevant probabilities.
How to install Ekbasis
Platform CLI
claude mcp add --env EKBASIS_URL=<EKBASIS_URL> --env EKBASIS_API_KEY=<EKBASIS_API_KEY> --transport stdio ekbasis -- uvx ekbasisReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from ekbasis <command>
Platform CLI
codex mcp add ekbasis --env EKBASIS_URL=<EKBASIS_URL> --env EKBASIS_API_KEY=<EKBASIS_API_KEY> -- uvx ekbasisReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from ekbasis <command>
Config file
{
"mcpServers": {
"ekbasis": {
"command": "uvx",
"args": [
"ekbasis"
],
"env": {
"EKBASIS_URL": "<EKBASIS_URL>",
"EKBASIS_API_KEY": "<EKBASIS_API_KEY>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from ekbasis <command>
Config file
{
"servers": {
"ekbasis": {
"type": "stdio",
"command": "uvx",
"args": [
"ekbasis"
],
"env": {
"EKBASIS_URL": "<EKBASIS_URL>",
"EKBASIS_API_KEY": "<EKBASIS_API_KEY>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from ekbasis <command>
Platform CLI
gemini mcp add -e EKBASIS_URL=<EKBASIS_URL> -e EKBASIS_API_KEY=<EKBASIS_API_KEY> ekbasis uvx ekbasisReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from ekbasis <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Ekbasis
How do I install Ekbasis in Claude Code?
Add the MCP server with claude mcp add ekbasis -e EKBASIS_API_KEY=<EKBASIS_API_KEY> -- uvx ekbasis. Replace the placeholder with your API key.
What does Ekbasis do?
It predicts the consequences of an agent action from the current project state, including possible work loss, command failure, and the resulting state.
What information does Ekbasis send to its server?
The chosen server receives text describing the check. Git requests include repository state and changed-file metadata, while file contents stay local; redaction still has limits.
