Connect AiAkiv to your AI

Claude Web URL

Settings → Connectors → ‘+’ → Add custom connector → paste the URL above. (Pro/Max. On team/enterprise, owner only: Settings → Org settings → Connectors.)

Claude Desktop

App-wide = account (bottom-left) → Settings → Connectors → Add custom connector → paste the URL. Folder = create .mcp.json in the working folder and paste the JSON below.

File · .mcp.json

{
  "mcpServers": {
    "AiAkiv-myproject": {
      "type": "http",
      "url": "https://mcp.aiakiv.com/mcp?project=myproject",
      "headers": {
        "X-K2G-Project": "myproject"
      }
    }
  }
}

ChatGPT (플러그인) URL

① AiAkiv is listed in OpenAI's plugin directory, so install it from inside the app (no pasting URLs). Settings → Plugins → Browse directory (the sidebar Plugins item opens the same place), then search for AiAkiv Memory. ② Click the result → Install plugin → sign in with your www.aiakiv.com account. That is it; it applies account-wide, so ChatGPT classic sees it too. ③ Finally, ChatGPT enables a plugin per conversation. Under Plugins below the composer of a new chat, turn AiAkiv Memory on and call it with @AiAkiv Memory (the “Try now” button shown right after installing opens a chat with it already on). Skip this and no tools appear in a new chat. The official AiAkiv Memory plugin in the ChatGPT plugin directory does not support app features (asking the AI to do app work such as console management). Everything the console app does (creating teams and inviting people, team links, projects and personas, switching Main and turning it off and on, managing the cards you made, and so on) can also be done by hand in the web console (the dashboard, https://app.aiakiv.com). To use app features, connect in Codex (install prompt, www.aiakiv.com/docs/codex-install-prompt) or connect a folder with a project-pinned API key (the ChatGPT card under “Per-folder” below).

xAI / Grok URL

grok.com/connectors → New Connector → Custom → paste the URL above.

Antigravity API key

Agent panel ‘…’ → MCP Servers → Manage MCP Servers → View raw config → paste the JSON below into mcp_config.json. It reloads on save. (File: ~/.gemini/antigravity/mcp_config.json; on some versions ~/.gemini/config/mcp_config.json)

The remote key MUST be serverUrl. url / httpUrl / type are not recognized (strict schema). The config is app-wide (no per-folder split), so the KEY picks the project: issue a project-scoped API key in the console and put it in the Authorization header (the key pins the project, so Main does not apply).

File · mcp_config.json

{
  "mcpServers": {
    "AiAkiv": {
      "serverUrl": "https://mcp.aiakiv.com/mcp",
      "headers": {
        "Authorization": "Bearer <API-KEY>"
      }
    }
  }
}

Cursor

App-wide = Settings (Ctrl/Cmd+,) → Tools & MCP → + Add New MCP Server → set Transport to streamable-http → paste the URL. Folder = create a .cursor folder and paste the JSON into mcp.json.

File · .cursor/mcp.json

{
  "mcpServers": {
    "AiAkiv-myproject": {
      "type": "http",
      "url": "https://mcp.aiakiv.com/mcp?project=myproject",
      "headers": {
        "X-K2G-Project": "myproject"
      }
    }
  }
}

Claude Code

Create a .mcp.json file in the working folder and paste the JSON below.

File · .mcp.json

{
  "mcpServers": {
    "AiAkiv-myproject": {
      "type": "http",
      "url": "https://mcp.aiakiv.com/mcp?project=myproject",
      "headers": {
        "X-K2G-Project": "myproject"
      }
    }
  }
}

ChatGPT

Installed as a plugin (the ChatGPT (plugin) card above), the whole account follows Main. Use this method when you want a project pinned per folder. Issue a project-scoped API key in the console, copy the whole config, and paste it into config.toml. The project stays pinned no matter what your Main project is. After editing .codex/config.toml, save it and restart the app. You can use it alongside the plugin install and other folder keys. The folder side's server name is AiAkiv-<project name>, so the names don't collide (the example below is for a project called myproject; copied from the console, it carries your project's name). This connection has app features (asking the AI to do app work such as console management). For the AI to change anything in the console, check “Allow console management by AI (manage)” when you issue the key.

Sign-in (OAuth) folder binding (the ?project= address) does not take hold on this app, so it pins with the key instead. You can keep the plugin install alongside it; the folder side's server name is AiAkiv-<project name>, so you can say which one to save through.

File · .codex/config.toml

[mcp_servers.AiAkiv-myproject]
url = "https://mcp.aiakiv.com/mcp"
http_headers = { "Authorization" = "Bearer <API-KEY>" }

Gemini CLI API key

Create a .gemini folder and paste the API-key config into settings.json. Issue the key per project in the console (shown once).

Gemini CLI's login session does not persist. You must use the API-key method.

File · .gemini/settings.json

{
  "mcpServers": {
    "AiAkiv-myproject": {
      "httpUrl": "https://mcp.aiakiv.com/mcp",
      "headers": {
        "Authorization": "Bearer <API-KEY>"
      }
    }
  }
}