Team Memory Sync ? LLM-ready install instructions Site: https://teams-memory.avmsistemas.net Contact: teams.memory@avmsistemas.net OVERVIEW Team Memory Sync adds collective organisation memory to MCP-capable AI assistants (Cursor, Claude Code, Antigravity, Windsurf, etc.). Local personal learning stays on the developer machine via the open-source my-local-storage-mcp core. Team facts sync through the @avm/my-local-storage-mcp-teams plugin and the Team Memory SaaS API. PREREQUISITES 1. An MCP-capable IDE or assistant already installed and licensed. 2. Node.js 20+ for MCP server packages. 3. Organisation MCP access key from the Team Memory console (after onboarding). 4. Public console (when open): https://teams-memory.avmsistemas.net INSTALL PACKAGES npm install -g my-local-storage-mcp npm install -g @avm/my-local-storage-mcp-teams MCP CONFIGURATION (example mcp.json / Cursor MCP settings) { "mcpServers": { "local-storage": { "command": "npx", "args": ["-y", "my-local-storage-mcp"], "env": { "MCP_PLUGINS": "teams", "MCP_TEAMS_ACCESS_KEY": "", "MCP_TEAMS_API_URL": "https://teams-memory.avmsistemas.net/api/v1", "MCP_TEAMS_SYNC_INTERVAL_MS": "120000", "MCP_TEAMS_PUSH_ON_REMEMBER": "1", "MCP_TEAMS_TOPICS": "*" } } } } ENVIRONMENT VARIABLES MCP_PLUGINS=teams Enable team sync plugin MCP_TEAMS_ACCESS_KEY Required. Secret org key from console MCP_TEAMS_API_URL Default: https://teams-memory.avmsistemas.net/api/v1 MCP_TEAMS_SYNC_INTERVAL_MS Background sync interval (default 120000) MCP_TEAMS_PUSH_ON_REMEMBER Push after remember_fact (default 1) MCP_TEAMS_TOPICS CSV of allowed topics or * for all MCP_TEAMS_ENRICH_RECALL Attach team block on local recall (0/1) MCP_TEAMS_SYNC_ANCHORS_ONLY Sync anchor records only (default 1) MCP TOOLS (plugin active) team_sync_status ? connection and last sync state team_sync_now ? manual push/pull recall_team_facts ? fetch team facts by topic/keywords WEB CONSOLE - Dashboard shows topic and keyword clouds (metadata only; fact bodies stay in MCP). - Facts list exposes topics and keywords, not full fact text (privacy by design). - Team admin: licence assignment, 2FA policy, MCP key distribution. ONBOARDING FLOW 1. Organisation admin receives MCP access key and onboarding email. 2. Each member adds env vars to MCP config and restarts the MCP server. 3. Store knowledge with remember_fact; team anchors sync automatically. 4. Use recall_team_facts or enriched recall for shared context. BUSINESS / EARLY ACCESS Public self-service may be closed during rollout. Contact teams.memory@avmsistemas.net for business enquiries and early access. PRIVACY Fact content is intended for MCP clients, not the public web UI. The console indexes topics and keywords to help teams improve context coverage without exposing sacred fact bodies in the browser.