Local MCP, included with Ikuna Pro

Ikuna knows what you are working on. Now your AI can too.

Connect Ikuna to Claude Desktop, Codex, or another compatible MCP client. Ask about the work that happened on your Mac, or start the right workspace from the conversation.

“What did I work on today?”

“Why was my focus so fragmented this afternoon?”
“Start my Writing Ikuna.”

Ikuna supplies the facts. Your AI helps you understand them or act on them, within the permissions you choose.

Get Ikuna Pro See how it connects

Stop explaining your day from scratch

An AI assistant can help with your work, but it usually starts each conversation missing the useful part: what you were actually doing.

Ikuna already has the structure of the day: the workspace you intended to use, sessions, active time, deep-work periods, context switches, apps, categories, and gaps where tracking was idle, private, or unavailable.

The model does not become the source of truth. Ikuna keeps the activity model, metric rules, and workspace state. The model reads the evidence you allow and helps interpret it.

Ask questions your AI could not answer before

What did I work on today?
When was my longest deep-work session?
Why did my focus break after lunch?
Which apps or websites caused the most context switching?
Compare focus in my Writing Ikuna this week with last week.
Show me the evidence behind that pattern.

If Ikuna does not have enough history, the honest answer is “not enough evidence”. It should not invent a productivity story from thin data.

Work with your Ikunas from the conversation

With workspace-control permission, your assistant can use Ikuna’s normal workspace actions.

List saved Ikunas
Start or stop an Ikuna
Save where you are now
Create an Ikuna
Open an Ikuna for editing
Show the Focus Intelligence dashboard

Actions that can rearrange windows, close or hide apps, or overwrite saved state require the right permission and a clear confirmation. Read access does not automatically grant control.

Local by default. Permissioned by you.

MCP is off until you set it up.
You grant access per client.
Activity read access, sensitive context, and workspace control are separate permissions.
Window titles, URLs, and folders have separate disclosure controls.
Requests appear in Ikuna’s local access history.
Ikuna does not send prompts or activity history to a model provider on its own.

Your chosen AI client and model provider have their own privacy terms. Ikuna controls the data it makes available through the connection.

Connect in three steps

Open AI Connections

In Ikuna, open Settings, then AI Connections.

Choose a client

Choose a supported client, or copy the standard configuration for another compatible MCP host.

Verify with a real request

Restart the client if needed, then ask a normal Ikuna question. A real request creates live verification.

Connection states say what is true

Setup saved: Ikuna found its configuration entry.
Client detected: the client and readable configuration were found.
Live verified: that client reached this Ikuna helper through a real request.
Needs repair: the saved setup is stale, invalid, or cannot reach Ikuna.

One Ikuna, not another product to manage

MCP ships inside Ikuna. It has its own page because it opens a different way to use the app, but your workspaces and Focus Intelligence stay in one product.

It is included with Ikuna Pro at €9/month or €70/year. The free plan still includes up to 4 Ikunas, full-context switching, and the basic dashboard.

Download Ikuna See Focus Intelligence

FAQ

What is MCP?

MCP is a standard that lets compatible AI clients connect to tools and data sources. Ikuna uses it to expose specific focus-intelligence and workspace capabilities from the Mac app, within the access you grant.

Does Ikuna send my activity to Claude or OpenAI automatically?

No. Enabling MCP does not transmit activity by itself. Data is returned when a connected client makes a request that fits its permission scopes.

Can the assistant change my workspaces?

Only if you grant workspace-control permission. Read access alone cannot change a workspace.

Can it read window titles and browser URLs?

Only if the shipped build captured them and you separately allow that sensitive-context scope.

What happens when Ikuna does not have enough data?

It reports limited coverage or not enough evidence. Observed facts and model interpretation stay separate.