mcpbeat Sign in

MemQ Team Sync MCP Server

by multinex Your server? Claim it
answering

MemQ Team Sync is answering right now. Last checked 5 min ago.

Shared project memory that keeps teammates and AI agents aligned across sessions.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 51 days of history · worst day 90%
51 days agonow
95.6%
Uptime 24h
87 of 91 checks
—
Tools
hidden behind auth
1150 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

MemQ Team Sync does not always answer

Over the last week it answered 94.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add memq --transport http https://mcp.multinex.ai/mcp/v1
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "memq": {
      "url": "https://mcp.multinex.ai/mcp/v1"
    }
  }
}
~/.codex/config.toml
[mcp_servers.memq]
url = "https://mcp.multinex.ai/mcp/v1"
.cursor/mcp.json
{
  "mcpServers": {
    "memq": {
      "url": "https://mcp.multinex.ai/mcp/v1"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "memq": {
      "url": "https://mcp.multinex.ai/mcp/v1"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.multinex.ai/mcp/v1 streamable-http sign-in 958 ms 5 min ago

Alternatives to MemQ Team Sync

same job, measured the same way
XMemo
by yonro

Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.

58 installs/wk answering
Engrm
by dr12hes

Shared memory across devices, sessions, and agents for OpenClaw, Claude Code, and Codex.

27 installs/wk local only
Central Intelligence
by alekseimarchenko

Persistent memory for AI agents. Store, recall, and share knowledge across sessions.

32 installs/wk local only
I
logbook-mcp
by abduljabbarbxr

Project memory across sessions for AI agents. A queryable decision log in the repo.

599 installs/wk local only
Goldhold
by jerrysrodz

Persistent memory for AI agents. Search, store, and recall across sessions.

25 installs/wk answering
Agent Memory OS
by yamantaka520

Local-first memory engine for AI-agent teams: team/project ACL, recall, and federated sync.

522 installs/wk local only
MCP Memento
by annibale-x

An MCP server that provides persistent memory and context management across sessions

197 installs/wk local only
Memoize — persistent agent memory
by harrisonford

Persistent cross-session memory shared by Codex, Claude Code, ChatGPT, and other AI agents.

answering

MemQ Team Sync — questions

Answers built from our own checks of this server.

Why is there no tool list for MemQ Team Sync?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 95.6% of checks in the last 24 hours got a reply.
Is MemQ Team Sync working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 87 of 91 checks got a reply (95.6%), average response time 1150 ms. The bar chart above shows every period we have measured.
Is MemQ Team Sync still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect MemQ Team Sync?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to MemQ Team Sync?
No API key is involved. MemQ Team Sync answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is MemQ Team Sync?
It answers our handshake in 1150 ms on average, which is faster than 8% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.