Other · Remote MCP server
MemQ Team Sync
Shared project memory that keeps teammates and AI agents aligned across sessions.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.multinex/memq- Version
- 2.8.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-09-07
- Updated
- 2026-09-07
- Publisher
- ai.multinex
- Namespace
- Namespace verified by the MCP Registry via the domain multinex.ai · how
- Repository
- github.com/multinex-ai/memq (folder mcp-server)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.multinex.ai/mcp/v1 | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | ghcr.io/multinex-ai/memq-mcp-server:registry-2.8.1 | - | stdio |
How to connect MemQ Team Sync
MemQ Team Sync is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.multinex.ai/mcp/v1, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/multinex-ai/memq-mcp-server:registry-2.8.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e MEMQ_API_KEY ghcr.io/multinex-ai/memq-mcp-server:registry-2.8.1. It reads the environment variable MEMQ_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"memq": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"MEMQ_API_KEY",
"ghcr.io/multinex-ai/memq-mcp-server:registry-2.8.1"
],
"env": {
"MEMQ_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| MemoTrader MCP ServerAI-to-human attention marketplace. Agents pay CPM to reach humans, earn credits by replying. | Local · stdio |
| MemoweftPortable AI memory as MCP tools: five reads and three controlled writes. | Local · stdio |
| MemPersistDurable, revision-pinned memory storage and retrieval for AI conversations. | Remote · HTTPLive check: sign-in required |
| MemphoraAdd persistent memory to AI assistants. Store and recall info across conversations. | Local · stdio |
| MemraPersistent memory for AI agents. EU-hosted, privacy-first, hybrid recall, contradiction detection. | Remote · HTTPLive check: ✓ handshake |
| MemtetherCross-client AI memory hub: agents share one SQLite memory.db via file-level pointers. | Local · stdio |
| MemtrustIndependent, reproducible benchmark harness for agent-memory backends. | Local · stdio |
| MemxusPersistent memory layer that saves and recalls your project context and preferences. | Remote · HTTPLive check: ✓ handshake |