Memory MCP Server
Persistent memory using a knowledge graph
Configurable tool bundle for AI coding agents — use via MCP server, CLI, or agent skills. npm wrapper for the Rust binary.
{
"mcpServers": {
"devboy-tools": {
"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.
Configurable tool bundle for AI coding agents — use via MCP server, CLI, or agent skills. npm wrapper for the Rust binary.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
Apache-2.0. View license →
Is it maintained?
Last commit 1 days ago. 11 stars.
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.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationNo known vulnerabilities.
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
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.
Hash-verified file editing MCP server with token efficiency hook. 11 tools for AI coding agents.
MCP Security Weekly
Get CVE alerts and security updates for Devboy Tools and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A fast, Open Source configurable tool bundle for AI coding agents, written in Rust. DevBoy ships a curated set of dev-workflow tools (GitHub, GitLab, ClickUp, Jira, and more) that can be plugged into any agent three ways: as an MCP server, as a CLI for humans and scripts, or as agent skills that call individual tools directly. Under the hood: plugin system for API providers, an LLM-optimized output pipeline, and multi-project context switching.
DevBoy is a tool bundle first — the transport is your choice:
| Mode | When to use | Example |
|---|---|---|
| MCP server | Claude Desktop, Claude Code, any MCP-compatible client | devboy mcp (stdio) |
| CLI | Humans, CI jobs, shell scripts | devboy issues, devboy mrs |
| Agent skills | Agents that don't want the full MCP tool-list tax — call just the tools a skill needs | devboy tools call get_issues from a skill script |
The same tools, the same pipeline, three ways to reach them. Start with one mode and layer on the others as your workflow grows.
Note on JSON arguments.
devboy tools call <name>takes an optional positional JSON string (defaults to{}). On POSIX shells wrap it in single quotes:devboy tools call get_issues '{"limit": 20}'. On Windowscmd.exe/ PowerShell escape the inner quotes instead:devboy tools call get_issues "{\"limit\": 20}".
| Others | DevBoy | |
|---|---|---|
| Privacy | Cloud-based credentials | Local OS keychain + env vars for CI |
| Focus | All projects at once | Context-based project isolation |
| Context | Static tool descriptions | Dynamic per-project prompts |
| Efficiency | Default API responses | LLM-optimized pipeline — ~5–20% token savings on real workloads (higher on large list/diff responses, lower on simple calls). Measured against our own production traffic and benchmarks — no cherry-picked numbers. |
| Tools | Generic aggregators | Purpose-built for dev workflows |
| **Extensibil |