mso-pm

Free, open-source project management for software studios and teams. Kanban boards, tasks, issues, releases, clients, docs and team chat, across any number of organizations with one login, with private-by-default data.

Live app · Architecture · Contributing · Security · License: AGPL-3.0

Features

• Projects and boards: board and list views, your own statuses, priorities and labels, drag and drop (mouse, touch and keyboard), checklists, task dependencies, milestones and releases.
• Issues: severity, steps, links to tasks, sorted by what matters.
• Team chat: a General channel per organization, a channel per project, named groups and direct messages, all live.
• Notifications: corner pop-ups with a sound, and per-category email for assignments, reviews, deadlines (08:00 in each organization's time zone), comments and project changes. Reviews follow task status.
• Organizations and roles: one login, many organizations; owner, admin, project manager, developer and viewer roles, custom roles, per-project overrides, single-use email invitations.
• Clients and docs: client records with their projects; docs next to the work.
• Use it from ChatGPT, Claude and other AI apps: a built-in MCP server lets people list, create and update tasks and comment from their AI assistant, signed in with their own mso-pm account and limited to what their role allows (how to connect).
• Accounts: 6-digit email codes for sign-up and password reset, 30-day sessions, email preferences, delete account.
• Admin console for whoever runs the installation: usage numbers, users and organizations (metadata only), suspend and restore, audit log, email delivery log, and an inbox for feature requests and issue reports.
• Installable on Android, iPhone and desktop (PWA), light and dark themes, works on phones.

Connect an AI app (MCP)

mso-pm is an MCP server at https://pm.mshinan.com/api/mcp (or /api/mcp on your own copy). Add that URL in your AI app, sign in with your mso-pm account, and click Allow:

App	Where
Claude (web and desktop)	Settings → Connectors → Add custom connector
ChatGPT	Settings → Connectors, with developer mode on
Claude Code	claude mcp add --transport http mso-pm https://pm.mshinan.com/api/mcp, then /mcp to sign in
Cursor	.cursor/mcp.json: { "mcpServers": { "mso-pm": { "url": "https://pm.mshinan.com/api/mcp" } } }
VS Code	.vscode/mcp.json: { "servers": { "mso-pm": { "type": "http", "url": "https://pm.mshinan.com/api/mcp" } } }

Tools: list_organizations, list_projects, list_tasks, get_task, create_task, update_task, add_comment. Then just ask, for example "What's assigned to me in WEB?" or "Move WEB-41 to Review and comment that it's ready."

Every call runs as you, so the AI sees and changes only what you could in the app, and your teammates get the usual notifications.

How it's built

Next.js 16 (App Router, Server Components) · Supabase (Postgres, Auth, Realtime, Vault, pg_cron, pg_net, OAuth 2.1 server) · Tailwind CSS v4 · MCP (@modelcontextprotocol/server, @supabase/server) · Cloudflare R2 for files · Resend for email · Vercel for hosting.

Every table has row-level security, so the database itself decides who can read or change what: the UI only hides what you can't do. The model, schema and trade-offs are in docs/ARCHITECTURE.md, and tests/rls.test.ts checks them against a real database with real users.

Run your own copy

Everything below fits in free tiers: Supabase (database and auth), Vercel Hobby (hosting, personal and non-commercial use), Cloudflare R2 (10 GB of files, free downloads) and Resend (3,000 emails a month).

1. Database

1. Create a project at supabase.com.

2. cp .env.example .env.local and fill in the Supabase values (Project Settings → API keys and Database → connection string, session pooler).

3. Apply the schema and make yourself the platform admin:

   npm install
   npm run db:push
   node --env-file=.env.local scripts/platform-admin.mjs [email protected]
   

2. App

npm run dev    # http://localhost:3000

Sign up with the email you made admin, confirm it with the code, and create an organization. In Supabase → Authentication → URL Configuration, add your app's URLs to the redirect list (http://localhost:3000/** and your production URL).

3. Email (sign-up codes and notifications)

Supabase's built-in email only reaches members of your Supabase team, so add your own sender before inviting anyone:

1. In Resend, verify your domain and create an API key.

2. Supabase → Authentication → Emails → SMTP: host smtp.resend.com, port 465, user resend, the API key as password, and your sender address.

3. Store the same settings for notification emails (read from the environment, so the key never lands in your shell history):

   RESEND_API_KEY=re_... node --env-file=.env.local scripts/email-setup.mjs "mso-pm <[email protected]>" https://your-app.example
   

4. After deploying (step 5), switch the sign-up and reset emails to codes: node --env-file=.env.local scripts/auth-emails.mjs (needs SUPABASE_ACCESS_TOKEN).

4. Files (Cloudflare R2)

1. Create a bucket (for example mso-pm-attachments) and add a CORS rule that allows GET and PUT with header content-type from your app's origins.
2. Create an R2 API token with Object Read & Write on that bucket.
3. Put R2_ACCOUNT_ID, R2_ACCESS_KEY_ID, R2_SECRET_ACCESS_KEY and R2_BUCKET in .env.local.

Without R2, everything works except attachments, which say storage isn't set up.

以上為 README 的開頭部分。其餘內容請閱讀原文。 檢視完整 README ↗