An incident-desk MCP server with a fixed resource, two resource templates, a prompt, a tool that borrows the client's model (sampling) and a tool that asks the operator to approve a restart (elicitation). Driven by a plain SDK client in JUnit and by raw curl, so the JSON-RPC for both server-to-client requests is committed. Also captured: a client that declared neither capability (a gated tool degrades, an ungated one returns an isError result), a slow client hitting the server request timeout, and protocol=STATELESS silently dropping every tool that takes McpSyncRequestContext (one WARN line, an empty tools/list). Negotiated protocol version is 2025-11-25; the 2026-07-28 spec is not implemented by SDK 2.1.0. No docs/ folder. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_017ic4b5jAFLJrmUXmbo5EuV
14 lines
613 B
Plaintext
14 lines
613 B
Plaintext
# prompts/list and prompts/get
|
|
prompt postmortem -- Draft a blameless postmortem for an incident
|
|
arg incidentId required=true
|
|
arg audience required=false
|
|
|
|
get postmortem(INC-1043, on-call manager) ->
|
|
[USER] Write a blameless postmortem for the on-call manager. Sections: impact, timeline, root cause, follow-ups. Use only the log below.
|
|
|
|
11:02:44 search-api WARN index segment merge running
|
|
11:02:51 search-api INFO p99 latency 840ms (SLO 500ms)
|
|
|
|
|
|
get postmortem(INC-9999) -> McpError: Error invoking prompt method: postmortem in com.ankurm.mcpadvanced.IncidentPrompts./nCause: No such incident: INC-9999
|