Using Dayward with Claude via MCP
Claude is an AI assistant made by Anthropic. On its own, it's excellent at writing, thinking, and answering questions — but it doesn't know anything about your life, your tasks, or your schedule.
That changes with MCP.
MCP (Model Context Protocol) is an open standard that lets Claude connect to external apps and actually do things in them — not just talk about them. Once you connect Dayward's MCP server to Claude, you can manage your entire day through conversation: capture tasks, plan your week, search past entries, reorganize your wiki, and more — without ever switching tabs.
What the Dayward MCP server does
The Dayward MCP server gives Claude read and write access to your Dayward account. Specifically, Claude can:
- Read and create daily entries
- Add, move, rename, complete, and delete tasks across your Now / Next / Later / Done sections
- Move overdue tasks to Now in bulk
- Search past entries by keyword
- Read, create, update, move, and delete blocks on wiki pages
- Search your wiki pages
- Pull usage statistics and daily recaps
In short: anything you can do in Dayward manually, you can ask Claude to do for you.
How to connect
Dayward's MCP server is hosted at:
https://mcp.dayward.app/mcp
On Claude.ai or Claude Desktop
- Open Claude and go to Settings (click your profile icon).
- Navigate to Connectors (or Integrations).
- Click the + button, then "Add custom connector".
- Give it a name — "Dayward" works fine — and paste in the server URL:
https://mcp.dayward.app/mcp - Click Add. The Dayward tools will become available immediately.
You'll be prompted to authorize Dayward to connect to your account the first time a Dayward tool is used in a conversation.
Plans: All Claude plans support custom MCP connections. Free accounts are limited to one custom connector. Paid plans (Pro, Max, Team, Enterprise) support multiple connectors and offer significantly more usage — which matters if you're using Claude to help manage your day regularly.
Alternative: JSON config (advanced)
If you prefer editing config files directly, or the Connectors UI isn't available in your version of Claude Desktop, you can add Dayward via the JSON config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"dayward": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.dayward.app/mcp"
]
}
}
}
This requires Node.js to be installed. Save the file and restart Claude Desktop.
Key use cases
Once Dayward is connected, Claude becomes a genuinely useful day planner. Here are some of the most practical ways to use it.
1. Plan your day in plain English
Instead of opening Dayward and manually dragging tasks around, tell Claude what you're working with:
"I have a dentist appointment at 2pm and need to finish the client proposal before then. Here's everything I want to get done today: [list]. Help me organize these into Now, Next, and Later and move them in Dayward."
Claude will read your current tasks, apply the Now / Next / Later / Done framework, and update your Dayward entry — in one shot.
2. Quick task capture
When you're in the middle of something and don't want to break flow:
"Add 'follow up with Sarah about the invoice' to my Next section for today."
Done. No tab switching, no clicking around.
3. Move overdue tasks forward
It's Monday morning. You have a pile of unfinished tasks from last week scattered across multiple days.
"Move all my overdue tasks to Now."
Claude handles it instantly. You start the week with a clean slate rather than hunting through past entries.
4. End-of-day recap
At the close of your day:
"Give me a recap of what I got done today, what's still open, and any notes from my entry."
Claude pulls your completed tasks, open items, and any journal notes you wrote, then summarizes them clearly — useful for daily standups, weekly reviews, or just closing out the day with intention.
5. Reorganize your wiki
Your Dayward wiki pages aren't just readable by Claude — they're editable. You can ask Claude to restructure an entire page:
"On my 'Product Roadmap' wiki page, move the 'Backlog' section below 'In Progress,' and rename the 'Ideas' section to 'Someday / Maybe.'"
Claude reads the current block structure, makes the changes, and reports back what it did.
6. Search across your entries
Dayward keeps a record of every day. Claude can search it:
"When did I last work on the brand refresh project? What did I write about it?"
Claude searches your past entries and surfaces the relevant ones — no scrolling through your history manually.
A few things worth knowing
Claude doesn't have memory between conversations. When you start a new chat, Claude doesn't remember your previous sessions — but it can always read your current Dayward entry and get right back up to speed. Starting a conversation with "Check today's entry and remind me what I'm working on" is a good habit.
Be specific with dates. If you want Claude to look at a specific day's entry, say the date explicitly: "Look at my entry for March 28th" rather than "look at yesterday." This prevents Claude from defaulting to today.
The MCP server requires an active Dayward account. If you're on a trial or your subscription lapses, the connection will still work but Claude won't be able to find any data.
Example workflows
These examples show exactly what to say and what happens under the hood.
Example: Add a task mid-conversation
User prompt: "Add 'review the Q2 budget doc' to my Next section for today."
What happens: Claude calls add_task with the title and today's date, placing the task in the Next section of your daily entry.
Result: The task appears immediately in Dayward under Next — no app switching required.
Example: Morning planning session
User prompt: "Pull up today's entry. I have a 10am call with the team and need to ship the landing page by end of day. Help me prioritize what's in Next and move the right things to Now."
What happens: Claude calls get_entry to read your current task list, reasons about urgency and the constraints you described, then calls apply_plan to batch-move tasks — putting the most time-sensitive items into Now and deferring lower-priority work to Later.
Result: Your Now section is updated in one shot with the tasks that matter most today. Claude tells you exactly what it moved and why.
Example: Search past entries for context
User prompt: "When did I last work on the onboarding flow? What did I write about it?"
What happens: Claude calls search_entries with the query "onboarding flow", which searches your full entry history and returns matching days with relevant text snippets.
Result: Claude surfaces the dates and the relevant notes from those entries — useful for picking up where you left off or writing a status update.
Example: End-of-day recap
User prompt: "Give me a recap of today — what I finished, what's still open, and any notes from my meetings."
What happens: Claude calls get_recap_context to pull completed tasks, meeting headers and their child notes, and any bullets in the Notes section. It then summarizes everything in plain English.
Result: A concise daily summary ready to paste into a standup, a journal, or just to close the day with clarity.
What to try first
If you've just connected Dayward to Claude, here's a good first prompt to see it working:
"Pull up today's Dayward entry. Tell me what's in my Now section and what's in Next. Then ask me how I want to prioritize the day."
From there, it's yours to explore.
Questions or issues?
Email us at hello@dayward.app or visit dayward.canny.io/feedback to report a problem or request a feature.