Skip to main content

MemClaw Team Sharing: How to Share Project Memory Across Your Team

· 2 min read
Felo Search Tips Buddy
Felo Search Tips Buddy
Operations

Complete guide to MemClaw team workspaces. How to invite members, manage permissions, share context, and eliminate knowledge silos.

MemClaw Team Sharing: Give Your Whole Team Shared AI Memory

When you use Claude Code alone, MemClaw gives you persistent memory across sessions. When your team uses Claude Code together, MemClaw gives everyone the same memory. Every developer on your team loads the same project context at session start. Architecture decisions, sprint goals, known issues — shared across the whole team automatically. Set up team sharing with MemClaw → memclaw.me

The Problem with Individual AI Memory​

Without shared memory, each developer's Claude Code session is isolated:

  • Developer A knows about the Redis connection limit — Developer B doesn't
  • Developer A logged the GraphQL rejection decision — Developer B suggests GraphQL anyway
  • New team member joins — they have no project context in their Claude sessions The result: inconsistent AI suggestions, repeated debates, slow onboarding.

How Team Sharing Works​

With a shared MemClaw workspace:

  1. One workspace ID for the whole team
  2. Each developer's .claude/mcp_config.json points to the same workspace
  3. Every session loads the same context
  4. Every /end command adds to the shared history

Setting Up Team Sharing​

1. Create a shared workspace​

One team member creates the workspace at memclaw.me and seeds it with project context:

2. Share the workspace ID​

Share the workspace ID and API key with the team (use a password manager or secrets tool — not Slack or email).

3. Each developer configures MCP​

Each developer adds to their project's .claude/mcp_config.json:

4. Everyone uses the same slash commands​

Add /start and /end to the project's .claude/commands/ so everyone uses the same workflow.

What Gets Shared​

Onboarding New Developers​

With a shared workspace, new developer onboarding is instant: No onboarding doc needed. Claude has the context.

Getting Started​

  1. Create a workspace at memclaw.me (paid plan for team sharing)
  2. Seed it with your project context
  3. Share workspace ID with the team
  4. Each developer configures MCP
  5. Add shared slash commands to the project Set up team sharing → memclaw.me