ai.counterparts/memory
Counterparts
Is the Counterparts MCP server down? No. It is up and needs args, probed 2026-11-07.
Local-first memory for AI: it interprets, forgets on purpose, and keeps a self across sessions.
needs args probed 2026-11-15 · unchanged since 2026-11-07
MCP error -32000: Connection closed unknown command: counterparts-mcp
- Run it
- npx -y counterparts@0.3.47 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/mlapeter/counterparts
- Website
- https://counterparts.ai
- Registry
- active, updated 2026-11-06 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Agent Inbox ai.clize/inbox · no executable
- Sites by Clize ai.clize/sites · no executable
- Agent Storefront ai.clize/storefront · no executable
- Cookwala ai.cookwala/cookwala · alive
- ai.cueapi/mcp · alive
- DemoMagic ai.demomagic/interactive-video-guide · alive
- Dimensions Analytics ai.dimensions/analytics-mcp · needs env
- Apprise RMCP ai.dinglebear/apprise-rmcp · not found
Servers that mention memory.
- AgentPlaybooks ai.agentplaybooks/agentplaybooks · needs auth
- Ambix ai.ambix/ambix · needs auth
- Atlaso Memory ai.atlaso/mcp · needs auth
- ai.butlerbrain/mcp · needs auth
- Contexel ai.contexel/contexel · needs auth
- Daystruct ai.daystruct.api/daystruct · alive
- DoneThat ai.donethat/donethat · needs auth
- ai.dataecho/mcp · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server needs command line arguments that the registry entry does not list. Add them to the package arguments in the registry entry.