get_blog_post — Cure Cancer With AI MCP Tool Read-only
get_blog_post
(get blog post) is one of 15 tools on the
Cure Cancer With AI
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_blog_post from your client
- Claude Code Cure Cancer With AI get_blog_post run in your project directory
- Claude Desktop Cure Cancer With AI get_blog_post ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Cure Cancer With AI get_blog_post ~/.cursor/mcp.json
- VS Code Cure Cancer With AI get_blog_post .vscode/mcp.json
- Zed Cure Cancer With AI get_blog_post ~/.config/zed/settings.json
- Windsurf Cure Cancer With AI get_blog_post ~/.codeium/windsurf/mcp_config.json
- Cline Cure Cancer With AI get_blog_post ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Cure Cancer With AI get_blog_post ~/.gemini/settings.json
- Grok Cure Cancer With AI get_blog_post .mcp.json (in your project root)
- ChatGPT Cure Cancer With AI get_blog_post Settings → Connectors → Advanced → Developer mode
- Claude.ai Cure Cancer With AI get_blog_post Settings → Connectors → Add custom connector
- LangChain Cure Cancer With AI get_blog_post pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http cure-cancer-with-ai https://www.curecancerwithai.com/api/mcpOther tools on this server
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.