An MCP server that exposes getMe key-value operations as MCP tools
Connect Runs on your machine
claude mcp add getme-mcp-server -e GETME_SOCKET_PATH=<GETME_SOCKET_PATH> -e GETME_READ_ONLY=<GETME_READ_ONLY> -e GETME_ALLOW_CLEAR=<GETME_ALLOW_CLEAR> -e GETME_KEY_PREFIX=<GETME_KEY_PREFIX> -- uvx getme-mcp-server==1.1.2{
"mcpServers": {
"getme-mcp-server": {
"command": "uvx",
"args": [
"getme-mcp-server==1.1.2"
],
"env": {
"GETME_SOCKET_PATH": "<GETME_SOCKET_PATH>",
"GETME_READ_ONLY": "<GETME_READ_ONLY>",
"GETME_ALLOW_CLEAR": "<GETME_ALLOW_CLEAR>",
"GETME_KEY_PREFIX": "<GETME_KEY_PREFIX>"
}
}
}
}{
"mcpServers": {
"getme-mcp-server": {
"command": "uvx",
"args": [
"getme-mcp-server==1.1.2"
],
"env": {
"GETME_SOCKET_PATH": "<GETME_SOCKET_PATH>",
"GETME_READ_ONLY": "<GETME_READ_ONLY>",
"GETME_ALLOW_CLEAR": "<GETME_ALLOW_CLEAR>",
"GETME_KEY_PREFIX": "<GETME_KEY_PREFIX>"
}
}
}
}{
"servers": {
"getme-mcp-server": {
"type": "stdio",
"command": "uvx",
"args": [
"getme-mcp-server==1.1.2"
],
"env": {
"GETME_SOCKET_PATH": "<GETME_SOCKET_PATH>",
"GETME_READ_ONLY": "<GETME_READ_ONLY>",
"GETME_ALLOW_CLEAR": "<GETME_ALLOW_CLEAR>",
"GETME_KEY_PREFIX": "<GETME_KEY_PREFIX>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
GETME_SOCKET_PATHOptional | Path to the UNIX socket for getMe core server |
GETME_READ_ONLYOptional | If true, only get and get_json tools are registered |
GETME_ALLOW_CLEAROptional | If true, enables the dangerous clear tool |
GETME_KEY_PREFIXOptional | String prefix prepended to all keys (e.g. agent1:) |
Details
| Package | [email protected] (PYPI, stdio) |
| First published | 10 Jun 2026 |
| Last updated | 10 Jun 2026 |
| Registry name | io.github.AatirNadim/getme-mcp-server |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.