get_blog_posts — Context Studios MCP MCP Tool Read-only
get_blog_posts
(get blog posts) is one of 28 tools on the
Context Studios MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_blog_posts from your client
- Claude Code Context Studios MCP get_blog_posts run in your project directory
- Claude Desktop Context Studios MCP get_blog_posts ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Context Studios MCP get_blog_posts ~/.cursor/mcp.json
- VS Code Context Studios MCP get_blog_posts .vscode/mcp.json
- Zed Context Studios MCP get_blog_posts ~/.config/zed/settings.json
- Windsurf Context Studios MCP get_blog_posts ~/.codeium/windsurf/mcp_config.json
- Cline Context Studios MCP get_blog_posts ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Context Studios MCP get_blog_posts ~/.gemini/settings.json
- Grok Context Studios MCP get_blog_posts .mcp.json (in your project root)
- ChatGPT Context Studios MCP get_blog_posts Settings → Connectors → Advanced → Developer mode
- Claude.ai Context Studios MCP get_blog_posts Settings → Connectors → Add custom connector
- LangChain Context Studios MCP get_blog_posts pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.contextstudios.ai/api/public/mcp
Other tools on this server
- ai_project_estimator
- blog_explorer
- fetch
- get_company_info
- get_comparison
- get_featured_glossary_terms
- get_glossary_by_tech_stack
- get_glossary_term
- get_guide
- get_location_page
- get_page
- get_pricing
- get_related_glossary_terms
- get_services
- list_comparisons
- list_glossary_categories
- list_guides
- list_location_pages
- request_consultation
- search
- search_blog_knowledge
- search_comparisons
- search_content
- search_glossary
- search_guides
- search_location_pages
- search_pages
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.