fetch_content_feed — MisarPost MCP Server MCP Tool Read-only
fetch_content_feed
(fetch content feed) is one of 85 tools on the
MisarPost MCP Server
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call fetch_content_feed from your client
- Claude Code MisarPost MCP Server fetch_content_feed run in your project directory
- Claude Desktop MisarPost MCP Server fetch_content_feed ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MisarPost MCP Server fetch_content_feed ~/.cursor/mcp.json
- VS Code MisarPost MCP Server fetch_content_feed .vscode/mcp.json
- Zed MisarPost MCP Server fetch_content_feed ~/.config/zed/settings.json
- Windsurf MisarPost MCP Server fetch_content_feed ~/.codeium/windsurf/mcp_config.json
- Cline MisarPost MCP Server fetch_content_feed ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MisarPost MCP Server fetch_content_feed ~/.gemini/settings.json
- Grok MisarPost MCP Server fetch_content_feed .mcp.json (in your project root)
- ChatGPT MisarPost MCP Server fetch_content_feed Settings → Connectors → Advanced → Developer mode
- Claude.ai MisarPost MCP Server fetch_content_feed Settings → Connectors → Add custom connector
- LangChain MisarPost MCP Server fetch_content_feed pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http misarpost-mcp https://api.misar.io/post/mcpOther tools on this server
- list_connections
- list_publish_options
- list_account_plugs
- configure_account_plug
- list_posts
- schedule_post
- cancel_post
- get_calendar
- update_post
- reply_to_post
- revert_post
- revert_post_batch
- share_post
- unshare_post
- list_drafts
- review_drafts
- get_stats
- get_analytics_trends
- get_growth_overview
- list_growth_opportunities
- list_growth_playbooks
- get_next_growth_opportunity
- get_contentripple_usage
- repurpose_content
- update_content_variant
- schedule_content_variant
- parse_content_source
- list_repurpose_history
- delete_repurpose_source
- generate_posts
- enhance_topic
- generate_plan
- research_hashtags
- get_optimization_insights
- generate_image
- get_trends
- queue_trend_drafts
- schedule_trend_posts
- refresh_trends
- send_trend_digest
- get_trend_hooks
- get_trend_platform_content
- generate_trend_platform_content
- use_trend_platform_content
- get_trend_performance
- list_post_templates
- get_post_template
- create_post_template
- update_post_template
- delete_post_template
- list_post_tags
- create_post_tag
- update_post_tag
- delete_post_tag
- list_media
- delete_media
- list_video_avatars
- list_video_voices
- create_video_script
- generate_video
- get_video_status
- list_personas
- get_persona
- create_persona
- get_persona_job_status
- rename_persona
- delete_persona
- generate_persona_post
- list_persona_replies
- generate_persona_reply
- review_persona_reply
- get_voice_model
- train_voice_model
- generate_bio_variants
- list_competitor_personas
- analyze_competitor
- list_notifications
- mark_notification_read
- mark_all_notifications_read
- list_webhooks
- create_webhook
- update_webhook
- delete_webhook
- list_workspaces
This list was read from the server itself, by connecting to it and calling tools/list on 17 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.