explain_task — Notematics MCP Prompt
explain_task
is one of 1 prompt on the
Notematics
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke explain_task from your client
- Claude Code Notematics Prompt/explain_task run in your project directory
- Claude Desktop Notematics Prompt/explain_task ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Notematics Prompt/explain_task ~/.cursor/mcp.json
- VS Code Notematics Prompt/explain_task .vscode/mcp.json
- Zed Notematics Prompt/explain_task ~/.config/zed/settings.json
- Windsurf Notematics Prompt/explain_task ~/.codeium/windsurf/mcp_config.json
- Cline Notematics Prompt/explain_task ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Notematics Prompt/explain_task ~/.gemini/settings.json
- Grok Notematics Prompt/explain_task .mcp.json (in your project root)
- ChatGPT Notematics Prompt/explain_task Settings → Connectors → Advanced → Developer mode
- Claude.ai Notematics Prompt/explain_task Settings → Connectors → Add custom connector
- LangChain Notematics Prompt/explain_task pip install langchain-mcp-adapters
Notematics also offers 1 resource — 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 11 November 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.