メニュー
Discover MCP server tools, resources, and prompts without installing plugins. Use when exploring MCP servers or debugging connections. Trigger with /mcp-discovery. Loaded by ai-maestro-plugin
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Batch-approve, refuse, or archive TRDD proposals — move them between the four design/ zones (proposals/ to tasks/ on approve; to refused/ on refuse; to archived/ on complete/cancel/supersede). GATED: only a MANAGER (or solo USER) may approve/refuse/archive; the COS relays but does not approve; list is open to all. Use when a MANAGER drains the proposal queue or archives a finished/cancelled/superseded TRDD. Trigger with /ama-proposal-approvals, 'list pending proposals', or 'approve proposals 4,6'. Column moves within tasks/ are /ama-trdd-transition.
Search, read, verify, and server-mediated mutate TRDDs via the aimaestro-trdd.sh CLI — the AI Maestro dashboard's authorization-aware view of the design/ corpus. Write verbs (edit / approve / refuse / promote / archive) are STRICT, gated by each TRDD's min-approval-requirement with a hard self-approval ban. Use when server-mirrored state or server-side authorization matters: the dashboard kanban, approving a proposal, confirming an approval is real. Trigger with /ama-trdd-server, 'approve this TRDD', 'search TRDDs on the dashboard'. For local design/ file editing use ama-trdd-find/write/update/transition. Loaded by ai-maestro-plugin
Move a TRDD between kanban columns (the 14-stage pipeline plus blocked/failed) — enforcing the transition matrix: who may trigger each move, the frontmatter side-effects it requires, and the AMP broadcast it sends. Each move is role-gated (ORCH dispatches, ARCH designs, INTEGRATOR owns the ->complete flip, assignee signals dev->testing, MEMBER is signal-only). Use when advancing a task through the pipeline. Trigger with /ama-trdd-transition, 'move TRDD X to testing', 'dispatch this task', or 'mark it blocked'. Authoring is /ama-trdd-write, editing /ama-trdd-update, rendering /ama-kanban-render.
Author a new TRDD task-design document under design/ with correct v2 frontmatter — uuid + timestamps, the right zone (tasks/ for a Tier-0 task written directly as 'planned'; proposals/ for a Tier-1/2/3 task needing approval), and a self-contained body. Allowed for every role (MEMBER via COS). Use when a non-trivial task, feature, or decision must be captured as a tracked spec, or a report's decision becomes a TRDD. Trigger with /ama-trdd-write, 'write a TRDD for X', or 'capture this as a task spec'. Finding is /ama-trdd-find, editing /ama-trdd-update, column moves /ama-trdd-transition.
Use when managing teams or governance titles. Trigger with /team-governance. Loaded by ai-maestro-plugin
Manage team kanban boards and tasks. Use when creating, moving, filtering, getting, or editing tasks. Trigger with /team-kanban. Loaded by ai-maestro-plugin
| name | mcp-discovery |
| user-invocable | false |
| description | Discover MCP server tools, resources, and prompts without installing plugins. Use when exploring MCP servers or debugging connections. Trigger with /mcp-discovery. Loaded by ai-maestro-plugin |
| allowed-tools | Bash(mcp-discover.sh:*), Bash(jq:*), Bash(curl:*), Bash(uv:*), Bash(cat:*), Read, Glob |
| metadata | {"author":"Emasoft","version":"2.0.0"} |
Discover and inspect tools, resources, and prompts from any MCP server. Works with installed plugins (via mcp-discover.sh) and standalone/remote servers (via mcp_discovery.py).
mcp-discover.sh at ~/.local/bin/ (included with AI Maestro plugin)jq for JSON processinguv and scripts_dev/mcp_discovery.pyFor installed plugins — use mcp-discover.sh:
mcp-discover.sh --plugin <plugin-name> <server-name>
mcp-discover.sh --plugin <plugin-name> <server-name> --format text
mcp-discover.sh --plugin <plugin-name> <server-name> --format llm
For standalone/remote servers — use mcp_discovery.py:
uv run scripts_dev/mcp_discovery.py --url https://mcp.example.com/sse
uv run scripts_dev/mcp_discovery.py --transport stdio -- npx -y <package>
Find server name if unknown:
jq 'keys[]' < ~/.claude/plugins/cache/<marketplace>/<plugin>/<ver>/.mcp.json
Advanced — call tools, list resources/prompts:
mcp-discover.sh --plugin <name> <server> --method tools/call --tool-name <t> --tool-arg k=v
mcp-discover.sh --plugin <name> <server> --method resources/list
Remote agents — route through API: mcp-discover.sh --plugin <name> <server> --api
{ tools, resources, prompts, serverInfo, capabilities }--raw): Exact protocol response--timeout 60 (default 25s)jq 'keys[]' on .mcp.json--raw to see raw capabilities/mcp-discovery
mcp-discover.sh --plugin chromedev-tools cdt --format text
Expected: list of tool names with descriptions.
uv run scripts_dev/mcp_discovery.py --transport stdio -- npx -y chrome-devtools-mcp@latest
Expected: JSON with tools array.
Copy this checklist and track your progress: