feat: complete SHD MCP plugin workflows and widget
Validate SHD MCP plugin / validate (push) Has been cancelled

This commit is contained in:
2026-08-24 17:25:38 +03:00
parent 39fb5c02b7
commit 08cf3672a4
86 changed files with 1707 additions and 5 deletions
+48
View File
@@ -0,0 +1,48 @@
# SHD MCP in ChatGPT
This file describes the user-side connection. The repository cannot create an
app inside another persons ChatGPT account and never stores OAuth tokens.
## Custom app
1. Open ChatGPT settings and enable Developer mode for Apps/Connectors.
2. Create a custom app with this MCP endpoint:
`https://shd.xyz.su/mcp`
3. Complete the SHD OAuth sign-in and consent screen.
4. Start a new chat or refresh the app connection.
5. Test with: `Покажи активные проекты с датой завершения и статусом.`
The expected flow is:
1. ChatGPT calls `shd_list_projects` with `archived: false`.
2. ChatGPT may call `shd_render_projects_widget` with the returned project
array.
3. The widget renders the sorted register and can call `shd_get_project` for
a selected row.
The MCP tools remain usable without the widget. A failed OAuth connection is
an account/endpoint configuration problem, not a missing token in this repo.
## Public directory
Directory submission is a separate optional release step. It is needed for
public discovery and reviewed installation, not for internal use or a custom
app added manually in ChatGPT. Before submission, the owner must provide the
production HTTPS endpoint, OAuth metadata, privacy/support URLs, accurate app
metadata, test prompts and any review credentials requested by OpenAI.
Use the official [submission guide](https://developers.openai.com/plugins/deploy/submission)
and [plugin guidelines](https://developers.openai.com/plugins/app-guidelines).
## License choice
This repository currently uses the proprietary SHD MCP Plugin License. Public
visibility means the source can be viewed; it does not grant permission to
redistribute, resell, modify or use it outside an authorized SHD account.
MIT would grant anyone permission to use, copy, modify, publish, sublicense and
sell the plugin, including forks, while retaining only the copyright notice and
license text. Switching to MIT is a product/legal decision and is not done
implicitly by publishing the repository.