Connect Tulina to Hermes

Hermes is the open-source agent from Nous Research. Once it is connected to Tulina it can work in your tools, follow your processes and read your company brain, the same way Claude or ChatGPT do.

Who can do this. Anyone with a Tulina account. Hermes gets what your account can see and do, and nothing more.

How long it takes. 5 minutes.

Step 1. Add Tulina to the Hermes config

Open ~/.hermes/config.yaml and add this block. If the file already has an mcp_servers section, add tulina inside it.

mcp_servers:
  tulina:
    url: "https://mcp.tulina.ai/mcp"
    auth: oauth
    oauth:
      redirect_port: 27890

Keep the redirect_port line. Tulina accepts the sign-in on five ports only: 27890, 27891, 27892, 27893 and 27894. If 27890 is already in use on your machine, pick one of the other four.

Leave the oauth block as short as it is here. Adding client_secret, client_name or token_endpoint_auth_method makes Hermes change how it signs in, and Tulina refuses it.

Step 2. Sign in

In a terminal, outside any running Hermes chat, run:

hermes mcp login tulina

Your browser opens on the Tulina sign-in page. Sign in the way you sign in to the app.

Step 3. Reload Hermes

Back in Hermes, type:

/reload-mcp

Restarting Hermes does the same thing. Tulina's tools are now available. Ask Hermes something only your company would know to check.

Hermes on a remote machine

If Hermes runs on a server and your browser is on your laptop, the sign-in page cannot hand the result back on its own. Two ways around it:

• Paste the address back. Open the link Hermes prints, sign in, then copy the final address from your browser's address bar and paste it into the terminal where Hermes is waiting. The browser shows a connection error at that point. That is expected.
• Forward the port. From your laptop, run ssh -N -L 27890:127.0.0.1:27890 user@host before step 2, then sign in normally.

Device-code login (--flow device) does not work with Tulina.

An agent with nobody at the screen

A Hermes that runs on its own, with no one there to sign in, uses an access key instead. In the Tulina app, open Personal settings and create an access key. It is shown once, so copy it there and then. The config block becomes:

mcp_servers:
  tulina:
    url: "https://mcp.tulina.ai/mcp"
    headers:
      Authorization: "Bearer YOUR_ACCESS_KEY"

A key opens everything its account can reach, to everyone who can talk to that agent. Create an account that holds only what the job needs, and delete the key from the same page when you no longer need it.

Troubleshooting

An error mentioning invalid_redirect_uri. Hermes tried to sign in on a port Tulina does not accept. Check that redirect_port is one of 27890 to 27894, and that the oauth block holds nothing else.

An error mentioning invalid_client. Hermes kept an old registration. Delete the tulina files in ~/.hermes/mcp-tokens/, then run hermes mcp login tulina again.

The sign-in worked but Hermes shows no Tulina tools. Type /reload-mcp. If they are still missing, run hermes mcp test tulina to see what Tulina answered.

The browser never opens. Hermes prints the sign-in link in the terminal. Open it by hand.