Saves a declared investment strategy so any agent can check a portfolio against it.
One address for any MCP client. You sign in at kovatools.com once, after adding it.
At most: only reads or looks up information.
Odel charges nothing per call. The publisher may charge for its own service.
Odel could not list its tools without signing in.
Kova is the strategy layer for agentic investors. It gives compatible AI agents a persistent investment strategy, a shared way to check portfolio alignment, and a clear approval boundary before Kova saves a strategy or creates a brief.
Explore Kova · Install the Agent Plugin
Strategy → approval → portfolio → brief
The plugin packages Kova's strategy workflows and secure MCP connection for clients that support Agent Plugins v1. It connects to Kova's hosted service, so there is no local server to build and no API key to place in a file.
Kova asks for explicit approval before it saves a strategy, records portfolio assets or liabilities, or creates a brief. It does not execute trades, make market predictions, or choose securities for you.
Authentication happens through Kova's OAuth flow. The plugin contains no credentials, authorization headers, tokens, or client-specific OAuth configuration. Strategy text, holdings, and account data stay out of the plugin package.
The published Kova app in ChatGPT is a separate distribution channel. Installing that app does not install this Agent Plugin, and installing this Agent Plugin does not add the ChatGPT app.
The directory containing plugin.json is the plugin root. Install the repository root, not its skills/ directory.
claude plugin marketplace add kovatools/kova-agent-plugin
claude plugin install kova@kova
Run /mcp once to sign in to Kova. To try it without installing, start a session with claude --plugin-dir /absolute/path/to/kova-agent-plugin.
gemini extensions install https://github.com/kovatools/kova-agent-plugin
The extension connects to https://kovatools.com/mcp and signs in through Kova's OAuth flow on first use.
VS Code can clone and install a plugin from its repository URL:
chat.plugins.enabled setting.https://github.com/kovatools/kova-agent-plugin.To update, run Extensions: Check for Extension Updates. VS Code also checks automatically when extension auto-update is enabled. To uninstall, find Kova under Agent Plugins - Installed, open its context menu, and select Uninstall.
For a local clone instead, register the plugin root in VS Code settings:
{
"chat.pluginLocations": {
"/absolute/path/to/kova-agent-plugin": true
}
}
See Agent plugins in VS Code for the current UI and settings.
Cursor loads local plugins from ~/.cursor/plugins/local:
mkdir -p ~/.cursor/plugins/local
git clone https://github.com/kovatools/kova-agent-plugin.git ~/.cursor/plugins/local/kova
Restart Cursor or run Developer: Reload Window. For development, you can clone elsewhere and symlink the repository root instead:
ln -s /absolute/path/to/kova-agent-plugin ~/.cursor/plugins/local/kova
To update a cloned copy, run git -C ~/.cursor/plugins/local/kova pull --ff-only, then reload Cursor. To uninstall, remove only the kova clone or symlink from ~/.cursor/plugins/local, then reload Cursor. See Cursor Plugins for the current local-plugin flow.
Clone a release, then copy or symlink the repository root into the directory your client scans for plugins:
git clone --branch v0.1.1 --depth 1 https://github.com/kovatools/kova-agent-plugin.git
If Git is unavailable, download the v0.1.1 source archive from GitHub, extract it, and register the extracted repository root as a local plugin directory.
Registration, update, and uninstall behavior belongs to the client because Agent Plugins v1 defines the package format, not a universal installer. Consult the compatible clients list and your client's documentation. To update a clone tracking main, use git pull --ff-only; for an immutable release, replace the clone with a newer SemVer tag. To uninstall, unregister the plugin root and remove only that local clone or symlink.
The first time a client connects to https://kovatools.com/mcp, it should open Kova's OAuth authorization flow:
Kova uses OAuth with PKCE. Local clients may use an exact http://localhost, http://127.0.0.1, or http://[::1] callback. Cursor may also use its exact native callback, cursor://anysphere.cursor-mcp/oauth/callback; every other callback must use HTTPS. An active Kova subscription is required for MCP access.
To revoke a connection, remove its Kova API token from your account. Uninstalling the plugin does not revoke an already issued token.
Use immutable GitHub Releases for repeatable installs and version-specific compatibility notes. To report an installation problem, client compatibility issue, or workflow bug, open an issue.
MIT