Loading Helikona…
Helikona

Your engagement

Connect your AI assistant

If you use Claude, ChatGPT, Gemini, or another AI assistant, you can connect it directly to your Helikona engagement. It can then read your briefs and quotes, answer questions about them with the actual documents as evidence, leave comments for us, raise change requests or issues, draft a new brief with you, and — if you allow it — accept or reject quotes on your behalf.

The address

We speak the Model Context Protocol (MCP), the open standard the major assistants use to reach outside tools. Wherever your assistant asks for a connector or MCP server address, give it:

https://client.helikona.com/api/mcp

The first time it connects, your browser will open our sign-in — use the same email your engagement is set up under — and then a consent screen where you choose exactly what the assistant may do.

Drafting a brief

A brief is where an engagement succeeds or fails, and a one-line request makes us guess at the audience, the outcome and the boundaries. So alongside the connector we publish a brief-drafting skill: it picks the template that matches the work — advisory, training, an app or prototype, a presentation, a workshop, emceeing, a video, or writing — then works through it with you section by section and lodges the result in your portal as a draft. Nothing reaches us until you issue it.

The skill is optional. The connector works on its own, and the templates are useful even if you write the brief yourself.

Either way, ask your assistant something like “draft a brief for a video we need” and it will take it from there.

Claude

The plugin is the route we recommend — nothing to paste, and you get the brief-drafting skill with it:

  1. Download the plugin file and open it with Claude.
  2. Approve the install, then the sign-in and consent screen.

Custom connectors are available on Claude’s paid plans, either way. If you would rather add the connector on its own and skip the skill, open Settings → Connectors in claude.ai or the Claude desktop app, choose Add custom connector, name it Helikona, and paste the address above. Using Claude Code instead? Run claude mcp add --transport http helikona https://client.helikona.com/api/mcp

ChatGPT & Codex

OpenAI installs plugins only from its own directory, so there is no single file to open here as there is for Claude. It comes in two pieces instead. Start with the skill — it needs nothing switched on:

  1. Download the skill.
  2. In ChatGPT, open Plugins in the sidebar, go to the Skills tab, and choose Create → Upload from your computer. If there is no Skills tab, your plan doesn’t include them yet.

That alone gets you the interview and a finished brief. The connector on top lets ChatGPT lodge it for you and read your quotes and requests — how you get it depends on your plan.

A work account (Business, Enterprise or Edu) — you probably have nothing to do. An administrator publishes us once for the whole workspace, and we then appear in everyone’s app list marked custom, with no developer mode to turn on. It is also the only plan family where an assistant may lodge anything. What your administrator needs:

A personal paid plan — you add it yourself, which means turning on Developer mode in Settings first. The connection is read-only there, so the skill hands you the finished brief to paste into a new brief rather than lodging it. If that is more fiddling than you want, the skill on its own is the better trade.

Using Codex, OpenAI’s coding agent? Run codex mcp add helikona --url https://client.helikona.com/api/mcp and then codex mcp login helikona to complete sign-in and consent. For the skill, unzip the download into ~/.agents/skills/.

Google

Google splits this across three products, so the path depends on which one you use.

Antigravity or the Gemini CLI — the route we recommend, because the plugin file above installs as an extension and brings the brief-drafting skill with it: gemini extensions install <path>, or agy plugin import for Antigravity. To wire up the connector by hand instead, add "helikona": { "httpUrl": "https://client.helikona.com/api/mcp" } under mcpServers in your settings file, then run /mcp auth helikona.

Gemini Enterprise (a work or school Google account) — an administrator registers us once for the whole organisation, in the Gemini Enterprise admin console under custom MCP servers. Worth passing them this list:

The Gemini app on a personal Google account — open Connected apps and add a custom app by MCP server URL, using the address above. Google currently limits this to personal accounts in the United States.

Something else

Any agent that speaks MCP over Streamable HTTP with OAuth can connect — we support automatic client registration, so there’s nothing to pre-arrange with us. If your tool only handles local (stdio) servers, the standard bridge works: npx mcp-remote https://client.helikona.com/api/mcp

What you’re agreeing to

The consent screen lists each permission with its own tick-box — untick anything you’d rather keep manual:

The assistant sees only what your own sign-in can see — your organisation’s engagement, nothing else. It receives its own credentials; your password and sign-in stay private.

Two things are never available to any assistant: it cannot pay an invoice and it cannot upload files. Payment always happens with you, in person, in Helikona. And briefs are the one document an assistant can author — but only ever as a draft, so issuing stays a decision you make here in the portal.

Switching it off

Remove the connector in your assistant’s settings at any time. Access also lapses on its own after 30 days of inactivity. If a device is lost or something behaves oddly, email admin@helikona.com and we’ll cut every connection on your account immediately — you can reconnect fresh whenever you like.

Ideas to try

Questions, or using an assistant we haven’t covered? Raise a request or email us — we’re happy to walk it through with you.