Team memory

MemIndex hosting lets a team save and read memory in shared projects. Access depends on both the person's role and the key they use.

The buyer makes the first owner key in the account, after signing in, and finds the project id there. Keys are never emailed. This page explains roles and permissions.

Roles

Role	What it can do with suitable key permissions
Read-only	Read, search, export memory, and read usage.
Member	Also save memory and delete individual notes.
Admin	Also clear a project's memory and manage members and keys.
Owner	Has the admin permissions and can offer ownership to an admin.

A key can allow less than its holder's role. A read-only key stays read-only even when its holder is an owner. Keys can also be limited to a project.

Managing the team's members and listing or revoking keys requires a team-wide key. An admin cannot grant a higher role than their own. The server keeps at least one owner.

Invite someone

An owner or admin invites people from the People page of the account, with an email address and a role. The invitation lasts seven days.

The invitation email has no link that lets anyone in. It says who invited you, as what, and where to sign in. To accept:

1. Go to your MemIndex account and sign in with the address the invitation was sent to. We email that address a one-time sign-in link. If your team uses its company login, you can sign in with that instead.
2. Your invitation is waiting there. Choose Join this team.

Only the invited address can accept. Forwarding the email, or knowing the invitation, lets no one else join. If every seat on the team is taken, you are told so and the invitation waits until a seat is added.

Joining shows no key. Members make their own key on the same page, once, or connect Claude Code and other apps by signing in from the app. Someone who joins as an admin goes straight on to the account page.

Making someone an owner

Nobody becomes an owner from someone else's account. An owner offers ownership to an admin, and the admin accepts it from their own sign-in, on the People page. An invitation as owner works the same way: the person joins as an admin, with an offer to become an owner that they accept themselves.

With the API

Scripts can manage the team with a team-wide key:

Action	Request
List members	GET /v1/members
Create an invitation	POST /v1/members/invites
Change a role	PATCH /v1/members/:userId
Remove a member	DELETE /v1/members/:userId
List keys	GET /v1/keys
Revoke a key	DELETE /v1/keys/:id

Creating an invitation takes an email and a role, and optionally expiresInDays (one to thirty). The API calls the read-only role viewer. It returns the invitation and signInAt, the address where the person signs in to accept, and it emails the person the same invitation the People page sends. It returns no token: invitations are accepted only by signing in with the invited address. POST /v1/invites/accept no longer accepts anything.

Asking for the role owner makes no one an owner. It offers ownership to that admin, emails them, and answers 202 with "offered": true; they become an owner when they accept. The person must already be an admin, and the owner whose key asks must have saved recovery codes. Every other role change works as before.

Connect the team's tools

Give each machine its own key. Give search-only clients read permission. Use a project-limited key where a client needs only one project.

Connecting an MCP client gives it search tools. Saving its conversations needs a supported capture integration. See the agent pages.

Change or remove access

Role changes apply on the next request. Removing a member revokes their keys. Revoking one machine's key leaves other valid keys usable.

Anyone allowed to read memory can export the memory their key can access. Choose roles and project limits with that in mind.

Pricing and availability

You can run the server yourself without a MemIndex hosting subscription. You provide the machine, model access, and backups.

Managed hosting for a team is the Team plan on the pricing page:

Price	$40 per seat each month
Seats	Two at least. Add or remove seats as your team changes, and the bill follows.
Trial	30 days
Notes	10,000 notes per seat each month, pooled across the team, starting again each month on your billing day. Past the pool, extra notes are billed at what they cost us, with no markup, up to a monthly cap (it starts at $50 and an owner can change it). At the cap notes pause and we email you.

Each seat is one person. An invitation beyond the seats you have is refused until you add a seat.

Team checkout is not open yet. To start a Team trial, write to [email protected]. Individual plans (Lite, Plus and Power) are described in hosting and plans.