Demo Tasks — ainote MCP Resource

Demo Tasks is one of 2 resources on the ainote MCP server. Connect the server and your client can attach it as context.

by client

How to attach Demo Tasks from your client

• Claude Code ainote Resource/Demo Tasks run in your project directory
• Claude Desktop ainote Resource/Demo Tasks ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor ainote Resource/Demo Tasks ~/.cursor/mcp.json
• VS Code ainote Resource/Demo Tasks .vscode/mcp.json
• Zed ainote Resource/Demo Tasks ~/.config/zed/settings.json
• Windsurf ainote Resource/Demo Tasks ~/.codeium/windsurf/mcp_config.json
• Cline ainote Resource/Demo Tasks ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI ainote Resource/Demo Tasks ~/.gemini/settings.json
• Grok ainote Resource/Demo Tasks .mcp.json (in your project root)
• ChatGPT ainote Resource/Demo Tasks Settings → Connectors → Advanced → Developer mode
• Claude.ai ainote Resource/Demo Tasks Settings → Connectors → Add custom connector
• LangChain ainote Resource/Demo Tasks pip install langchain-mcp-adapters

Other resources on this server

• Demo Categories

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, 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 resource's type and contents.