Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Read app-store keyword observations and prepare reviewable listing drafts. AI actions use tokens.
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.
APPDRIFT_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
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": {
"appdrift": {
"command": "npx",
"args": [
"-y",
"appdrift-mcp"
],
"env": {
"APPDRIFT_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add appdrift --env APPDRIFT_API_KEY=your-value -- npx -y appdrift-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"appdrift": {
"command": "npx",
"args": [
"-y",
"appdrift-mcp"
],
"env": {
"APPDRIFT_API_KEY": "your-value"
}
}
}
}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": {
"appdrift": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"appdrift-mcp"
],
"env": {
"APPDRIFT_API_KEY": "your-value"
}
}
}
}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.
Runs on your computer; the tool list appears in your AI app after you install it.
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 with the GitHub account blaze-apps, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
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.
You need to fill in: APPDRIFT_API_KEY
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).
The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 36 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush
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.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
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.
Read your AppDrift keyword observations, account apps and action plan from Claude Desktop, Cursor or another MCP client. Generate or translate listing copy, review the result, and apply accepted fields to an editable AppDrift draft. These tools do not publish to Apple or Google.
This package is a small local stdio client for the AppDrift REST API. It requires Node.js 22 or later and an AppDrift API key. API access is available on eligible paid plans. Eligible first subscriptions have a seven-day trial with a card; the trial adds no tokens. Current plans and token allowances.
Add AppDrift to your MCP client's configuration (Claude Desktop, Cursor or another MCP client):
{
"mcpServers": { "appdrift": { "command": "npx", "args": ["-y", "appdrift-mcp"], "env": { "APPDRIFT_API_KEY": "ad_live_your_key_here" } } } }
account_status, then list_apps. These calls consume no AI tokens.On the first run, npx downloads the package and its dependencies. If the client cannot find npx, use its absolute local executable path.
Without the npm registry: AppDrift also hosts the same wrapper as a versioned archive. Use https://appdrift.co/downloads/appdrift-mcp-0.2.0.tgz in args in place of appdrift-mcp, and check it against its SHA-256 checksum. The archive includes the complete wrapper source and MIT license. server.json prepares the official MCP registry entry, which is not published yet.
No additional AI tokens: API access still requires an eligible account plan.
| Tool | Result |
|---|---|
keyword_difficulty | Legacy competitor-based difficulty/popularity heuristics. These are not measured keyword demand or ranking probability. Store collection can fail or be incomplete. |
list_apps | Apps connected to the account, including the ID used by app-scoped tools. |
app_keywords | Tracked keywords and latest observed ranks for the selected app. |
app_opportunities | Tracked keywords ranked 11–30, ordered by the legacy difficulty heuristic; candidates to review, not predicted gains. |
action_plan | The account's prioritized ASO actions. |
account_status | Plan and remaining AI-token balance. |
apply_optimization | Changes saved content: applies accepted title, subtitle, keywords or short_description fields to the app's editable draft. Review and store publishing remain separate. |
AI tools: AppDrift charges for successful processing. Check the returned token charge and account balance. The client never retries these actions automatically.
| Tool | Cost | Result |
|---|---|---|
optimize_for_keyword | 3 tokens | Proposed title/subtitle/keyword changes and rationale. |
generate_metadata | 1 per short field; 2 per long field | Listing fields generated from the app brief. |
translate_metadata | Per language: 1 normally; 3 for description; 5 for full_description | One field translated into 1–15 distinct locales. |
Paid operations and apply_optimization are advertised as writes to MCP clients. A timeout or lost response does not prove that the server stopped processing or charged nothing. Check the account and draft before retrying. The client sends your API key and supplied listing text to the configured AppDrift API; AI requests may use the account's configured AI provider.
The legacy keyword_difficulty tool is separate from the experimental Keyword analyzer. Its scores do not predict rank, traffic or download gains.
| Environment variable | Required | Default |
|---|---|---|
APPDRIFT_API_KEY | Yes | Create it in the Developers dashboard. |
APPDRIFT_API_BASE | No | AppDrift production API. Change only to an endpoint you trust with the key and listing text. HTTPS required; HTTP permitted only for loopback development. |
APPDRIFT_REQUEST_TIMEOUT_MS | No | 90000; permitted range 1000–120000. |
The client rejects redirects, bounds response size, validates tool inputs before requests and returns authored error messages instead of provider errors or stack traces. These safeguards do not replace backend authorization or review of an agent's proposed actions.
npx availability and a nonempty APPDRIFT_API_KEY. MCP protocol messages use stdout; startup errors use stderr.account_status and current token options. A trial itself adds no tokens.Within a source checkout, run npm ci, npm test and npm run verify:package. Integration checks launch the actual stdio process against local fixture APIs; they do not use production credentials or spend tokens. Package verification packs only the declared runtime files, installs the archive through a local HTTP URL into a clean directory and runs the integration suite against the installed executable.
MIT. See LICENSE.