When the account connector and a folder connection are both attached

In one line. Claude Code attaches your claude.ai account connector separately from the AiAkiv in the folder's .mcp.json, so one conversation can have two AiAkiv connections. Don't turn the account connector off. Turning it off removes AiAkiv from claude.ai on the web and from the mobile app too. Leave both attached and the AI saves through the folder connection first. That isn't enforced, though, so check where the save went afterwards. If saves must go to the folder only, turn Main off for a while in the AiAkiv console. While it's off, the account connector refuses requests and only the folder connection works. It refuses on your phone and the web too, so turn it back on when you use it there.

What a folder connection (folder binding) is lives in Folder binding, and the steps for using one in Desktop live in Claude Desktop. This page covers where saves go when both connections are attached, and how to check.

What happens

The account connector is the AiAkiv you registered on your claude.ai account. It saves by following your account's Main. The address to enter when you add the connector is https://mcp.aiakiv.com/mcp. This connection shows the memory tools and the card tool. Account management happens outside the conversation (Account management is in the web console or the CLI).

Claude Code (the terminal CLI from version 2.1.46, and Claude Desktop's </> Code) attaches this account connector to the session separately from the AiAkiv in the folder's .mcp.json. That leaves two AiAkiv connections in one conversation.

AiAkiv from the folder's .mcp.json  ──>  saves to the folder project
AiAkiv from the account connector   ──>  saves to Main

The two have identical tool names. The AI picks which one to save through, and depending on its pick, the save lands in the folder project or in Main.

This overlap happens even when the folder connection is approved. Approval decides whether the folder connection attaches at all (Claude Desktop §4); the account connector attaching alongside it is a separate matter.

Leave it on

⚠ Turning AiAkiv off under Claude Desktop's + menu → Connectors turns it off for your whole account. Not just that Desktop session: AiAkiv disappears from claude.ai web chat and from the mobile app too. The account connector is one setting attached to your account.

So turning the account connector off is not the fix. Anyone who uses AiAkiv on the web or on mobile loses it there entirely. Treat having both connections attached as normal, and check where each save went as described below.

If saves must only ever go to the folder project, there are two ways that leave your Claude account settings alone.

• Turn Main off for a while in the AiAkiv console. The account connector stays attached but refuses requests, and only the folder connection works. This works in Desktop too → Turning Main off for a while.
• Block that one folder in the terminal CLI. The account connector drops out only in terminal sessions in that folder → Blocking one folder only.

The AI saves through the folder connection first

When it connects, the AiAkiv server gives the AI these instructions.

• With two or more AiAkiv connections in one conversation, save through the one whose save-target check (get_save_target) reports binding as folder or api-key.
• A save through a connection whose binding is main lands in the account's Main project.
• Tell the user once that two connections are attached and which project the save went to.

In practice both Claude and ChatGPT mostly save through the folder connection. But it isn't enforced. The server only gives instructions, and now and then the AI may use the other one. So the final check is yours.

Account management is in the web console or the CLI

Account management such as teams, projects and switching Main is not done with the tools of either connection. Do it yourself in the web console, or ask an AI that has a shell, such as Claude Code and </> Code. The AI runs npx aiakiv console in the terminal, so even with two AiAkiv connections in one conversation there is nothing to choose between (The AiAkiv CLI). The app action tool that used to do this inside the conversation was removed from every connection → The app action tool is gone.

Checking where a save went

Every save response carries its destination (active_target: team, project, binding). Look at the project name the AI reports after it saves, or just ask.

where did that just get saved?

Two things to look at.

• Check that binding is "folder". If you attached with an API key it shows "api-key". Either means it saved through the folder side.
• Check that the project name doesn't carry (Main). If it does, it saved through the account connector and went to Main.

Asking before you save isn't enough. "Where are you saving right now?" makes the AI call get_save_target, and with two connections it answers folder or main depending on which connection it asked. That answer doesn't decide which connection the next save goes through. The destination after an actual save is the reliable evidence.

Every value binding can take, and what each means, is in Confirming it attached in Folder binding.

When a save lands in Main

1. Ask the AI to save it again through the folder connection.

   save what you just saved again through the folder connection (the one whose binding is folder)
   

2. After saving again, check the destination once more (the section above).

3. If needed, retire the copy that landed in Main to take it out of recall. Retiring isn't deleting and is hard to undo, so finish step 2's check first. What retiring does and doesn't do is in Correcting a save afterwards: edit and retire in Saving.

Turning Main off for a while

Checking after each save and saving again is usually enough, but sometimes you want saves never to slip into Main at all. For that, turn Main off in the AiAkiv console. While it's off, the account connector's side takes no requests, so even with both connections attached only the folder connection works.

This suits someone who uses only folder connections on a PC and only Main (the account connector) on a phone. Turn Main off while you work on the PC and saves can't slip into Main through the account connector. Turn it back on when you use your phone.

It isn't the same as turning AiAkiv off under Claude's + menu → Connectors. The account connector stays attached in Claude; the AiAkiv server simply refuses requests from connections that follow Main, and says why and where to turn it back on.

Where to turn it off and on

In the console (app.aiakiv.com), open Projects → Project management (https://app.aiakiv.com/app/?view=project.manage) and press "Turn Main off". To turn it back on, press "Turn Main on" on the same screen. The card of the Main you turned off also shows "Turn Main on" as its button.

While it's off, the console's top bar shows a "Main off" notice. On mobile (screen width 760px or less) it appears as a one-line banner just below the top bar. Clicking the notice or the banner only takes you to Project management; it doesn't turn Main on, so press "Turn Main on" there.

You can also leave turning it off and on to the AI → Letting the AI turn it off and on.

What stops while it's off

• It refuses on your phone and the web too. What you turn off is your account's one Main, so it applies on every device. To use AiAkiv on your phone, turn it on first.
• When it refuses, the AI passes the server's message on to you as written. The message starts with Main is turned off for this account, tells the AI that if this conversation has another AiAkiv connection pinned to a folder or an API key, it should use that one, and includes a link to turn Main back on in the console. The message does not tell the AI how to turn Main on by itself, so that an AI trying to get a refused request through does not turn back on a Main you turned off.

When you turn it back on

• The Main you had just before turning it off comes back unchanged. You don't pick the project again.
• If that Main was a timed switch, its expiry moves later by as long as Main was off.
• Pressing "Switch to main" on another project in the console moves Main to that project and turns it on. So does switching through a switch link (switch_url). Opening the link alone changes nothing, though: the switch happens, and Main turns on, only when you press the button on the page it opens.

Letting the AI turn it off and on

By default a person turns Main off and on, in the console. To leave it to the AI, turn on "Turn Main off" and "Turn Main back on" in the console's Reference → AI permissions. Both start off, and each is turned on and off on its own. The AI turns Main off and on with npx aiakiv console in a shell, so you can leave this only to an AI that has a shell (Claude Code, </> Code and so on).

• You can split the two. With only "Turn Main off" on, the AI can turn Main off but not back on; turning it on stays with you, in the console. If you keep Main off on purpose, leave "Turn Main back on" off.
• The CLI uses keys that do not follow Main, so it can turn Main on while Main is off. Claude on your phone has no shell, so on your phone you turn it on with the console's "Turn Main on" button.
• When Main goes off, the account connector in that conversation is refused too, from its next request. The folder connection keeps working.
• Even with the save target switch permission (target:switch) on, the AI can't change or clear Main while it's off, and that permission can't turn Main on either. To turn it on, have the AI do it under "Turn Main back on", or turn it on yourself in the console.

More in Asking your AI to do console work.

Worth knowing

• Leaving the team, that team being deleted, or clearing Main removes the Main setting itself. The off state goes with it.
• Turning Main off and on, including when the AI did it, is recorded in your own save-target switch history.

Blocking one folder only: per-folder blocking in the terminal CLI

Turning Main off makes AiAkiv refuse on your phone and the web too. To leave those alone and drop the account connector in one folder only, put the following in that folder's .claude/settings.local.json in the terminal CLI (Claude Code).

{
  "deniedMcpServers": [{ "serverName": "claude.ai AiAkiv" }]
}

• It doesn't touch your account settings. The account connector drops out only in terminal sessions opened in that folder. Other folders, Desktop, web chat, and the mobile app stay as they are.

• Each entry is an object, not a string. Write it in the { "serverName": "..." } shape.

• If the same file already has approval settings (enabledMcpjsonServers, enableAllProjectMcpServers), write it inside the same braces. A second pair of braces breaks the file.

  {
    "enabledMcpjsonServers": ["AiAkiv-myproject"],
    "deniedMcpServers": [{ "serverName": "claude.ai AiAkiv" }]
  }
  

  The approval side (enabledMcpjsonServers) is an array of name strings; the blocking side (deniedMcpServers) is an array of objects. The shapes differ, which makes them easy to mix up. On the approval side, write the name exactly as the folder server is named in .mcp.json (AiAkiv-<project name>, e.g. AiAkiv-myproject).

Afterwards, check that only one AiAkiv (the folder one) is left in the /mcp list, and ask for the save target to confirm binding is folder (or api-key). It isn't certain when the setting reaches a conversation that's already open, so open a new conversation to check.

Desktop has no per-folder block

• The terminal setting above (deniedMcpServers) doesn't reach Desktop.
• Desktop's + menu → Connectors isn't a per-folder setting; it's an account-wide one.

So in Desktop, keep both connections and check where each save went. If a piece of work must only ever save to the folder project, turn Main off in the AiAkiv console. That isn't a Claude setting, so it works in Desktop too → Turning Main off for a while. If you can't have AiAkiv stop on your phone and the web as well, do that work in the terminal CLI with the per-folder block above.

Not recommended

Both of these turn off more than AiAkiv in this folder. Know what goes off before you use them.

• Turning AiAkiv off under Desktop's + menu → Connectors. It goes off for your whole account: AiAkiv disappears from claude.ai web chat and the mobile app too.
• Turning off every account connector in the terminal. The environment variable ENABLE_CLAUDEAI_MCP_SERVERS=false or the setting "disableClaudeAiConnectors": true turns off every other account connector too, not just AiAkiv. To block one folder, the per-folder block above is the better choice.

If the goal is to send saves to the folder only, use Turning Main off for a while above. You turn it off and on in the AiAkiv console, and Claude's connector settings stay as they are.

The ChatGPT apps

ChatGPT and ChatGPT classic work differently. You keep the account-wide connection (the plugin install) and register the folder connection under a different name to tell the two apart → Connecting ChatGPT. The server's instruction to save through the folder connection first, and the after-save check, apply in ChatGPT too.

In Claude, the AI can still use the account connector even with different names. So in Claude, checking where each save went matters more than splitting names.

Common problems

• I turned AiAkiv off under Connectors and it disappeared on the web and mobile too. That switch is account-wide. Turn it back on in the same + menu → Connectors.
• A save went to Main. The AI used the account connector. Save it again and check, per When a save lands in Main above.
• Before saving it said folder, but the save went to Main. The save-target check answers for the connection you asked. With two connections, the before-save answer isn't enough; look at the destination after the save.
• I added the terminal setting but Desktop still shows two. deniedMcpServers doesn't reach Desktop. In Desktop, work with both attached and check where each save went. If saves must go to the folder only, turn Main off in the console.
• I added the setting but nothing is blocked. Check two things. That you didn't write the entry as a string ("claude.ai AiAkiv"): it must be an object ({ "serverName": "claude.ai AiAkiv" }). And that the server name exactly matches the account connector's name in the /mcp list (claude.ai AiAkiv).
• There's only one AiAkiv in the folder and saves always go to Main. The folder connection wasn't approved, so it was skipped and only the account connector is left. An unapproved folder connection drops out with no error. Approve it per §4 of Claude Desktop. If you've also added the terminal's per-folder block, you'll see no AiAkiv at all in that case.
• The AI refuses to save or search, saying Main is turned off. Main is turned off in the console. If this conversation also has a folder connection, tell the AI to use that one. If you meant to use AiAkiv where only the account connector is attached, such as your phone or the web, press "Turn Main on" in the console's Project management. If "Turn Main back on" is on in AI permissions, you can also ask an AI that has a shell to turn it on → Turning Main off for a while.
• Main is off and every request is refused even in the folder. The folder connection wasn't approved, so only the account connector is left, and it follows Main, so it refuses. Approve the folder connection per §4 of Claude Desktop.

Related

• Using a folder connection in Desktop, and approving in advance → Claude Desktop
• What a folder connection is, and what the binding values mean → Folder binding
• Correcting and retiring a wrong save → Saving
• What Main is and who changes it → Teams and projects
• The console's project management screen → Console
• Running two connections side by side in ChatGPT and ChatGPT classic → Connecting ChatGPT
• OAuth and API keys → Authentication