Installation

Connecting hackÜ takes two minutes and requires nothing installed on your machine and no key from anyone. You authorise with your own hackÜ account, you pick your company, and the assistant ends up with read access to that company’s data.

You need to be staff

The plugin only works with an account that administers at least one company in hackÜ. If your account is a student account, the authorisation screen will not offer you any company. Talk to whoever administers hackÜ in your organisation.

Connecting it

ChatGPT / Codex

1. Open Plugins in the sidebar.

2. Search for hackÜ and install it.

3. A browser tab opens with the hackÜ authorisation screen. If you are not signed in, it will ask you there — never in the chat.

4. Review the permissions and pick your company in the dropdown. This is the decision that matters most: access is pinned to that company and cannot be changed without authorising again.

5. Press Authorise. You go back to ChatGPT and you can start asking.

To call it, type @hackÜ at the start of your message:

@hackÜ what is my company called and how many people do we have?

Claude

1. Open Settings → Connectors → Add custom connector.

2. Paste the server address:

   https://mcp.hacku.com

3. Claude takes you to the hackÜ authorisation screen. Sign in if you need to, pick your company and authorise.

4. You go back to Claude with the connector active.

About personal data

Claude belongs to Anthropic. If your organisation has data processing agreements that cover some providers and not others, check which one applies before authorising the names and emails permission. The permission is optional: without it the plugin works just the same, and people come back identified by their id.

Checking that it worked

Ask this:

@hackÜ what is our company called?

If it answers with your company’s name, you are set. If it says it cannot confirm that or that it has no access, see Troubleshooting.

Switching companies

If you administer more than one company and you need to query a different one, authorise the plugin again and pick the other one in the dropdown. One authorisation always points at a single company; that is what guarantees an answer never mixes data from two organisations.

Removing access

You can revoke the authorisation at any time from your client’s settings, by uninstalling the plugin or deleting the connector. Access also cuts off by itself if you stop administering that company in hackÜ: nobody has to remember to revoke it when somebody changes role.

Environments

Alongside the production plugin there is hackÜ QA, which points at the testing environment. It installs as a separate plugin, under its own name, so the two can coexist without being confused for each other. The data QA returns is not production data and must not be used to make decisions.

If your organisation works with hackÜ in a dedicated environment, ask your hackÜ contact for your server address and use the Claude tab with that address instead of the production one.