Add SHD MCP plugin package

2026-08-24 16:51:12 +05:00
parent ce6e619731
commit 39fb5c02b7
15 changed files with 426 additions and 0 deletions
@@ -0,0 +1,45 @@
+---
+name: shd-routing
+description: Use for any request that asks SHD for data, a project operation, a module workflow, or a change to SHD records. Route the request to the narrowest existing SHD MCP tool and preserve server-side permissions.
+---
+
+# SHD routing and safety
+
+SHD MCP is the source of truth for live data, tool schemas, permissions,
+organization/project scope, conflicts, idempotency, audit and persisted
+readback. Do not invent fields, statuses, identifiers, routes or capabilities.
+
+## Route the request
+
+- Project list, project status, deadlines or project context: use the Projects
+  Core tools and the `shd-active-projects` or `shd-project-status` workflow.
+- ProjectBase schema, records, links or data quality: use Project DB tools and
+  the `shd-project-db-audit` workflow.
+- Tasks, task projects, task status or task dates: use Tasks tools and the
+  `shd-task-workflow` workflow.
+- Project files and paths: use Files tools and the `shd-project-files` workflow.
+- Finance or CRM records: use the specific module tools and the
+  `shd-finance-crm` workflow; use project context for a high-level overview.
+- A multi-record change: use `shd-safe-bulk-change` before any mutation.
+
+Use `shd_capabilities` only when the available module or permission boundary is
+unclear. If a tool or module is unavailable, report that fact instead of
+falling back to an undocumented endpoint.
+
+## Read-first rule
+
+For every write, first read the target and its relevant schema or metadata.
+Only perform a mutation when the user explicitly requested that mutation. A
+request to inspect, summarize, compare, audit or suggest is not permission to
+write.
+
+Preserve the exact server result. Separate confirmed values from inference,
+and include affected identifiers, conflicts, validation errors and final
+readback when the server returns them.
+
+## Scope and secrets
+
+Never ask for or expose access tokens, passwords, cookies, private keys, raw
+public-link bearer tokens or integration secrets. Never use a user-provided
+project name as an identifier when SHD has not resolved it to a returned
+project code or ID.