Skip to content

Connect ChatGPT, Codex, or Claude

The exact UI differs between clients, but the safety contract is the same.

Connection values

MCP server: https://mcp.heyaira.eu/mcp
Transport: Streamable HTTP
Authentication: OAuth 2.1 Authorization Code + PKCE
Resource: https://mcp.heyaira.eu/mcp

Listing values

When a client asks for a name, description, icon, or website for the connector, use the approved values so HeyAira reads the same everywhere:

Name: HeyAira
Description: Keep your project's decisions, tasks and handoffs across the AI tools you choose.
Website: https://heyaira.eu
Icon: HeyAira-AppIcon-Light-1024x1024.png (official single blue dot)

Always write the name as one word, HeyAira. Developer, category, and website fields are stored by the client, not by the MCP server, so update them in the client's connector or app settings.

Do not paste a token into a repository, prompt, screenshot, or shared note. Complete OAuth consent in the client. A client connection represents an OAuth grant; repeated reconnects can leave stale grants that require revocation.

Verify before writing

Run a read-only check first:

  1. server_identity
  2. continuity_context
  3. compare the returned project and resource with the operator-selected connection profile
  4. only then allow a mutation

If the client exposes an old tool schema, reconnect it before attempting a write. In particular, current write tools require write_context; do not try to bypass this requirement.

Client-specific notes

Use the client’s connector or MCP settings to reconnect. The server cannot repair a stale OAuth grant stored by a client. If multiple entries for HeyAira appear, keep the working grant for the intended project and remove stale entries only after checking their target.

What success looks like

A successful connection can discover the current tools and complete both read-only calls. A successful connection is not proof that a write is safe until the returned identity matches the selected project and instance.