Neemee MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 241 installs a week from npm. Last commit 18 Mar 2026.
MCP client library and bridge for Neemee personal knowledge management system
The author archived this repository on GitHub, meaning it is no longer maintained.
We read the source, 21 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
пакет neemee-mcp ссылается на paul-bonneville-labs/neemee-app
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add neemee-mcp -e 'NEEMEE_API_KEY=<NEEMEE_API_KEY>' -- npx -y neemee-mcp
{
"mcpServers": {
"neemee-mcp": {
"command": "npx",
"args": [
"-y",
"neemee-mcp"
],
"env": {
"NEEMEE_API_KEY": "<NEEMEE_API_KEY>"
}
}
}
}
[mcp_servers.neemee-mcp]
command = "npx"
args = ["-y", "neemee-mcp"]
env = { NEEMEE_API_KEY = "<NEEMEE_API_KEY>" }
{
"mcpServers": {
"neemee-mcp": {
"command": "npx",
"args": [
"-y",
"neemee-mcp"
],
"env": {
"NEEMEE_API_KEY": "<NEEMEE_API_KEY>"
}
}
}
}
{
"servers": {
"neemee-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"neemee-mcp"
],
"env": {
"NEEMEE_API_KEY": "<NEEMEE_API_KEY>"
}
}
}
}
Put your own value in place of
<NEEMEE_API_KEY> (API key for authenticating with Neemee API (required)).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
NEEMEE_API_BASE_URL (Base URL for Neemee MCP server (optional, defaults to https://neemee.app/mcp)).
Persistent memory, knowledge graph, task management and more for AI agents via MCP.
Personal knowledge graph every MCP client reads from and writes to. Portable across agents.
MCP server for Pickaxe API - manage AI agents, knowledge bases, users, and analytics
Persistent knowledge system with OWL-RL reasoning and 22 MCP tools. Local-first.
Ingeniux CTnP MCP server for personalization, A/B testing, and audience management.
Search, browse and manage your DesignVault design-asset library from any MCP client.
Your personal knowledge base and memory for AI agents: search, explore and feed your myBrain.
AI knowledge graph for architecture, portfolio, and digital strategy management.
Answers built from our own checks of this server.