status — TweetFeed MCP Resource

status is one of 7 resources on the TweetFeed MCP server. Connect the server and your client can attach it as context.

by client

How to attach status from your client

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

Other resources on this server

• counts
• trends
• campaigns
• iocs-today
• iocs-week
• iocs-month

TweetFeed also offers 3 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.