@atoms-tech/atoms-mcp 0.99.0 → 0.105.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -81,6 +81,9 @@ ATOMS MCP uses **OAuth 2.1 with PKCE** — the same flow used by GitHub CLI and
81
81
  # Interactive login (opens browser)
82
82
  npx @atoms-tech/atoms-mcp@latest login
83
83
 
84
+ # Email and password account (asks for the password in this terminal)
85
+ npx @atoms-tech/atoms-mcp@latest login --email you@example.com
86
+
84
87
  # Check current session
85
88
  npx @atoms-tech/atoms-mcp@latest whoami
86
89
 
@@ -95,12 +98,17 @@ npx @atoms-tech/atoms-mcp@latest logout
95
98
  3. Tokens are stored locally at `~/.atoms/credentials.json`
96
99
  4. Tokens auto-refresh — you only need to login once
97
100
 
101
+ The browser login continues with Google. If you sign in to ATOMS with an email and password, use
102
+ `login --email` instead: it asks for your password without showing it (never pass it as an argument),
103
+ signs in, and saves the same credentials file.
104
+
98
105
  You can also set `ATOMS_ACCESS_TOKEN` as an environment variable for CI/headless use.
99
106
 
100
107
  ## CLI Commands
101
108
 
102
109
  ```
103
110
  npx @atoms-tech/atoms-mcp@latest login # Authenticate with ATOMS
111
+ npx @atoms-tech/atoms-mcp@latest login --email [address] # Sign in with email and password
104
112
  npx @atoms-tech/atoms-mcp@latest logout # Clear stored credentials
105
113
  npx @atoms-tech/atoms-mcp@latest whoami # Show current user
106
114
  npx @atoms-tech/atoms-mcp@latest --help # Show all commands
@@ -151,6 +159,16 @@ If your config writes `-y` today, keep it:
151
159
 
152
160
  atoms-mcp checks for a newer version once a day and tells you in `atoms_status` and in the next tool result. Set `ATOMS_MCP_NO_UPDATE_CHECK=1` to turn the check off.
153
161
 
162
+ ### Pinning one version
163
+
164
+ A team that checks each tool release before use (for example under a quality system) can run one exact version instead of `@latest`. Write the version you checked, from the [changelog](./CHANGELOG.md), in place of `X.Y.Z`, and change it only after you have checked the next one:
165
+
166
+ ```json
167
+ "args": ["-y", "@atoms-tech/atoms-mcp@X.Y.Z"]
168
+ ```
169
+
170
+ From 0.100.1 the package also names each of its direct dependencies at one exact version. From 0.101.0 it also ships an `npm-shrinkwrap.json`, so npm installs every dependency, direct or not, at the version that release was tested with, and a fix in one of them reaches you with the next ATOMS release. The remote connector (claude.ai, iPad) always runs the current release.
171
+
154
172
  ## Org-Controlled Policy
155
173
 
156
174
  Org admins can set guardrails (read-only mode, allowed toolsets, project scope, required confirmations) for every member of their org through **Org Settings → MCP Access Policy** in the ATOMS web app. Both this stdio package and the hosted MCP server (`https://<project>.supabase.co/functions/v1/mcp-server`) read the same `mcp_policy` table, one policy for each organization where you are an editor or admin, and judge each call by the organization of the project it touches. This package re-reads the policies every 30 seconds; the hosted server reads them on every request. So an admin's policy applies to their own organization's projects regardless of how a user connects, and a change needs no restart. If you belong to several organizations, a tool is listed when at least one of them allows it, and a call is refused when the organization of its project refuses it.
@@ -279,6 +297,10 @@ Identifier persisted to the audit log so you can see which client (e.g., `cursor
279
297
  - **Project scoping** — `ATOMS_MCP_PROJECT_ID` binds a session to a single project and rejects tool calls referencing any other one — defense-in-depth on top of RLS.
280
298
  - **No secrets in the package** — The Supabase anon key is a publishable client key (like a Firebase API key). It grants zero data access without a valid user JWT.
281
299
 
300
+ ## Report a vulnerability
301
+
302
+ If you think you have found a security vulnerability in ATOMS, email [support@atoms.tech](mailto:support@atoms.tech) with "Security" in the subject line. Please do not report it in a public issue. The disclosure policy is at [https://atoms.tech/security-policy.txt](https://atoms.tech/security-policy.txt), and the contact details at [https://atoms.tech/.well-known/security.txt](https://atoms.tech/.well-known/security.txt).
303
+
282
304
  ## Requirements
283
305
 
284
306
  - Node.js >= 18