MemQ Team Sync

ai.multinexPublished by multinex.aiOfficial publisherv2.8.1Updated Oct 27, 2026

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

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

MemQ Team Sync gives an assistant shared project memory so teammates and AI agents stay aligned across sessions.

What you can do
No tools are listed for this server. Per its description, it provides shared project memory that keeps teammates and AI agents aligned across sessions, so context from earlier work can carry over instead of being rebuilt each time. It is offered as a hosted remote endpoint and as a local container image over stdio.
When to use it
Consider it when several people and their AI assistants work on the same project and need a common memory that persists between sessions, rather than each assistant starting from scratch.
Requirements
A MemQ account with OAuth sign-in, or a MemQ API key supplied through the MEMQ_API_KEY environment variable for the local container. The remote endpoint is reached over streamable HTTP; the local option runs the published container image over stdio.
Before you install
The server requires authentication and, for local use, an API key from the Multinex billing dashboard, so it is tied to a paid Multinex account. Shared memory means project context is stored with a third-party service and visible to others on the team; avoid putting secrets or sensitive material into it.

Installation

In SourceWeft

  1. Open MemQ Team Sync in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.multinex%2Fmemq/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "memq-team-sync": {
      "type": "http",
      "url": "https://mcp.multinex.ai/mcp/v1"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2.8.1LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.