Debug and analyze Nanostores apps with AI: scan stores, monitor runtime events, and search docs.
{
"mcpServers": {
"io-github-valyay-nanostores-mcp": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Debug and analyze Nanostores apps with AI: scan stores, monitor runtime events, and search docs.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Commit history unknown.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
MCP Security Weekly
Get CVE alerts and security updates for io.github.Valyay/nanostores-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Model Context Protocol server for Nanostores — analyze, debug and monitor your nanostores in AI assistants like Claude Desktop.
@nanostores/logger, performance metrics, activity trackingnpx nanostores-mcp
Ask your AI: "Analyze my store architecture" or "Which stores update most frequently?"
Made at Evil Martians, product consulting for developer tools.
Understand your nanostores architecture without running your app:
.subscribe() / .listen() calls and component bindings across React, Vue, Svelte, and Angular<script> and <script setup> blocks in .vue files (requires @vue/compiler-sfc)<script context="module"> and instance <script> blocks, auto-subscriptions ($storeName in templates), and filters out Svelte 5 runes ($state, $derived, $effect, etc.) so they are not mistaken for store references (requires svelte)@nanostores/angular NanostoresService constructor injections and detects this.nanostores.useStore(...) call patterns in TypeScript component filesReal-time insights into your running application:
@nanostores/loggerSearch and browse Nanostores documentation directly from your AI assistant:
nanostores in your node_modules automatically| Requirement | Version |
|---|---|
| Node.js | `^2 |