corpus-status — Zoning Signal MCP Resource

corpus-status is one of 4 resources on the Zoning Signal MCP server. Connect the server and your client can attach it as context.

by client

How to attach corpus-status from your client

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

Other resources on this server

• signal-model-schema
• agent-start-page
• agent-full-index

Zoning Signal also offers 5 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.