corpus_summary — SRI — MCP Server Inspector MCP Resource

corpus_summary is one of 3 resources on the SRI — MCP Server Inspector MCP server. Connect the server and your client can attach it as context.

by client

How to attach corpus_summary from your client

• Claude Code SRI — MCP Server Inspector Resource/corpus_summary run in your project directory
• Claude Desktop SRI — MCP Server Inspector Resource/corpus_summary ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor SRI — MCP Server Inspector Resource/corpus_summary ~/.cursor/mcp.json
• VS Code SRI — MCP Server Inspector Resource/corpus_summary .vscode/mcp.json
• Zed SRI — MCP Server Inspector Resource/corpus_summary ~/.config/zed/settings.json
• Windsurf SRI — MCP Server Inspector Resource/corpus_summary ~/.codeium/windsurf/mcp_config.json
• Cline SRI — MCP Server Inspector Resource/corpus_summary ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI SRI — MCP Server Inspector Resource/corpus_summary ~/.gemini/settings.json
• Grok SRI — MCP Server Inspector Resource/corpus_summary .mcp.json (in your project root)
• ChatGPT SRI — MCP Server Inspector Resource/corpus_summary Settings → Connectors → Advanced → Developer mode
• Claude.ai SRI — MCP Server Inspector Resource/corpus_summary Settings → Connectors → Add custom connector
• LangChain SRI — MCP Server Inspector Resource/corpus_summary pip install langchain-mcp-adapters

Other resources on this server

• corpus_changes
• corpus_index

SRI — MCP Server Inspector also offers 2 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 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.