blog_catalog — postcopilot mcp MCP Resource

blog_catalog is one of 1 resource on the postcopilot mcp MCP server. Connect the server and your client can attach it as context.

by client

How to attach blog_catalog from your client

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

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.