GitHub Actions Workflows
This directory contains CI/CD workflows for the @daichi-kudo/mcp-memory-sqlite package.
📁 Files
workflows/ci.yml- Continuous Integration workflow
Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no 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.
AbrirDo publicador
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
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
MCP Memory Sqlite roda localmente via stdio.
Última verificação: 2026-10-28. SQLite-based MCP memory server with WAL mode for concurrent access. Drop-in replacement for @modelcontextprotocol/server-memory