Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Ikuna
Overview
Description from the maker (original English)
Read workspace context and activity from the running Ikuna macOS app, with app-managed permissions.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"ikuna": {
"command": "npx",
"args": [
"-y",
"ikuna-mcp"
]
}
}
}Run this in your terminal
claude mcp add ikuna -- npx -y ikuna-mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ikuna": {
"command": "npx",
"args": [
"-y",
"ikuna-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.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"ikuna": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ikuna-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.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
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.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account RobertoHanas, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 18354 servers in this category
- Published to the registry more recently than 46% of the other 18354 servers in this category
- Basic checks equal to or better than 100% of the other 18354 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Ikuna safe?
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.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 2 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Qemu MCP
Alternatives
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
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated 2 days ago
Install
Qemu MCP
by 0xmortuex
Boot and drive QEMU VMs from an AI agent: keys, screenshots, serial. No guest agent.
Runs on your computerUpdated today
Install
README from the maker
Open the README
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.
Ikuna MCP
Connect your AI client to the workspace context in the Ikuna app running on your Mac.
ikuna-mcp 0.1.1 is listed in the official MCP Registry as io.github.RobertoHanas/ikuna-mcp.
Connect
- Install Node.js 18 or later, including
npx. - Open Ikuna and enable the capabilities you want to share in Settings → AI Connections.
- Run the guided setup:
npx -y ikuna-mcp setupSetup detects Claude Desktop, Codex, Claude Code, and Cursor, merges only Ikuna's entry into their existing configuration, retains the latest three backups, and verifies the local MCP handshake. Re-run the same command to repair stale or missing values, or make that intent explicit:
npx -y ikuna-mcp setup --repairnpx -y ikuna-mcp setup --client codex
Exit status 0 means every detected client was configured and the handshake passed, 1 means configuration was saved but verification needs a manual step, and 2 means no detected client could be configured.
For a client that is not detected automatically, add this entry to its mcpServers configuration, keeping your other servers:
"ikuna": { "command": "npx", "args": ["-y", "ikuna-mcp"] }For clients such as Claude Desktop, Claude Code, and Cursor, a complete JSON configuration is:
{"mcpServers": { "ikuna": { "command": "npx", "args": ["-y", "ikuna-mcp"] } } }
For Codex, add this to ~/.codex/config.toml:
[mcp_servers.ikuna]command = "npx" args = ["-y", "ikuna-mcp"] startup_timeout_sec = 30
Restart or reconnect your MCP client after saving. Ask it to check Ikuna's health, then ask about your workspace. Your available tools depend on the capabilities enabled in Ikuna.
The first run downloads this small package from npm. Later runs use npm's cache. If your client cannot find npx, use the full executable path reported by command -v npx as command and ensure Node.js is on that client's PATH.
Requirements and troubleshooting
This package runs locally on macOS. It requires an Ikuna build that includes the MCP helper at Contents/bin/ikuna-mcp.
- Ikuna is installed but closed: open Ikuna, leave it running, and reconnect the MCP client. The npm bridge exits with an error when Ikuna is closed; it does not open the app for you.
- Ikuna is not installed: install it from the official Ikuna product page, open it, and reconnect the MCP client.
- MCP helper unavailable: update Ikuna to a build with AI Connections support.
- Discovery timeout: quit and reopen Ikuna, then retry. Running-app discovery has a short deadline and errors are written to stderr, never mixed with MCP responses.
- More than one Ikuna copy running: quit the extra copies. All copies share the local bridge service, so use one running installation at a time.
- Tools unavailable or approval required: review the capabilities in Ikuna's AI Connections settings. Installing this package does not change permissions.
Custom installation locations are discovered automatically from the running app. To select a particular running bundle explicitly:
"ikuna": {"command": "npx", "args": ["-y", "ikuna-mcp", "--app-path", "/Applications/Ikuna.app"] }
IKUNA_APP_PATH is the equivalent environment variable. A selected bundle must already be running. The optional IKUNA_MCP_CLIENT_ID environment variable is passed through to Ikuna for connection bookkeeping; it does not grant access.
How it works
MCP client → npx ikuna-mcp → Ikuna.app/Contents/bin/ikuna-mcp → local XPC bridge → IkunaThe npm package discovers the running Ikuna bundle and launches its embedded native helper with the client's stdio streams. The native helper provides the signed XPC connection, request deadlines, and per-client protocol sessions. Ikuna remains responsible for tools, workspace data, approvals, and mutations. On the way back to the client, the package repairs the tools/list schema so an optional confirmation field stays optional and strict clients do not reject valid read calls; it changes no request, workspace data, or result. The package has no runtime dependencies, reads no workspace database, and opens no network listener.
The MCP Registry manifest is included as server.json. Maintainers can follow RELEASE.md to publish the npm package and listing together.