MCP server for Nano Stores: devtools, migration helpers, logger integration
MCP server for Nano Stores: devtools, migration helpers, logger integration. That is what the nanostores mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Ask your AI: "Analyze my store architecture" or "Which stores update most frequently?"
The server publishes 14 tools. What each one is for:
nanostores_scan_project — Scan project for all stores, subscribers, and dependenciesnanostores_store_summary — Detailed summary of a specific storenanostores_project_outline — High-level overview: store kinds, top directories, hub storesnanostores_store_subgraph — BFS-expanded dependency neighborhood of a storenanostores_store_impact — Downstream causal chain — what recomputes/re-renders if X changesnanostores_runtime_overview — Overall health report with statistics for all storesnanostores_store_activity — Activity timeline for a specific store (filterable by kind/action)nanostores_find_noisy_stores — Identify stores with high change frequency or error ratesnanostores_runtime_coverage — Compare static graph with runtime events to find coverage gapsnanostores_docs_search — Search docs by query (full-text), storeKind (atom, map, computed, persistentAtom, etc.), or both. Optional: limit (default 10), tagsnanostores_ping — Server health check and logger bridge statusnanostores_clear_cache — Clear project index cache to force rescanInstallation goes through your MCP client rather than a global install: point it at nanostores-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: NANOSTORES_MCP_ROOT, NANOSTORES_MCP_LOGGER_HOST. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
| Requirement | Version | | ----------- | ----------------------- | | Node.js | ^20.0.0 \|\| >=22.0.0 | Required peer dependency (for static analysis): Optional peer dependencies — install only if you use the corresponding file format: | Package | When needed | | -------------------- | -------------------------------------- | | @vue/compiler-sfc | Vue SFC (.vue) file scanning | |
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Nanostores MCP's toolset — nanostores_scan_project, nanostores_store_summary, nanostores_project_outline and 11 more — is a fair guide to whether it matches your workflow. It is maintained by valyay; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| nanostores_scan_project | Scan project for all stores, subscribers, and dependencies |
| nanostores_store_summary | Detailed summary of a specific store |
| nanostores_project_outline | High-level overview: store kinds, top directories, hub stores |
| nanostores_store_subgraph | BFS-expanded dependency neighborhood of a store |
| nanostores_store_impact | Downstream causal chain — what recomputes/re-renders if X changes |
| nanostores_runtime_overview | Overall health report with statistics for all stores |
| nanostores_store_activity | Activity timeline for a specific store (filterable by kind/action) |
| nanostores_find_noisy_stores | Identify stores with high change frequency or error rates |
| nanostores_runtime_coverage | Compare static graph with runtime events to find coverage gaps |
| nanostores_docs_search | Search docs by query (full-text), storeKind (atom, map, computed, persistentAtom, etc.), or both. Optional: limit (default 10), tags |
| nanostores_ping | Server health check and logger bridge status |
| nanostores_clear_cache | Clear project index cache to force rescan |
| Cursor | Create .cursor/mcp.json in your project root (or ~/.cursor/mcp.json for global): |
| Windsurf | You can also open this file from the MCP icon in the Cascade panel → "Configure". |
{
"mcpServers": {
"nanostores": {
"command": "npx",
"args": ["-y", "nanostores-mcp"],
"env": {
"NANOSTORES_MCP_ROOT": "/path/to/your/project"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Requirement | Version | | ----------- | ----------------------- | | Node.js | ^20.0.0 \|\| >=22.0.0 | Required peer dependency (for static analysis): Optional peer dependencies — install only if you use the corresponding file format: | Package | When needed | | -------------------- | -------------------------------------- | | @vue/compiler-sfc | Vue SFC (.vue) file scanning | |
| Variable | Description | Required |
|---|---|---|
| NANOSTORES_MCP_ROOT | Configuration value read at startup. | Optional |
| NANOSTORES_MCP_LOGGER_HOST | Endpoint or connection string the server talks to. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.