The Complete Guide to Beyond Time MCP: Setup, Commands, and Real Workflows

The Model Context Protocol — MCP — is the bridge between Claude and external tools. Without it, you paste data into a chat window and hope Claude makes sense of it. With it, Claude can read, write, and query structured information in tools you already use.

Beyond Time was among the first planning tools to ship an MCP server. That matters because goal tracking is exactly the kind of task where copy-paste creates friction: you shouldn’t have to manually export your weekly summary before asking Claude to analyze it.

This guide covers everything — what the Beyond Time MCP actually does, how to set it up, every command that’s available, and what real planning sessions look like when Claude has live access to your data.

What Is MCP and Why Does It Matter for Planning?

MCP stands for Model Context Protocol, an open standard developed by Anthropic. It defines how AI models communicate with external servers — think of it as a typed API that Claude knows how to call.

Before MCP, integrating Claude with a tool meant one of three things: copy-pasting content, building a custom API wrapper, or using a third-party automation layer like Zapier. Each approach adds latency and friction.

With an MCP server, Claude can call specific functions in a tool, receive structured results, and act on them — all within a single conversation. The key word is structured. Claude doesn’t just receive a wall of text; it receives typed data with clear field names. That makes its responses dramatically more precise.

For planning specifically, this closes a meaningful gap. Goal tracking systems accumulate data that’s most useful when an AI can reason over it in context. Asking “which of my goals am I behind on?” is a different conversation when Claude can actually pull the answer rather than trust what you manually summarize.

What the Beyond Time MCP Server Does

The Beyond Time MCP server exposes your planning data — goals, progress logs, milestones, and time allocations — as callable functions. Claude can invoke these functions during a conversation, process the returned data, and either display it or use it to inform its next suggestion.

There are five categories of functionality:

Goal management. Create, list, update, and archive goals. Each goal stores a title, description, target date, category (health, work, learning, etc.), and a progress percentage.

Progress logging. Log a progress entry against any active goal. Entries include a timestamp, a numeric value (percentage or units), and an optional note. This is the “daily check-in” function.

Milestone tracking. Goals can have sub-milestones. The MCP lets you list milestones for a goal, mark one complete, and add new ones mid-goal.

Weekly summaries. A single command retrieves a digest of the past seven days: which goals received log entries, which didn’t, progress deltas, and any goals near their target date.

Time allocation queries. If you’ve linked calendar data within Beyond Time, the MCP can return how many hours were actually allocated to goal-related work versus how many were planned.

This is the practical layer that makes Claude useful as a planning partner rather than just a text generator.

How to Set Up the Beyond Time MCP

Setup involves three steps: getting your API key, adding the server to Claude Desktop’s config file, and verifying the connection.

Step 1: Get Your Beyond Time API Key

Log into beyondtime.ai and navigate to Settings > Integrations > MCP. Click “Generate API Key.” Copy the key — you’ll need it in the next step.

Keep this key private. It grants read and write access to all your goals and progress logs.

Step 2: Edit Claude Desktop’s Config File

Claude Desktop stores its MCP configuration in a JSON file. Its location depends on your OS:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Open that file in any text editor. If it doesn’t exist yet, create it. Add the Beyond Time server entry to the mcpServers object:

{
  "mcpServers": {
    "beyond-time": {
      "command": "npx",
      "args": ["-y", "@beyondtime/mcp-server"],
      "env": {
        "BEYOND_TIME_API_KEY": "your-api-key-here"
      }
    }
  }
}

Replace your-api-key-here with the key you copied in Step 1.

Step 3: Restart Claude Desktop and Verify

Quit Claude Desktop completely and relaunch it. Open a new conversation and type:

List my active goals using Beyond Time.

If the connection is working, Claude will return a formatted list of your goals pulled directly from Beyond Time. If it returns an error or no data, double-check the JSON syntax in your config file — a missing comma or bracket is the most common issue.

The Full Command Set

Once connected, Claude can invoke these Beyond Time MCP functions either explicitly (when you ask) or implicitly (when they’re relevant to a planning question).

list_goals

Returns all active goals with their titles, categories, target dates, and current progress.

When Claude uses it: Anytime you ask about your goals without specifying one in particular. Also used as the first step in weekly reviews.

Example prompt:

What goals am I currently tracking in Beyond Time? Which ones 
are more than 30 days out from their target date?

create_goal

Creates a new goal with a title, optional description, category, and target date.

When Claude uses it: When you describe a new goal in conversation and ask Claude to record it.

Example prompt:

I want to track writing 50,000 words by December 31. Create a 
goal for this in Beyond Time — category: creative work, 
target: December 31, 2025.

log_progress

Logs a progress entry against a specific goal. Requires a goal identifier (name or ID), a value, and optionally a note.

When Claude uses it: During daily check-ins or when you report what you’ve done.

Example prompt:

I wrote 1,200 words today on the novel. Log that against my 
writing goal. Note: slow start, but picked up pace after 
switching locations.

get_weekly_summary

Returns a digest of the past seven days across all goals: which goals received entries, total progress made, goals with no activity, and upcoming target dates.

When Claude uses it: During weekly reviews, or when you ask how you’re tracking overall.

Example prompt:

Pull my Beyond Time weekly summary. Tell me which goals I 
neglected this week and why that might have happened based on 
what I've told you about my schedule.

list_milestones

Returns milestones for a specific goal.

Example prompt:

What milestones have I set for my product launch goal? Which 
ones are still open?

complete_milestone

Marks a specific milestone as complete.

Example prompt:

I finished the beta user interviews. Mark that milestone 
complete on my product launch goal.

add_milestone

Adds a new milestone to an existing goal.

Example prompt:

Add a milestone to my product launch goal: "Complete pricing 
page copy" — due October 28.

get_time_allocation

Returns planned versus actual hours for goal-related work in a given time window. Requires calendar integration to be active in Beyond Time.

Example prompt:

How many hours did I actually spend on deep work this week 
versus what I planned? Use Beyond Time to pull the data.

What Real Planning Sessions Look Like

Here’s where the MCP stops being theoretical. These are illustrative session transcripts showing how the commands work together.

Monday Morning Goal Review

You: Pull my active goals and give me a quick status check. 
Any that need attention this week?

Claude: [calls list_goals]

Here's where you stand:

- Product launch (Work) — 68% complete, target Nov 15. 
  On track if you hit the pricing and onboarding milestones.
- Writing 50k words (Creative) — 34% complete, target Dec 31. 
  Slightly behind pace; you'd need ~450 words/day from here.
- Strength training 3x/week (Health) — 71% for the month. 
  Last logged 4 days ago — may need a session this week.

Anything you want to log or adjust before we plan the week?

End-of-Day Progress Log

You: Quick end-of-day log. I had three meetings eat my morning, 
got about 45 minutes of real writing done — around 800 words. 
Also skipped the gym.

Claude: [calls log_progress for writing goal]
[calls log_progress for health goal with a zero-session note]

Logged. Writing: 800 words added (running total: 17,400 / 50,000). 
Health: no session today noted.

You're now 34.8% toward the writing target — still within 
recoverable range for the week if tomorrow is cleaner. The 
three-meeting morning is a pattern worth watching; want me to 
flag it if it shows up again next week?

Friday Weekly Summary Review

You: Let's do a proper weekly review. Pull the summary from 
Beyond Time.

Claude: [calls get_weekly_summary]

Here's this week:

Goals with logged activity (4/5):
- Product launch: +12 percentage points. Completed "pricing 
  page copy" milestone — good week.
- Writing: +8pp. Three of five weekdays logged. Pace 
  improving slightly.
- Strength training: 2 sessions logged vs. 3 planned.
- Language learning: 4 of 7 days. Consistent.

Goal with no activity:
- Online course completion: zero entries this week.

What happened with the course? If it's no longer active, 
we should archive it rather than let it sit as silent 
deadweight in your list.

That last exchange illustrates something worth noting: Claude with MCP access can surface the absence of data, not just its presence. A goal with no log entries is information.

What the MCP Cannot Do

Being clear about limitations is as important as explaining capabilities.

It cannot access other apps. The Beyond Time MCP only reads and writes Beyond Time data. It has no visibility into your calendar unless you’ve explicitly linked it within Beyond Time’s settings.

It cannot take automatic action. Nothing happens until you ask Claude something. The MCP is reactive, not autonomous. Claude won’t send you a reminder or log progress without you initiating a conversation.

It cannot analyze data it hasn’t been shown. If you want Claude to reason about trends across months, you need to request that data explicitly. Claude doesn’t maintain a persistent memory of previous sessions by default.

It does not replace structured goal-setting. The MCP is a data-access layer. If your goals are vague or your milestones aren’t meaningful, better tooling won’t fix that. The quality of Claude’s planning help is proportional to the quality of your goal definitions.

The Workflow That Gets the Most from MCP

Across different use patterns, three habits consistently improve the value of the Beyond Time MCP connection.

Daily micro-logs. A 60-second end-of-day check-in — “log 800 words to writing goal, no gym today” — creates the data density that makes weekly summaries useful. Without consistent logging, the weekly summary is sparse.

Weekly review as the anchor. Friday or Sunday, pull the summary, have Claude identify the one goal that needs a different strategy, and adjust. This is where the MCP earns its setup cost.

Goal hygiene. Regularly archive completed or abandoned goals. A list of six active goals is actionable. A list of eighteen is noise. Ask Claude to flag any goal with no log entries in the past fourteen days.

How This Differs from Asking Claude Without MCP

The honest answer: for simple questions, not much. If you manually paste your goals into a chat, Claude can reason about them. The difference is friction and data freshness.

Without MCP, you have to maintain a separate document or habit of exporting data before each conversation. The inevitable result is that you skip the export on busy days, which are precisely the days when planning help is most useful. With MCP, the data is always current because it comes from the live source.

The more meaningful difference is bidirectional access. Without MCP, Claude can only read what you paste. With MCP, Claude can write — creating goals, logging entries, marking milestones — without you having to switch to a separate app and update it manually.

That feedback loop, where the AI both reads your data and updates it in real time, is qualitatively different from a chat conversation. It makes Claude a genuine planning partner rather than a text editor with opinions.

Getting Started: The First 20 Minutes

Set aside 20 minutes for the initial setup. Most of it is the configuration file.

1. Generate your API key in Beyond Time’s settings.
2. Edit claude_desktop_config.json to add the server entry.
3. Restart Claude Desktop.
4. Run list_goals to confirm the connection.
5. If you have fewer than three goals recorded in Beyond Time, create one during this session using the create_goal command.
6. Log one progress entry — even a small one — using log_progress.

That’s the minimum viable setup. From here, a single daily check-in before you close your laptop builds the data foundation that makes the weekly summary genuinely useful.

The goal isn’t a perfect system. It’s a conversation that has access to real data, updated regularly enough to be worth consulting.

Your first action: Open Claude Desktop, add the Beyond Time MCP config, and ask Claude to list your goals. The connection either works or it doesn’t — and if it doesn’t, the error message will tell you exactly what to fix.

Related:

• How to Set Up Beyond Time MCP
• Beyond Time MCP Full Walkthrough
• 5 Prompts for Beyond Time via MCP
• The Complete Guide to MCP Integration for Goal Tracking
• Planning with Claude AI

Tags: beyond time mcp, mcp setup, claude ai planning, goal tracking ai, model context protocol