delinea-mcp 2.0.0rc1__tar.gz

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 (29) hide show
  1. delinea_mcp-2.0.0rc1/.gitignore +246 -0
  2. delinea_mcp-2.0.0rc1/CHANGELOG.md +281 -0
  3. delinea_mcp-2.0.0rc1/LICENSE +21 -0
  4. delinea_mcp-2.0.0rc1/PKG-INFO +559 -0
  5. delinea_mcp-2.0.0rc1/README.md +527 -0
  6. delinea_mcp-2.0.0rc1/SECURITY.md +39 -0
  7. delinea_mcp-2.0.0rc1/delinea_mcp/__init__.py +14 -0
  8. delinea_mcp-2.0.0rc1/delinea_mcp/annotations.py +167 -0
  9. delinea_mcp-2.0.0rc1/delinea_mcp/api.py +285 -0
  10. delinea_mcp-2.0.0rc1/delinea_mcp/auth/__init__.py +0 -0
  11. delinea_mcp-2.0.0rc1/delinea_mcp/auth/as_config.py +206 -0
  12. delinea_mcp-2.0.0rc1/delinea_mcp/auth/routes.py +220 -0
  13. delinea_mcp-2.0.0rc1/delinea_mcp/auth/validators.py +69 -0
  14. delinea_mcp-2.0.0rc1/delinea_mcp/config.py +23 -0
  15. delinea_mcp-2.0.0rc1/delinea_mcp/constants.py +208 -0
  16. delinea_mcp-2.0.0rc1/delinea_mcp/field_push.py +89 -0
  17. delinea_mcp-2.0.0rc1/delinea_mcp/secretserver_users.py +205 -0
  18. delinea_mcp-2.0.0rc1/delinea_mcp/server.py +480 -0
  19. delinea_mcp-2.0.0rc1/delinea_mcp/session.py +44 -0
  20. delinea_mcp-2.0.0rc1/delinea_mcp/strongdm_tools.py +981 -0
  21. delinea_mcp-2.0.0rc1/delinea_mcp/tls.py +42 -0
  22. delinea_mcp-2.0.0rc1/delinea_mcp/tool_guard.py +210 -0
  23. delinea_mcp-2.0.0rc1/delinea_mcp/tools.py +2651 -0
  24. delinea_mcp-2.0.0rc1/delinea_mcp/transports/__init__.py +0 -0
  25. delinea_mcp-2.0.0rc1/delinea_mcp/transports/origin.py +114 -0
  26. delinea_mcp-2.0.0rc1/delinea_mcp/transports/sse.py +68 -0
  27. delinea_mcp-2.0.0rc1/delinea_mcp/transports/streamable_http.py +95 -0
  28. delinea_mcp-2.0.0rc1/delinea_mcp/user_platform_tools.py +1068 -0
  29. delinea_mcp-2.0.0rc1/pyproject.toml +78 -0
@@ -0,0 +1,246 @@
1
+ # Created by https://www.toptal.com/developers/gitignore/api/python,macos,visualstudiocode
2
+ # Edit at https://www.toptal.com/developers/gitignore?templates=python,macos,visualstudiocode
3
+
4
+ ### macOS ###
5
+ # General
6
+ .DS_Store
7
+ .AppleDouble
8
+ .LSOverride
9
+
10
+ # Icon must end with two \r
11
+ Icon
12
+
13
+
14
+ # Thumbnails
15
+ ._*
16
+
17
+ # Files that might appear in the root of a volume
18
+ .DocumentRevisions-V100
19
+ .fseventsd
20
+ .Spotlight-V100
21
+ .TemporaryItems
22
+ .Trashes
23
+ .VolumeIcon.icns
24
+ .com.apple.timemachine.donotpresent
25
+
26
+ # Directories potentially created on remote AFP share
27
+ .AppleDB
28
+ .AppleDesktop
29
+ Network Trash Folder
30
+ Temporary Items
31
+ .apdisk
32
+
33
+ ### macOS Patch ###
34
+ # iCloud generated files
35
+ *.icloud
36
+
37
+ ### Python ###
38
+ # Byte-compiled / optimized / DLL files
39
+ __pycache__/
40
+ *.py[cod]
41
+ *$py.class
42
+
43
+ # C extensions
44
+ *.so
45
+
46
+ # Distribution / packaging
47
+ .Python
48
+ build/
49
+ develop-eggs/
50
+ dist/
51
+ downloads/
52
+ eggs/
53
+ .eggs/
54
+ lib/
55
+ lib64/
56
+ parts/
57
+ sdist/
58
+ var/
59
+ wheels/
60
+ share/python-wheels/
61
+ *.egg-info/
62
+ .installed.cfg
63
+ *.egg
64
+ MANIFEST
65
+
66
+ # PyInstaller
67
+ # Usually these files are written by a python script from a template
68
+ # before PyInstaller builds the exe, so as to inject date/other infos into it.
69
+ *.manifest
70
+ *.spec
71
+
72
+ # Installer logs
73
+ pip-log.txt
74
+ pip-delete-this-directory.txt
75
+
76
+ # Unit test / coverage reports
77
+ htmlcov/
78
+ .tox/
79
+ .nox/
80
+ .coverage
81
+ .coverage.*
82
+ .cache
83
+ nosetests.xml
84
+ coverage.xml
85
+ *.cover
86
+ *.py,cover
87
+ .hypothesis/
88
+ .pytest_cache/
89
+ cover/
90
+
91
+ # Translations
92
+ *.mo
93
+ *.pot
94
+
95
+ # Django stuff:
96
+ *.log
97
+ local_settings.py
98
+ db.sqlite3
99
+ db.sqlite3-journal
100
+
101
+ # Flask stuff:
102
+ instance/
103
+ .webassets-cache
104
+
105
+ # Scrapy stuff:
106
+ .scrapy
107
+
108
+ # Sphinx documentation
109
+ docs/_build/
110
+
111
+ # PyBuilder
112
+ .pybuilder/
113
+ target/
114
+
115
+ # Jupyter Notebook
116
+ .ipynb_checkpoints
117
+
118
+ # IPython
119
+ profile_default/
120
+ ipython_config.py
121
+
122
+ # pyenv
123
+ # For a library or package, you might want to ignore these files since the code is
124
+ # intended to run in multiple environments; otherwise, check them in:
125
+ # .python-version
126
+
127
+ # pipenv
128
+ # According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
129
+ # However, in case of collaboration, if having platform-specific dependencies or dependencies
130
+ # having no cross-platform support, pipenv may install dependencies that don't work, or not
131
+ # install all needed dependencies.
132
+ #Pipfile.lock
133
+
134
+ # poetry
135
+ # Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
136
+ # This is especially recommended for binary packages to ensure reproducibility, and is more
137
+ # commonly ignored for libraries.
138
+ # https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
139
+ #poetry.lock
140
+
141
+ # pdm
142
+ # Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
143
+ #pdm.lock
144
+ # pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
145
+ # in version control.
146
+ # https://pdm.fming.dev/#use-with-ide
147
+ .pdm.toml
148
+
149
+ # PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
150
+ __pypackages__/
151
+
152
+ # Celery stuff
153
+ celerybeat-schedule
154
+ celerybeat.pid
155
+
156
+ # SageMath parsed files
157
+ *.sage.py
158
+
159
+ # Environments
160
+ .env
161
+ .env.live
162
+ .env.*.local
163
+ .creds
164
+ .venv
165
+ env/
166
+ venv/
167
+ ENV/
168
+ env.bak/
169
+ venv.bak/
170
+
171
+ # Spyder project settings
172
+ .spyderproject
173
+ .spyproject
174
+
175
+ # Rope project settings
176
+ .ropeproject
177
+
178
+ # mkdocs documentation
179
+ /site
180
+
181
+ # mypy
182
+ .mypy_cache/
183
+ .dmypy.json
184
+ dmypy.json
185
+
186
+ # Pyre type checker
187
+ .pyre/
188
+
189
+ # pytype static type analyzer
190
+ .pytype/
191
+
192
+ # Cython debug symbols
193
+ cython_debug/
194
+
195
+ # PyCharm
196
+ # JetBrains specific template is maintained in a separate JetBrains.gitignore that can
197
+ # be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
198
+ # and can be added to the global gitignore or merged into this file. For a more nuclear
199
+ # option (not recommended) you can uncomment the following to ignore the entire idea folder.
200
+ #.idea/
201
+
202
+ ### Python Patch ###
203
+ # Poetry local configuration file - https://python-poetry.org/docs/configuration/#local-configuration
204
+ poetry.toml
205
+
206
+ # ruff
207
+ .ruff_cache/
208
+
209
+ # LSP config files
210
+ pyrightconfig.json
211
+
212
+ ### VisualStudioCode ###
213
+ .vscode/*
214
+ !.vscode/settings.json
215
+ !.vscode/tasks.json
216
+ !.vscode/launch.json
217
+ !.vscode/extensions.json
218
+ !.vscode/*.code-snippets
219
+
220
+ # Local History for Visual Studio Code
221
+ .history/
222
+
223
+ # Built Visual Studio Code Extensions
224
+ *.vsix
225
+
226
+ ### VisualStudioCode Patch ###
227
+ # Ignore all local history of files
228
+ .history
229
+ .ionide
230
+
231
+ # End of https://www.toptal.com/developers/gitignore/api/python,macos,visualstudiocode
232
+
233
+
234
+ # custom local temp directories
235
+
236
+ .cache/
237
+ .artifacts/
238
+
239
+ config.json
240
+ !.vscode/mcp.json
241
+
242
+ # Private Claude directory submission materials (never commit)
243
+ .submission/
244
+
245
+ # Playwright MCP browser snapshots (local tool output)
246
+ .playwright-mcp/
@@ -0,0 +1,281 @@
1
+ # Release Notes
2
+
3
+ ## v2.0.0 — Claude Code plugin, PyPI package, secret-visibility hardening
4
+
5
+ ### Distribution
6
+
7
+ - Published on PyPI as `delinea-mcp`, with a `delinea-mcp` console script
8
+ (`uvx delinea-mcp`). The implementation moved into the package
9
+ (`delinea_mcp/server.py`, `delinea_mcp/api.py`); the root `server.py` and
10
+ `delinea_api.py` stay as aliases, so `uv run server.py` still works.
11
+ - New Claude Code plugin in `plugins/delinea`, with the
12
+ **no-secret-visibility** and **building-reports** skills. The skills also
13
+ work on their own with any Delinea MCP connection.
14
+ - Runs without a config file: connection settings fall back to
15
+ `DELINEA_USERNAME`, `DELINEA_BASE_URL`, `PLATFORM_HOSTNAME`,
16
+ `PLATFORM_SERVICE_ACCOUNT` and `PLATFORM_TENANT_ID`, and
17
+ `DELINEA_MCP_CONFIG` can point at a config file. Fixes a bug where no
18
+ tools were registered when `config.json` wasn't in the working directory.
19
+
20
+ ### Secret visibility
21
+
22
+ - `get_secret` and `fetch` mask password-type fields (`********`) and list
23
+ them under `maskedFields`.
24
+ - Plaintext reveal is **disabled by default**. When the user or an
25
+ administrator enables it (new `secret_reveal_mode` config key,
26
+ `DELINEA_SECRET_REVEAL_MODE`, or the plugin's "Allow revealing passwords"
27
+ setting), a new `reveal_secret_field` tool returns one plaintext value
28
+ only after the user approves an MCP elicitation prompt ("Reveal secret
29
+ value") sent by the server, on both the 2026-07-28 input-required flow and
30
+ older protocol versions. Modes: `disabled` (default), `elicit`,
31
+ `client_approval`.
32
+ - Over stdio, `get_secret_environment_variable` fetches the secret itself
33
+ and writes a private (`0600`), self-deleting env file that expires after
34
+ 15 minutes, returning only its path. It no longer needs curl or jq, and
35
+ works the same in bash, PowerShell and cmd (the old cmd script needed
36
+ `head` and `sed`, which Windows doesn't have).
37
+ - Over stdio, `set_secret_field_environment_variable` uploads `file:`
38
+ sources directly, and for `env:`/`stdin` returns a one-line command that
39
+ runs the server's own Python (`delinea_mcp.field_push`, hidden prompt for
40
+ `stdin`). No curl, jq or PowerShell 7 needed.
41
+ - New `script_delivery` config key (`auto`, `file`, `inline`). Scripts
42
+ returned over HTTP transports state their requirements; the broken bash
43
+ script (both `export` lines on one line, mis-quoted `jq`, two API calls)
44
+ is fixed, and cmd is refused there in favor of PowerShell.
45
+
46
+ ### Plugin setup
47
+
48
+ - **One Platform service account is enough.** With a Platform hostname set,
49
+ the vault session signs in through the Platform, and the Platform user,
50
+ role and report tools now reuse that account unless a separate
51
+ `PLATFORM_SERVICE_*` pair is given. The plugin settings say so.
52
+ - Error text built from API responses masks any value the user just
53
+ submitted (`set_secret_field_environment_variable` and `field_push`), even
54
+ if a server echoes it in a validation message.
55
+ - `scripts/seed_test_tenant.py` creates the folder, secret and IDs the live
56
+ tests expect; the live tests can sign in through the Platform
57
+ (`LIVE_SS_VIA_PLATFORM=1`).
58
+ - Outbound TLS is verified against the **operating system's certificate
59
+ store** (`truststore`), so the server signs in on networks that inspect
60
+ TLS (Cloudflare Gateway, Zscaler, Netskope) and to on-premises Secret
61
+ Servers with internal CAs. Before, `requests` used Python's bundled list
62
+ and failed with `CERTIFICATE_VERIFY_FAILED`. Set `DELINEA_TLS_TRUST=bundled`
63
+ to keep the old behavior.
64
+ - New **Enabled tools** plugin setting (`DELINEA_ENABLED_TOOLS`, a
65
+ comma-separated list) limits which tools are registered. Blank or `all`
66
+ enables every tool, which is the default.
67
+ - The plugin launches with `uvx --no-config --python 3.13`. It's
68
+ distributed through the official Claude plugin directory.
69
+ - **The plugin never reads config files from your project.** Claude Code
70
+ starts the server in the open project's folder, so a `config.json` in a
71
+ cloned repository could have redirected `delinea_base_url` and received your
72
+ keychain password. With `DELINEA_MCP_PLUGIN=1` (set by the plugin) the
73
+ server ignores `./config.json` and `$DELINEA_MCP_CONFIG` and takes settings
74
+ only from the plugin configuration. `uvx` runs with `--no-config` so a
75
+ project's `uv.toml` / `[tool.uv]` can't point the download at another
76
+ package index.
77
+
78
+ - **Windows support in the plugin is experimental.** The server, skills
79
+ and credential handoff are platform-neutral, but the plugin's startup
80
+ check and `/delinea:setup` helper are POSIX shell scripts (they run under
81
+ the Git Bash that Claude Code uses on Windows) and haven't been verified
82
+ on Windows yet; there `setup-uv.sh link` only prints PATH instructions.
83
+ - The startup check also notices when the plugin's settings were never
84
+ entered (Claude Code then leaves the server out silently) and tells the
85
+ user to fill them in under `/plugin`.
86
+ - A `SessionStart` hook checks for `uvx` and, only when it's missing or off
87
+ PATH, asks Claude to offer `/delinea:setup`. It never installs anything.
88
+ - The `/delinea:setup` skill checks the machine, asks the user once, then
89
+ installs uv (Homebrew, WinGet, Scoop, pipx, a private PyPI virtual
90
+ environment, or uv's official installer), links `uvx` onto PATH so no
91
+ restart is needed where possible, and pre-downloads the server. The logic
92
+ lives in `plugins/delinea/scripts/setup-uv.sh` (no `sudo`); it covers
93
+ proxies, blocked Python downloads, and a no-uv fallback.
94
+
95
+ ### Tool quality
96
+
97
+ - Every tool has a `title` (also set in its annotations).
98
+ - API failures return the Secret Server or Platform error message, its
99
+ `errorCode`, and a hint on what to do, instead of a bare HTTP status.
100
+ - `run_report` links the Secret Server REST API docs, points at
101
+ `list_example_reports` as its schema reference, and caps rows with
102
+ `max_rows` (default 200), reporting `total_rows` and `truncated`.
103
+ - `search_secrets`, `search_folders` and every `list` action page with
104
+ `take` (default 50, max 500) and `skip`. `get_folder` returns the
105
+ descendant tree only with `all_children=True`.
106
+
107
+ ### Breaking changes
108
+
109
+ - Removed `ai_generate_and_run_report`, the Azure OpenAI dependency and the
110
+ `azure_openai_*` config keys. Build SQL from `list_example_reports` and
111
+ run it with `run_report`.
112
+ - `get_secret` and `fetch` no longer return plaintext passwords; use
113
+ `get_secret_environment_variable`, or enable `secret_reveal_mode` and use
114
+ `reveal_secret_field`.
115
+ - Over stdio, `get_secret_environment_variable` returns
116
+ `{"script_path", "run", ...}` and `set_secret_field_environment_variable`
117
+ returns `{"result": ...}` or `{"command": ...}` instead of script text.
118
+ Over HTTP transports, `get_secret_environment_variable` no longer
119
+ supports `cmd`.
120
+ - `get_folder` and `folder_management("get")` no longer include all
121
+ children by default.
122
+ - `run_report` errors start with `Report '<name>' failed:`.
123
+ - StrongDM tools register only with `strongdm_enabled: true`. StrongDM, a
124
+ Delinea company, will be fully supported in a future release.
125
+
126
+ ### Other
127
+
128
+ - License copyright: Delinea, 2026 (originally written by Gal Diskin, 2025).
129
+ - New `SECURITY.md` with private vulnerability reporting.
130
+ - Secret Server sign-in rejections (400/401/403) explain the Secret Server
131
+ 12.1+ **Prevent direct API authentication** default and how to fix it
132
+ (use an Application Account, or grant **Bypass Direct API Authentication
133
+ Restriction**); the README has a new "Secret Server account" section.
134
+ - Security work released since 1.1.0 (#60, #61, #63, #64, #65): `authlib`
135
+ dropped in favor of `joserfc` (now `>=1.7.5`, for GHSA-jpxq-7h8p-2q76 and
136
+ GHSA-9pg5-8c7x-5hfx) for JWT handling; mcp 2.2.0, pyjwt 2.15.1,
137
+ urllib3 2.8.0 and anyio 4.14.2 in the lockfile; refreshed container base
138
+ image and pinned CI actions; tool error text preserved on MCP SDK 2.1+.
139
+
140
+ ## v1.1.0 — MCP protocol 2026-07-28, StrongDM backend, security batch
141
+
142
+ ### MCP protocol / SDK
143
+
144
+ - Migrated to the `mcp` 2.0 SDK line (`MCPServer`). The server now speaks
145
+ **protocol revision 2026-07-28** (stateless requests, `server/discover`)
146
+ while continuing to serve 2024-11-05…2025-11-25 handshake clients.
147
+ - New **streamable HTTP endpoint at `/mcp`** — the current MCP transport —
148
+ mounted alongside the legacy `/mcp/sse` + `/messages/` HTTP+SSE endpoints
149
+ (unchanged) and stdio. New config keys `streamable_http_stateless` /
150
+ `streamable_http_json_response` (both default `true`).
151
+ - **RFC 9728 protected-resource metadata** at
152
+ `/.well-known/oauth-protected-resource` (+ `/mcp` alias); 401/403 responses
153
+ now carry `WWW-Authenticate` headers with `resource_metadata` so clients
154
+ can discover the authorization server per the current MCP auth spec.
155
+ - Every tool now publishes **behaviour annotations**
156
+ (read-only/destructive/idempotent hints) via `tools/list`.
157
+
158
+ ### StrongDM (new optional backend, experimental)
159
+
160
+ - `pip install "delinea-mcp[strongdm]"` adds ten compound SDM admin tools:
161
+ `sdm_search`, `sdm_audit_access`, `sdm_grant_access` (time-boxed JIT or
162
+ standing), `sdm_revoke_access`, `sdm_user_management` (onboard/offboard),
163
+ `sdm_role_management`, `sdm_resource_health`, `sdm_access_requests`,
164
+ `sdm_activity_report`, `sdm_network_status`. See `docs/strongdm.md`.
165
+ - House safety rails: confirm + audit-comment gating on destructive actions,
166
+ preview mode, candidate disambiguation before any mutation, bounded lists,
167
+ verification read-backs.
168
+
169
+ ### Security
170
+
171
+ - OAuth guard now applies to the SSE message channel (`/messages/` routed
172
+ through FastAPI instead of a dependency-bypassing mount) — previously
173
+ every `tools/call` over SSE+OAuth was unauthenticated (#52).
174
+ - `/oauth/register` actually requires the registration PSK
175
+ (constant-time compare; Bearer or JSON `secret`) (#53).
176
+ - `enabled_tools` allowlist now covers SS-local and Platform registrars (#54).
177
+ - Newly written JWT private keys are chmod 0600 (#55).
178
+ - Dependency patches: cryptography 50.0.0 (GHSA-537c-gmf6-5ccf), joserfc
179
+ 1.7.4, pyjwt 2.13.0, python-multipart 0.0.32, starlette 1.6.0
180
+ (multiple PYSEC advisories); `pip-audit` reports clean.
181
+
182
+ ### Fixes
183
+
184
+ - SSE clients are now advertised the exact guarded POST path
185
+ (`/messages/`); the transport handlers no longer trigger a second ASGI
186
+ response after streaming ends.
187
+ - Connector guides pointed at a `/sse` endpoint that never existed; they
188
+ now document `/mcp` (and `/mcp/sse` as legacy).
189
+
190
+ ### Notes
191
+
192
+ - SDK v2 runs sync tools on worker threads; token acquisition in the SS
193
+ session and Platform header cache is now lock-protected.
194
+ - Follow-up recorded: CIMD (Client ID Metadata Documents) support — DCR is
195
+ deprecated as of protocol 2026-07-28 but current connectors still use it.
196
+
197
+ ## v1.0.0 — Platform-first user management (breaking)
198
+
199
+ In Delinea cloud and Platform-integrated tenants the authoritative user
200
+ store is the Delinea Platform identity directory; Secret Server's own
201
+ `/v1/users/*` endpoints only manage local-mirror records there. v1.0.0
202
+ makes the canonical `user_management` and `search_users` tools talk to
203
+ the Platform identity API by default.
204
+
205
+ ### Breaking
206
+
207
+ - `user_management` now talks to the Delinea Platform identity API
208
+ (`/identity/CDirectoryService/*`, `/identity/UserMgmt/*`). The previous
209
+ Secret-Server-local implementation has moved to
210
+ `secretserver_local_user_management` (in
211
+ `delinea_mcp.secretserver_users`).
212
+ - `search_users` now searches the Platform user directory. The previous
213
+ `/v1/users` search has moved to `search_secretserver_local_users`.
214
+ - Clients that pinned `enabled_tools` to `user_management` /
215
+ `search_users` will now hit Platform endpoints. SS-only deployments
216
+ must either:
217
+ 1. configure Platform (`PLATFORM_HOSTNAME`,
218
+ `PLATFORM_SERVICE_ACCOUNT`, `PLATFORM_SERVICE_PASSWORD`,
219
+ `PLATFORM_TENANT_ID`), or
220
+ 2. switch the client to the new `secretserver_local_*` tool names.
221
+
222
+ ### Added
223
+
224
+ - **`update_secret_fields`** — read-template → mutate-non-password-fields
225
+ → verify flow. Refuses fields whose template marks `isPassword=True`
226
+ unless `allow_password_fields=True`; routes audit comments through
227
+ `autoCheckout`/`autoCheckIn`/`autoComment` query params.
228
+ - **`bulk_user_response`** — opinionated combinator over
229
+ `/v1/bulk-user-operations/*`. Scenarios: `compromise`, `offboard`,
230
+ `unlock`, `reenable`, `force_logout`. Requires `confirm=True` _and_ a
231
+ non-empty `comment`; `confirm=False` returns a preview that makes no
232
+ API calls.
233
+ - **`platform_role_management`** — Platform identity role CRUD using
234
+ `SaasManage/StoreRole`, `Roles/UpdateRole`, `Redrock/Query`, and
235
+ `SaasManage/RemoveRole`.
236
+ - **`platform_user_role_management`** — add/remove/list users on a
237
+ Platform role via `Roles/UpdateRole` `Users.Add`/`Users.Delete`.
238
+ - **`platform_user_management`** retained as a deprecated alias for
239
+ `user_management`; old clients keep working.
240
+
241
+ ### Notes
242
+
243
+ - Live-verified against:
244
+ - a Secret-Server cloud tenant for all SS-side flows
245
+ (`update_secret_fields`, `bulk_user_response` preview,
246
+ `secretserver_local_*`, search/fetch).
247
+ - a Delinea Platform tenant (`dartlabs.secureplatform.io`) for the
248
+ Platform-side flows (`user_management` full CRUD lifecycle,
249
+ `search_users`, `platform_role_management` read, `platform_user_role_management`
250
+ read). 32 live integration tests pass.
251
+ - Platform endpoint discovery: on modern Delinea Platform tenants the
252
+ identity-API namespace is `/identity/api/...` (not `/identity/...`),
253
+ and `GetUser` was replaced by `GetUserAttributes` (POST `{"ID": …}`).
254
+ This release fixes those paths.
255
+ - Role mutation endpoints (`SaasManage/StoreRole`, `Roles/UpdateRole`,
256
+ `SaasManage/RemoveRole`) are **discovery-driven**: the tools attempt
257
+ the documented endpoint and only fall back to a structured guidance
258
+ error on HTTP 404 (typical on modern Platform tenants using the
259
+ `xpmheadless` scope, which exposes user CRUD but not role CRUD).
260
+ Tenants that DO expose those endpoints get the real result. The
261
+ guidance error directs callers to the SS-side `role_management` /
262
+ `user_role_management` tools or the Platform admin UI.
263
+
264
+ The current release introduces a comprehensive tool set for integrating Delinea Secret Server with the Model Context Protocol.
265
+
266
+ ## Highlights
267
+
268
+ - Manage folders, secrets, users, groups and roles directly from the MCP server.
269
+ - Inbox management and access request helpers for administrators.
270
+ - Coding agent utilities and ChatGPT compatible tools (`search` and `fetch`).
271
+ - Initial Delinea Platform support limited to user management.
272
+ - Choose between SSE or STDIO transport modes.
273
+ - OAuth 2.0 authentication with Dynamic Client Registration.
274
+ - TLS support for secure connections.
275
+ - Verified with ChatGPT (deep research and custom connector), Claude Desktop, remote Claude connector, VSCode Copilot and openwebui.
276
+
277
+ ## Roadmap
278
+
279
+ 1. Passthrough authentication
280
+ 2. Streaming HTTP transport support
281
+ 3. Expanded tool coverage on the Delinea Platform and other Delinea products
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 Delinea (originally written by Gal Diskin, 2025)
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.