Organizations & Teams

mem/ctl is organized around organizations and projects. Organizations own projects, manage billing, and share context across projects.

Structure

Organization
├── Members (owner, admin, member)
├── Projects
│   ├── Memories
│   ├── Context entries
│   ├── Session logs
│   └── Activity logs
├── Org defaults
├── Project templates
└── Billing (Stripe plan)

Roles

Role	Permissions
owner	Full access. Manage billing, members, all projects.
admin	Manage members and all projects. Cannot change billing.
member	Access only assigned projects.

Owners and admins can access all projects. Members must be explicitly assigned to projects.

Projects

Projects live inside organizations. Each project has its own:

Memory store (isolated from other projects)
Context entries
Session logs and activity logs
Capacity limits (based on the org's plan)

Project slugs are unique within an organization.

curl -X POST https://memctl.com/api/v1/projects \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -H "X-Org-Slug: my-team" \
  -d '{"name": "Backend API", "slug": "backend-api"}'

Plan limits

Limits are defined in packages/shared/src/constants.ts.

Plan	Price	Projects	Members (included)	Extra seat	Memory/Project	Rate/min
Free	$0	3	1	N/A	400	60
Lite	$5/mo	10	3	+$8/mo	1,200	100
Pro	$18/mo	25	10	+$8/mo	5,000	150
Business	$59/mo	100	30	+$8/mo	10,000	150
Scale	$149/mo	150	100	+$8/mo	25,000	150
Enterprise	Custom	Unlimited	Unlimited	Included	Unlimited	150

All plans have unlimited API calls per month. Rate limits are per-minute per-user sliding window.

Self-hosted deployments (SELF_HOSTED=true) bypass all plan limits.

Org defaults

Org defaults are memory entries that can be applied to any project in the org. Useful for org-wide coding standards, architecture decisions, and constraints.

Setting defaults

{
  "tool": "org",
  "action": "defaults_set",
  "key": "agent/context/coding_style/org-standard",
  "content": "All projects:\n- TypeScript strict mode\n- ESLint + Prettier\n- No default exports",
  "priority": 80,
  "tags": ["coding_style"]
}

Applying defaults to a project

{
  "tool": "org",
  "action": "defaults_apply"
}

This copies all org defaults into the current project. Existing keys are updated, new keys are created.

Listing defaults

{
  "tool": "org",
  "action": "defaults_list"
}

Project templates

Templates are reusable sets of memory entries for bootstrapping new projects.

Creating a template

{
  "tool": "org",
  "action": "template_create",
  "name": "React Starter",
  "description": "Standard context for React projects",
  "data": [
    {
      "key": "agent/context/coding_style/react",
      "content": "- Functional components only\n- Use hooks for state",
      "priority": 80,
      "tags": ["react", "coding_style"]
    },
    {
      "key": "agent/context/testing/react",
      "content": "- Use React Testing Library\n- Test behavior, not implementation",
      "priority": 70,
      "tags": ["react", "testing"]
    }
  ]
}

Applying a template

{
  "tool": "org",
  "action": "template_apply",
  "templateId": "template-id"
}

Listing templates

{
  "tool": "org",
  "action": "template_list"
}

Returns both built-in and custom templates.

Cross-project search

Search across all projects in the org:

{
  "tool": "context",
  "action": "search_org",
  "query": "authentication patterns",
  "limit": 50
}

Results are grouped by project. Useful for finding how different projects solve similar problems.

Context diff

Compare agent context between two projects:

{
  "tool": "org",
  "action": "context_diff",
  "projectA": "backend-api",
  "projectB": "frontend-app"
}

Returns:

Keys unique to project A
Keys unique to project B
Shared keys (with whether content matches or differs)
Statistics (totals, overlaps)

Useful for standardization or for understanding how context diverges across projects.

Member management

Inviting members

Via the dashboard or API:

curl -X POST https://memctl.com/api/v1/orgs/my-team/members \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"email": "[email protected]", "role": "member"}'

Project assignment

Members (non-admin) only see projects they are assigned to. Owners and admins see all projects.

Project assignment is managed through the dashboard or the member projects endpoint:

GET /orgs/{slug}/members/{memberId}/projects

Organizations & Teams

mem/ctl is organized around organizations and projects. Organizations own projects, manage billing, and share context across projects.

Structure

Organization
├── Members (owner, admin, member)
├── Projects
│   ├── Memories
│   ├── Context entries
│   ├── Session logs
│   └── Activity logs
├── Org defaults
├── Project templates
└── Billing (Stripe plan)

Roles

Role	Permissions
owner	Full access. Manage billing, members, all projects.
admin	Manage members and all projects. Cannot change billing.
member	Access only assigned projects.

Owners and admins can access all projects. Members must be explicitly assigned to projects.

Projects

Projects live inside organizations. Each project has its own:

Memory store (isolated from other projects)
Context entries
Session logs and activity logs
Capacity limits (based on the org's plan)

Project slugs are unique within an organization.

curl -X POST https://memctl.com/api/v1/projects \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -H "X-Org-Slug: my-team" \
  -d '{"name": "Backend API", "slug": "backend-api"}'

Plan limits

Limits are defined in packages/shared/src/constants.ts.

Plan	Price	Projects	Members (included)	Extra seat	Memory/Project	Rate/min
Free	$0	3	1	N/A	400	60
Lite	$5/mo	10	3	+$8/mo	1,200	100
Pro	$18/mo	25	10	+$8/mo	5,000	150
Business	$59/mo	100	30	+$8/mo	10,000	150
Scale	$149/mo	150	100	+$8/mo	25,000	150
Enterprise	Custom	Unlimited	Unlimited	Included	Unlimited	150

All plans have unlimited API calls per month. Rate limits are per-minute per-user sliding window.

Self-hosted deployments (SELF_HOSTED=true) bypass all plan limits.

Org defaults

Org defaults are memory entries that can be applied to any project in the org. Useful for org-wide coding standards, architecture decisions, and constraints.

Setting defaults

{
  "tool": "org",
  "action": "defaults_set",
  "key": "agent/context/coding_style/org-standard",
  "content": "All projects:\n- TypeScript strict mode\n- ESLint + Prettier\n- No default exports",
  "priority": 80,
  "tags": ["coding_style"]
}

Applying defaults to a project

{
  "tool": "org",
  "action": "defaults_apply"
}

This copies all org defaults into the current project. Existing keys are updated, new keys are created.

Listing defaults

{
  "tool": "org",
  "action": "defaults_list"
}

Project templates

Templates are reusable sets of memory entries for bootstrapping new projects.

Creating a template

{
  "tool": "org",
  "action": "template_create",
  "name": "React Starter",
  "description": "Standard context for React projects",
  "data": [
    {
      "key": "agent/context/coding_style/react",
      "content": "- Functional components only\n- Use hooks for state",
      "priority": 80,
      "tags": ["react", "coding_style"]
    },
    {
      "key": "agent/context/testing/react",
      "content": "- Use React Testing Library\n- Test behavior, not implementation",
      "priority": 70,
      "tags": ["react", "testing"]
    }
  ]
}

Applying a template

{
  "tool": "org",
  "action": "template_apply",
  "templateId": "template-id"
}

Listing templates

{
  "tool": "org",
  "action": "template_list"
}

Returns both built-in and custom templates.

Cross-project search

Search across all projects in the org:

{
  "tool": "context",
  "action": "search_org",
  "query": "authentication patterns",
  "limit": 50
}

Results are grouped by project. Useful for finding how different projects solve similar problems.

Context diff

Compare agent context between two projects:

{
  "tool": "org",
  "action": "context_diff",
  "projectA": "backend-api",
  "projectB": "frontend-app"
}

Returns:

Keys unique to project A
Keys unique to project B
Shared keys (with whether content matches or differs)
Statistics (totals, overlaps)

Useful for standardization or for understanding how context diverges across projects.

Member management

Inviting members

Via the dashboard or API:

curl -X POST https://memctl.com/api/v1/orgs/my-team/members \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"email": "[email protected]", "role": "member"}'

Project assignment

Members (non-admin) only see projects they are assigned to. Owners and admins see all projects.

Project assignment is managed through the dashboard or the member projects endpoint:

GET /orgs/{slug}/members/{memberId}/projects

Organizations & Teams

Organizations & Teams

Structure

Roles

Projects

Plan limits

Org defaults

Setting defaults

Applying defaults to a project

Listing defaults

Project templates

Creating a template

Applying a template

Listing templates

Cross-project search

Context diff

Member management

Inviting members

Project assignment

On this page

Organizations & Teams

Organizations & Teams

Structure

Roles

Projects

Plan limits

Org defaults

Setting defaults

Applying defaults to a project

Listing defaults

Project templates

Creating a template

Applying a template

Listing templates

Cross-project search

Context diff

Member management

Inviting members

Project assignment

On this page