Experience cards (empty) — tickadoo mcp MCP Resource

Experience cards (empty) is one of 4 resources on the tickadoo mcp MCP server. Connect the server and your client can attach it as context.

by client

How to attach Experience cards (empty) from your client

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

Other resources on this server

• Experience cards
• Availability date picker
• Availability date picker (empty)

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.