TeamOnly

dev.teamonlyPublished by teamonly.devv0.9.0Updated Oct 29, 2026

Deploy AI-built internal apps behind your company login, with a database, files and secrets.

VerifiedSTDIODesktop onlyDatabases Cloud & Infrastructure Developer Tools

Server details

Identifier: dev.teamonly/teamonly
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Oct 26, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to teamonly.dev. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/dev.teamonly%2Fteamonly.svg)](https://sourceweft.com/mcp/dev.teamonly%2Fteamonly?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Deploys AI-built internal apps behind a company login, with a database, file storage, secrets and version rollback, from an MCP client.

What you can do: Read app rules and scaffold a new app or add TeamOnly to an existing one
Build and deploy the app behind the company login, list versions and roll back
Pull a deployed app's code down and check account, plan and app access
Inspect live request logs, console output and errors for a short window
Manage who can open the app, in-app roles, and app secrets
Sign in by emailed code, start a trial, get a payment link, delete an app
When to use it: Useful when you build small internal tools with an AI assistant and want them hosted for colleagues only, rather than running them locally or wiring up your own hosting, database and auth. Also handy for redeploying, rolling back or debugging an app already on TeamOnly.
Requirements: Runs locally as an npm package (teamonly) over stdio, so Node.js 20 or newer is needed (22 for the logs tool). Desktop MCP client only. No API keys: sign-in uses a work email plus a 6-digit code sent by email, and the session is stored in the user's home directory. A TeamOnly company account is required; new companies can start a 14-day trial.

Before you install

Deploying reads the project's files and publishes the app online, and delete_app removes the app and its data. set_secret stores API keys and passwords for the app. subscribe returns a payment link, so a paid plan can be purchased. Sign-in codes and the saved session in the home directory are credentials; the app can also read and add rows in Google Sheets shared with it.

Installation

In SourceWeft

Open TeamOnly in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

TeamOnly MCP server

Deploy the internal apps you build with AI behind your company login, from Claude Code, Cursor, Claude Desktop, VS Code, Windsurf or any MCP client.

Say "deploy this on TeamOnly" and your agent puts the app online at https://<app>.<company>.teamonly.app. Only people with an email at your company can open it: they sign in with their work Google or Microsoft account, or a code sent to their work email. The app gets its own database, file storage and secrets, and can read and add rows in Google Sheets your team shares with it. Free for 14 days, no card.

Website: teamonly.dev/mcp · npm: teamonly · MCP Registry: dev.teamonly/teamonly

Install

The server is part of the teamonly npm package and runs on your computer (deploying reads your project's files). It needs Node.js 20 or newer (22 for logs).

Claude Code

Cursor: Add to Cursor, or put this in ~/.cursor/mcp.json. Claude Desktop (claude_desktop_config.json) and Windsurf take the same:

VS Code

Tools

Tool	What it does
`get_app_rules`	The rules for an app that deploys: React + Vite front end, Hono API on one Cloudflare Worker, D1 database, and how to read the signed-in person. The agent reads this before writing code.
`init`	Starts an app in an empty folder (or from a template), or adds TeamOnly to an app you already have.
`deploy`	Builds the app and puts it online behind your company login.
`versions`	Lists the app's versions: when, who deployed each, and which is live.
`rollback`	Puts the previous version (or a chosen one) back live in seconds.
`pull`	Downloads a deployed app's code into a new folder, so you can change an app whose code isn't on your computer. Owner or admin.
`status`	Who is signed in, the plan, and every app with who can open it.
`logs`	Watches the live app's requests, `console.log` output and errors for 5 to 60 seconds.
`access`	Who can open the app: everyone at the company, or a list of people.
`roles`	Roles people have inside the app, like approver or finance.
`set_secret`	Saves an API key or password for the app.
`sign_in`	Signs in with a work email and the 6-digit code TeamOnly emails.
`start_trial`	Starts the free 14-day trial for a company new to TeamOnly.
`subscribe`	Returns a payment link for a paid plan.
`delete_app`	Deletes the app and its data. Needs the app name to confirm.

How sign-in works

There are no API keys to paste. The agent asks for your work email, calls sign_in, and asks you for the code from the email. If your company is new to TeamOnly it offers the free trial. The sign-in is saved on your computer in ~/.teamonly, shared with the npx teamonly command line tool.

Example

Build a tool where people submit expenses and their manager approves them. Deploy it on TeamOnly so only people at our company can open it.

Templates

Five ready-made internal tools (expense approval, customer lookup, inventory tracker, request form, ask the docs): sohelsd/teamonly-templates.

Source

src/mcp.ts is the server. It ships inside the teamonly npm package next to the command line tool it runs: each tool call runs the matching teamonly command without a terminal and returns its output, so the MCP tools and the CLI always behave the same. This copy is updated with each release. The Dockerfile runs the published package.

License

This repository is MIT licensed. The teamonly npm package it runs has its own license.

Support

Email [email protected].

Source: README.md at commit f38f4f3

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.9.0LatestOct 29, 2026
v0.6.1Oct 26, 2026
v0.6.0Oct 26, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts