Skip to main content

Check out a video walkthrough showing AI with Space

Get introduced to AI in Sp§ace.
If you use agentic AI tools like Claude, Codex, or Craft Agents, you can connect them to Space. Once connected, your AI tool can read your Space data (like your inbox, today, and your projects) and — if you allow it — help you make changes (like creating tasks or updating plans). The connection between Space and your AI tool is made using MCP, an emerging standard that many agentic tools support. Getting started is easy. So what can you do?
  • Quick context: get a briefing of today, this week, or a specific project.
  • Search and review: find tasks, check long-term plans, and spot what’s stuck.
  • Plan with more context: connect other information sources to your agent for assisted goalsetting.
  • Hands-on changes: create and update tasks/projects/areas/groups, and manage yearly/quarterly plans.
Some prompts to get you started:
  • “What does today look like in Space? Include events.”
  • “Open my current week and highlight anything overdue.”
  • “Get my action items from these meeting notes and add them to the Summer Promo project in Space.”

​
Enable MCP in Space

MCP support is included in the Mac version of Space.
In Space:
  1. Open Settings.
  2. Go to AI.
  3. Turn on Enable MCP.
When off, you can configure:
  • Port (default: 2402)
  • Access Mode (Read Only or Read & Write)

​
Choose an access mode

​
Read Only

Pick this when you want safe visibility from your AI tool.
  • AI tools can read views, projects, areas, groups, and long-term plans.
  • Write tools are not exposed.
  • Any write attempt is rejected.

​
Read & Write

Read & Write lets your AI tool make changes in Space — including deleting data. Start with Read Only, and only switch to Read & Write once you trust your tool setup.
Pick this when you want the AI to actively manage your Space data.
  • Includes all read tools.
  • Adds write tools for task/project/area/group/plan management.
  • Destructive actions require confirmation:
    • Interactive confirmation when the MCP client supports elicitation, or
    • Explicit confirm_destructive: true when interactive confirmation is unavailable.

​
Connect an AI tool to Space

​
Tools that support MCPB files (like Claude Desktop)

The easiest way to connect Space to your AI tool is using an MCP Bundle (an .mcpb file). This works in Claude Desktop. Open Settings and the AI tab. Under MCPB, click Reveal in Finder and double-click the Space.mcpb file. In your AI tool you’ll enter the pairing code shown in Space Settings, and you’re done.

​
Connecting manually

In Settings > AI, copy the Endpoint shown in the Authenticate section (for example: http://127.0.0.1:2402/). Space MCP listens on localhost (127.0.0.1) and uses HTTP transport with OAuth. During OAuth you’ll be asked for a time-based pairing code that Space shows in the same Settings screen.
Time-based pairing code shown in Space settings

​
Connecting to Claude Code CLI

Run: 
claude mcp add --transport http space http://127.0.0.1:2402/
Then:
  1. Start Claude Code: claude
  2. Run /mcp
  3. Select space (it will show as unauthenticated)
  4. Confirm authentication
  5. Enter the pairing code when your browser opens
Claude Code showing Space MCP connection

​
Connecting to OpenAI Codex CLI

Run: 
codex mcp add Space --url http://127.0.0.1:2402/
A browser window should open asking you for the pairing code. Get it from Space (Settings > AI).
The Codex Desktop app will automatically pick this registration up as well.

​
Connecting to OpenAI Codex Desktop App

  1. Open Settings → MCP Servers
  2. Click + Add server
  3. Give the server a name (for example: Space)
  4. Select Streamable HTTP as the transport
  5. Enter http://127.0.0.1:2402/ as the URL
Adding an MCP server in Codex Desktop
Click Save. An Authenticate button will appear next to the server. Click it and enter the pairing code from Space (Settings > AI).
Authenticating an MCP server in Codex Desktop

​
Connecting to Craft Agents

  1. In Craft Agents, go to Sources → MCPs
  2. Click +
  3. When asked what to connect, enter “Connect to ‘Space Life Planner’, an MCP server at http://127.0.0.1:2402/”
  4. Wait a bit, then allow opening the OAuth screen
  5. Enter the pairing code from Space (Settings > AI)

​
Connected clients

Space shows all connected clients in Settings > AI. You can disconnect a clients to immediately revoke access.

​
Reference: what you can do

​
Read operations

  • get_inbox, get_day, get_day_events, get_week, get_project, get_area
  • list_projects, list_areas, list_groups
  • list_long_term_plans, get_long_term_plan
  • search_todos

​
Write operations

Task operations:
  • add_task, edit_task, delete_task, sort_tasks
  • bulk_edit_tasks, bulk_delete_tasks
  • schedule_task_event
Structure operations:
  • add_project, edit_project, delete_project
  • add_area, edit_area, delete_area
  • add_group, edit_group, sort_groups, delete_group
Planning metadata and cleanup:
  • edit_day, edit_week
  • delete_completed_todos (project/area scope)
Long-term planning (yearly and quarterly plans):
  • add_long_term_plan
  • edit_long_term_plan
  • list_long_term_plans (defaults to active plans when no state filter is passed)

​
Prompts and resources (optional)

You can use Space with tools only. Prompts and resources are optional, but useful in clients that support them.

​
Prompts

Prompts are pre-packaged workflows: Space bundles the right data plus a strong instruction template. Prompt families:
  • Briefings (quick overview): day_brief, week_brief
  • Planning (actionable plans): day_plan, week_plan
  • Operational review: inbox_triage, project_review
  • Long-term planning: ltp_summary, ltp_status_update, ltp_next_actions, ltp_risks, ltp_execution_alignment, ltp_plan_assist

​
Resources

Resources are read-only snapshots that some MCP clients can preload before generating a response. Examples:
  • space://context/today
  • space://context/this_week
  • space://context/day/{date}
  • space://context/week/{year}/{week}
  • space://plans/active
  • space://projects/{project_id}/summary
If your client does not support resources, you can ignore them and call tools directly (get_day, get_week, get_day_events, etc.).

​
Important behavior notes

  • Space must be running to use it with your AI tools.
  • day_iso values are local calendar day semantics (YYYY-MM-DD) in the current system timezone.
  • Week inputs use ISO week semantics (week + year).
  • get_day_events uses the same visible-calendar pipeline as the in-app calendar.
  • Tools that offer include_late / include_late_day filtering fall back to Space preferences when omitted.
  • sort_tasks follows your rollover preference for day/week late-task visibility. Sorting a day or week also normalizes visible late tasks to that day/week.
  • Group intensity is a score from 0 to 10; use null in edit_group to disable group intensity scoring. Group intensity is primarily used for yearly and quarterly plans.
  • IDs such as project_id, area_id, group_id, and plan_id are opaque tokens returned by Space.