runsheet-result-view — Runsheet MCP Resource
runsheet-result-view
is one of 2 resources on the
Runsheet
MCP server. Connect the server and your client can attach it as context.
by client
How to attach runsheet-result-view from your client
- Claude Code Runsheet Resource/runsheet-result-view run in your project directory
- Claude Desktop Runsheet Resource/runsheet-result-view ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Runsheet Resource/runsheet-result-view ~/.cursor/mcp.json
- VS Code Runsheet Resource/runsheet-result-view .vscode/mcp.json
- Zed Runsheet Resource/runsheet-result-view ~/.config/zed/settings.json
- Windsurf Runsheet Resource/runsheet-result-view ~/.codeium/windsurf/mcp_config.json
- Cline Runsheet Resource/runsheet-result-view ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Runsheet Resource/runsheet-result-view ~/.gemini/settings.json
- Grok Runsheet Resource/runsheet-result-view .mcp.json (in your project root)
- ChatGPT Runsheet Resource/runsheet-result-view Settings → Connectors → Advanced → Developer mode
- Claude.ai Runsheet Resource/runsheet-result-view Settings → Connectors → Add custom connector
- LangChain Runsheet Resource/runsheet-result-view pip install langchain-mcp-adapters
Other resources on this server
Runsheet also offers 1 prompt — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 11 November 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.