GitHub Actions Workflows
This directory contains CI/CD workflows for the @daichi-kudo/mcp-memory-sqlite package.
📁 Files
workflows/ci.yml- Continuous Integration workflow
Alimenter votre agent
Installation de l'éditeur. Ce n'est pas un endpoint PlugMCP.
Host a copy with our keys and logs.
Pas encore de version packagée dans le registre. Suivez le README du dépôt.
URL distante ou commande sur votre machine ? Ce qui distingue les deux installations
Exécuter sur PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LancerDe l'éditeur
This directory contains CI/CD workflows for the @daichi-kudo/mcp-memory-sqlite package.
workflows/ci.yml - Continuous Integration workflowSQLite-based MCP memory server with WAL mode for concurrent access. Drop-in replacement for @modelcontextprotocol/server-memory
workflows/release.yml - Release and npm publishing workflowSETUP.md - Detailed setup instructionsPIPELINE_DIAGRAM.md - Visual pipeline diagramsSETUP_COMMANDS.bat
bash SETUP_COMMANDS.sh
This will:
If you prefer to set up manually, follow these steps:
npm install -D \
@typescript-eslint/eslint-plugin \
@typescript-eslint/parser \
eslint \
rimraf
Add these scripts to package.json:
{
"scripts": {
"typecheck": "tsc --noEmit",
"lint": "eslint src --ext .ts && tsc --noEmit",
"test": "echo \"No tests yet\" && exit 0",
"test:ci": "npm run typecheck && npm run lint && npm run test",
"clean": "rimraf dist",
"prepublishOnly": "npm run clean && npm run build"
}
}
NPM_TOKENnpm run typecheck # Should pass ✓
npm run lint # Should pass ✓
npm run build # Should create dist/ ✓
npm test # Should pass ✓
git add .
git commit -m "ci: add GitHub Actions workflows"
git push origin master
Triggers:
main or developmain or developJobs:
Duration: ~2-3 minutes
Triggers:
v* patternSteps:
Duration: ~3-5 minutes
git tag v1.0.0
git push origin v1.0.0
## What's New
- Initial release
- SQLite-based MCP memory server
- WAL mode for concurrency
## Installation
npm install @daichi-kudo/mcp-memory-sqlite
The workflow will automatically publish to npm! 🎉
After release, verify at:
npm run typecheck # See errors locally
# Fix errors
npm run typecheck # Verify fixed
npm run lint # See lint errors
npm run lint -- --fix # Auto-fix
The build-check job fails if committed dist/ doesn't match the build output.
Fix:
npm run clean
npm run build
git add dist/
git commit -m "chore: update build artifacts"
git push
Common causes:
@daichi-kudo scopeSolutions:
The native module should rebuild automatically. If it fails:
The CI workflow tests on 6 combinations:
This ensures the package works across all supported platforms.
The release workflow uses npm provenance, which:
If you encounter issues:
Happy CI/CD! 🚀
SQLite-based MCP memory server with WAL mode for concurrent access. Drop-in replacement for @modelcontextprotocol/server-memory
Outils
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Copiez sur cette page la configuration stdio pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
Aucune variable d'environnement requise n'est indiquée sur cette fiche.
MCP Memory Sqlite s'exécute en local via stdio.
Dernière vérification : 2026-10-28. SQLite-based MCP memory server with WAL mode for concurrent access. Drop-in replacement for @modelcontextprotocol/server-memory