Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Saves a declared investment strategy so any agent can check a portfolio against it.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://kovatools.com/mcpRun this in your terminal
claude mcp add --transport http kova https://kovatools.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"kova": {
"url": "https://kovatools.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"kova": {
"type": "http",
"url": "https://kovatools.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://kovatools.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain kovatools.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.10.1) reached the registry 24 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, topo^alpin
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Avalanche bulletins and mountain weather forecasts for any place in the Alps.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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