@specset/cli 0.5.0 → 0.6.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
@@ -9,14 +9,23 @@ Add the Specset skill to your agent, then just ask it a question — the skill i
9
9
  **Claude Code:**
10
10
 
11
11
  ```
12
- /plugin marketplace add specsetai/specset-skill
12
+ /plugin marketplace add specsetai/specset-plugins
13
13
  /plugin install specset
14
14
  ```
15
15
 
16
- **Any other agent** (Cursor, Codex, Gemini CLI, custom): tell it to fetch and follow
17
- `https://raw.githubusercontent.com/specsetai/specset-skill/main/plugins/specset/skills/specset/SKILL.md`.
16
+ **Codex:**
18
17
 
19
- Then ask something like *"What mechanical equipment is scheduled on level 2 of my project?"*
18
+ ```bash
19
+ codex plugin marketplace add specsetai/specset-plugins
20
+ codex plugin add specset@specset-plugins
21
+ ```
22
+
23
+ Start a new Codex task after installation so the bundled skills and MCP tools load.
24
+
25
+ **Any other agent** (Cursor, Gemini CLI, custom): tell it to fetch and follow
26
+ `https://raw.githubusercontent.com/specsetai/specset-plugins/main/plugins/specset/skills/specset/SKILL.md`.
27
+
28
+ Then ask something like _"What mechanical equipment is scheduled on level 2 of my project?"_
20
29
 
21
30
  ## Manual install
22
31
 
@@ -79,6 +88,14 @@ specset skill print specset-submittals
79
88
 
80
89
  Updating an agent plugin does not upgrade an existing global CLI. Run `npm install -g @specset/cli@latest`, then re-run `specset skill install --target <agent>` to refresh direct-installed skill copies.
81
90
 
91
+ ## MCP transports and files
92
+
93
+ The Codex/Claude plugin uses the local `specset mcp` stdio server. Hosted clients use the server's stateless Streamable HTTP endpoint at `https://<host>/mcp`; OAuth consent selects and binds the organization. Both dispatch through the same allowlisted Specset tool registry.
94
+
95
+ Local agents can upload with `specset files upload <path>` and download project assets with the entity download commands. The hosted endpoint exposes OpenAI-compatible `uploadFile` and `getFileDownload` tools; uploads stream from the host's short-lived file URL into Specset storage.
96
+
97
+ The hosted endpoint exposes MCP OAuth 2.1 discovery, Client ID Metadata Document support, PKCE authorization, short-lived audience-bound access tokens, and rotating refresh tokens. First-party clients may also use a Specset session bearer token with an explicit organization header.
98
+
82
99
  ## Configuration
83
100
 
84
101
  - Credentials and the active host/org live in `~/.config/specset/config.yml` (mode 0600).