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, 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.
Claude
- In claude.ai or the Claude desktop app, open Settings → Connectors and choose Add custom connector.
- Name it Helikonaand paste the address above. Custom connectors are available on Claude’s paid plans.
- Approve the sign-in and consent screen when they appear.
- Using Claude Code instead? Run
claude mcp add --transport http helikona https://client.helikona.com/api/mcp
ChatGPT & Codex
- In ChatGPT, open Settings → Apps & Connectors and turn on Developer mode(under Advanced) if you haven’t already — OpenAI gates custom connectors behind it on most plans.
- Choose Create, name it Helikona, paste the address above as the MCP server URL, and select OAuth for authentication.
- Approve the sign-in and consent screen when they appear.
- In a conversation, enable the Helikona connector from the tools menu when you want ChatGPT to use it.
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.
Gemini
Google’s consumer Gemini app doesn’t yet take custom connectors, but the Gemini CLI does. Add this to ~/.gemini/settings.json:
{
"mcpServers": {
"helikona": {
"httpUrl": "https://client.helikona.com/api/mcp"
}
}
}Then run /mcp auth helikona inside the CLI to complete sign-in and consent.
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:
- Read your briefs (including past versions)
- Read your quotes (including pricing and past versions)
- Read comments on briefs and quotes
- Add and resolve comments
- Accept or reject issued quotes on your behalf
- Read your change requests and issues
- Raise, comment on, and reopen change requests and issues
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. And some things are never available to any assistant: it cannot pay an invoice, upload files, or author documents. Payment always happens with you, in person, 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
- “Summarise the latest Helikona brief for my exec team — five bullet points.”
- “What changed between version 1 and version 2 of our brief?”
- “Walk me through the current quote line by line. Is GST included in the total?”
- “Here are my notes — leave a comment on each section of the brief with my reactions.”
- “Are there unresolved comments waiting on us? Summarise who said what.”
- “Raise a change request against the latest brief asking for a shorter timeline.”
- “Every Monday, check the Helikona portal and give me a one-paragraph status update.”
Questions, or using an assistant we haven’t covered? Raise a request or email us — we’re happy to walk it through with you.