figmanage 1.3.7 → 1.3.8

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.
Files changed (2) hide show
  1. package/README.md +53 -35
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # figmanage
2
2
 
3
- The Figma workspace layer that agents can manage. Seats, teams, permissions, billing, offboarding -- from the terminal, Claude Code, Cursor, or OpenClaw. Runs locally.
3
+ The Figma workspace layer that agents can manage. Seats, teams, permissions, billing, offboarding -- from Claude Code, Cursor, OpenClaw, or the terminal. Runs locally.
4
4
 
5
5
  [![npm](https://img.shields.io/npm/v/figmanage)](https://www.npmjs.com/package/figmanage)
6
6
  [![downloads](https://img.shields.io/npm/dm/figmanage)](https://www.npmjs.com/package/figmanage)
@@ -12,22 +12,58 @@ The Figma workspace layer that agents can manage. Seats, teams, permissions, bil
12
12
  npm install -g figmanage
13
13
  ```
14
14
 
15
- ## setup
15
+ ## MCP
16
+
17
+ figmanage runs as an MCP server for Claude Code, Cursor, OpenClaw, and other AI assistants. Runs locally via stdio.
16
18
 
17
19
  ```bash
18
- figmanage login
20
+ # Claude Code
21
+ claude mcp add figmanage -- npx -y figmanage
22
+
23
+ # Cursor / OpenClaw / other MCP clients
24
+ # Add to your MCP config:
25
+ {
26
+ "mcpServers": {
27
+ "figmanage": {
28
+ "command": "npx",
29
+ "args": ["-y", "figmanage"]
30
+ }
31
+ }
32
+ }
19
33
  ```
20
34
 
21
- Extracts your Chrome session cookie, prompts for a PAT, and stores credentials locally at `~/.config/figmanage/`. One-time setup -- no env vars, no JSON config editing.
35
+ On first run, figmanage walks you through setup right in the conversation -- extracts your Chrome session cookie, asks you to create a PAT, and stores credentials locally. No env vars, no JSON editing, no separate terminal step.
22
36
 
23
- ```bash
24
- figmanage whoami # verify auth
25
- figmanage logout # clear credentials
37
+ ### what you can ask
38
+
39
+ ```
40
+ "which paid seats haven't been active in 30 days? how much would we save?"
41
+
42
+ "offboard sarah@company.com -- show me everything she owns, then transfer it to jake"
43
+
44
+ "audit and clean up the Mobile App project -- stale files, permissions, branches"
45
+
46
+ "set up a new hire: invite alex@company.com to Design and Engineering as an editor"
47
+
48
+ "run a quarterly design ops report for the org"
49
+
50
+ "audit permissions on the Platform team -- flag external users or overshared files"
26
51
  ```
27
52
 
53
+ ### toolset presets
54
+
55
+ Use `FIGMA_TOOLSETS` to expose only specific tool groups:
56
+
57
+ | Preset | Toolsets |
58
+ |--------|----------|
59
+ | `starter` | navigate, reading, comments, export |
60
+ | `admin` | navigate, org, permissions, analytics, teams, libraries |
61
+ | `readonly` | navigate, reading, comments, export, components, versions |
62
+ | `full` | everything (default) |
63
+
28
64
  ## usage
29
65
 
30
- Commands use a noun-verb pattern: `figmanage <group> <action>`.
66
+ Also works as a CLI. Commands use a noun-verb pattern: `figmanage <group> <action>`.
31
67
 
32
68
  ```bash
33
69
  figmanage org seat-optimization # find inactive paid seats
@@ -47,43 +83,25 @@ figmanage files summary abc123 # pages, components, styles o
47
83
 
48
84
  Run `figmanage <group> --help` for available subcommands. All commands output JSON when piped or when `--json` is passed.
49
85
 
50
- ## AI integration (MCP)
86
+ ## setup
51
87
 
52
- figmanage runs as an MCP server for Claude Code, Cursor, OpenClaw, and other AI assistants. Runs locally via stdio.
88
+ Log into figma.com in Chrome, then:
53
89
 
54
90
  ```bash
55
- # Claude Code
56
- claude mcp add figmanage -- npx -y figmanage
57
-
58
- # Cursor / OpenClaw / other MCP clients
59
- # Add to your MCP config:
60
- {
61
- "mcpServers": {
62
- "figmanage": {
63
- "command": "npx",
64
- "args": ["-y", "figmanage"]
65
- }
66
- }
67
- }
91
+ figmanage login
68
92
  ```
69
93
 
70
- On first run, figmanage walks you through setup right in the conversation -- extracts your Chrome session cookie, asks you to create a PAT, and stores credentials locally. No env vars, no JSON editing, no separate terminal step.
94
+ Extracts your Chrome session cookie, prompts for a PAT, and stores credentials locally at `~/.config/figmanage/`. One-time setup -- no env vars, no JSON config editing.
95
+
96
+ ```bash
97
+ figmanage whoami # verify auth
98
+ figmanage logout # clear credentials
99
+ ```
71
100
 
72
101
  If you prefer CLI setup or need to reconfigure: `npx figmanage login`.
73
102
 
74
103
  Env vars (`FIGMA_PAT`, `FIGMA_AUTH_COOKIE`, etc.) override the config file for backwards compatibility. HTTP transport available via `--mcp --http <port>`.
75
104
 
76
- ### toolset presets (MCP only)
77
-
78
- Use `FIGMA_TOOLSETS` to expose only specific tool groups:
79
-
80
- | Preset | Toolsets |
81
- |--------|----------|
82
- | `starter` | navigate, reading, comments, export |
83
- | `admin` | navigate, org, permissions, analytics, teams, libraries |
84
- | `readonly` | navigate, reading, comments, export, components, versions |
85
- | `full` | everything (default) |
86
-
87
105
  ## auth
88
106
 
89
107
  figmanage uses two Figma API surfaces:
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "figmanage",
3
3
  "mcpName": "io.github.dannykeane/figmanage",
4
- "version": "1.3.7",
4
+ "version": "1.3.8",
5
5
  "description": "MCP server for managing your Figma workspace from the terminal.",
6
6
  "type": "module",
7
7
  "main": "dist/index.js",