Installation

hackÜ exposes an MCP server at https://mcp.hacku.com. Connecting it 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 connector 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.

You add it by hand, not from a directory

hackÜ is not published in the ChatGPT directory, so searching for it by name will not find it. You add it by pasting the server address, which is what the steps below describe. When that changes, this page changes.

Connecting it

ChatGPT

You need developer mode, which is what allows adding an MCP server by address. It is available on the Pro, Plus, Business, Enterprise and Edu plans, on the web only. On Business and Enterprise your administrator may have to enable it for the whole workspace first.

1. Open Settings → Security and login and turn on Developer mode.

2. Go to Plugins and press the + button to create a developer-mode app.

3. Paste the server address:

   https://mcp.hacku.com

4. Choose OAuth as the authentication method. There is no key to paste: the server negotiates it on its own.

5. The hackÜ authorisation screen opens. If you are not signed in, it will ask you there — never in the chat.

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

7. Press Authorise. The app lands in Drafts, where you can toggle tools on and off and refresh the list if the server changes.

In the chat you reach it through the composer’s Developer mode tool. To call it, name it at the start of the message:

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

Codex

From the terminal, with the Codex CLI:

1. Register the server:

   codex mcp add hacku --url https://mcp.hacku.com

2. Authenticate:

   codex mcp login hacku --oauth-client-registration dcr

   dcr is dynamic client registration: Codex registers itself with hackÜ, so there is no client_id to request or paste.

3. Codex prints an authorisation URL. Open it, sign in to hackÜ, pick your company on the consent screen and authorise.

4. The token comes back through the callback and is stored by the client. Do not paste it into the chat.

To confirm it registered:

codex mcp list

If you want to narrow the scope from the start, ask for the permissions you need and nothing else:

codex mcp login hacku --oauth-client-registration dcr \
  --scopes users:read,courses:read,communications:read,learning:read

That leaves out names and emails (users:pii) and requesting reports (reports:generate). See Permissions.

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 return to Claude with the connector active.

About personal data

Claude is made by Anthropic. If your organisation has data processing agreements covering some providers and not others, check which one applies before authorising the names and emails permission. The permission is optional: without it the connector works just the same and people appear 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 it or that it has no access, see Troubleshooting.

If you administer several companies

When you authorise, every company you administer is listed and ticked. Untick the ones you do not want the assistant to read, and authorise once.

From then on you move between them in the same conversation, without signing in or authorising again:

@hackÜ how many people do we have in Éxito 2?
@hackÜ and in Éxito 3?

Every answer is about one company: the server never blends two. If your question does not make clear which one you mean, the assistant will ask rather than choose.

To add a company you did not tick, authorise again and tick it.

Removing access

You can revoke the authorisation at any time from your client’s settings, by deleting the app or the connector. In Codex:

codex mcp logout hacku
codex mcp remove hacku

Access also cuts off on its own if you stop administering that company in hackÜ: nobody has to remember to revoke it when someone changes role.

Environments

Besides the production server there is a QA one, pointing at the test environment. You add it the same way, with its own address, so the two can coexist without being confused — in Codex, under a different name:

codex mcp add hacku-qa --url https://mcp.qa.hacku.com

The data QA returns is not production data and is not good for making decisions.

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