distill-url-to-markdown — AgentDiet AI Token Diet & Context Window Distiller MCP Prompt
distill-url-to-markdown
is one of 2 prompts on the
AgentDiet AI Token Diet & Context Window Distiller
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke distill-url-to-markdown from your client
- Claude Code AgentDiet AI Token Diet & Context Window Distiller Prompt/distill-url-to-markdown run in your project directory
- Claude Desktop AgentDiet AI Token Diet & Context Window Distiller Prompt/distill-url-to-markdown ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AgentDiet AI Token Diet & Context Window Distiller Prompt/distill-url-to-markdown ~/.cursor/mcp.json
- VS Code AgentDiet AI Token Diet & Context Window Distiller Prompt/distill-url-to-markdown .vscode/mcp.json
- Zed AgentDiet AI Token Diet & Context Window Distiller Prompt/distill-url-to-markdown ~/.config/zed/settings.json
- Windsurf AgentDiet AI Token Diet & Context Window Distiller Prompt/distill-url-to-markdown ~/.codeium/windsurf/mcp_config.json
- Cline AgentDiet AI Token Diet & Context Window Distiller Prompt/distill-url-to-markdown ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AgentDiet AI Token Diet & Context Window Distiller Prompt/distill-url-to-markdown ~/.gemini/settings.json
- Grok AgentDiet AI Token Diet & Context Window Distiller Prompt/distill-url-to-markdown .mcp.json (in your project root)
- ChatGPT AgentDiet AI Token Diet & Context Window Distiller Prompt/distill-url-to-markdown Settings → Connectors → Advanced → Developer mode
- Claude.ai AgentDiet AI Token Diet & Context Window Distiller Prompt/distill-url-to-markdown Settings → Connectors → Add custom connector
- LangChain AgentDiet AI Token Diet & Context Window Distiller Prompt/distill-url-to-markdown pip install langchain-mcp-adapters
Other prompts on this server
AgentDiet AI Token Diet & Context Window Distiller also offers 10 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 19 October 2026.
A listing does not declare its prompts, 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 prompt's arguments.