@atoms-tech/atoms-mcp 0.100.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 +14 -0
- package/dist/apps/src/apps/browse/browse-app.html +37 -37
- package/dist/apps/src/apps/coverage/coverage-app.html +31 -31
- package/dist/apps/src/apps/editor/editor-app.html +34 -34
- package/dist/apps/src/apps/import/import-app.html +26 -26
- package/dist/apps/src/apps/mermaid/mermaid-app.html +242 -242
- package/dist/apps/src/apps/summary/summary-app.html +35 -35
- package/dist/apps/src/apps/trace/trace-app.html +37 -37
- package/dist/index.cjs +1 -1
- package/dist/index.js +1 -1
- package/npm-shrinkwrap.json +5691 -0
- package/package.json +17 -11
package/README.md
CHANGED
|
@@ -159,6 +159,16 @@ If your config writes `-y` today, keep it:
|
|
|
159
159
|
|
|
160
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.
|
|
161
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
|
+
|
|
162
172
|
## Org-Controlled Policy
|
|
163
173
|
|
|
164
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.
|
|
@@ -287,6 +297,10 @@ Identifier persisted to the audit log so you can see which client (e.g., `cursor
|
|
|
287
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.
|
|
288
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.
|
|
289
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
|
+
|
|
290
304
|
## Requirements
|
|
291
305
|
|
|
292
306
|
- Node.js >= 18
|