01 — Connect · Your agent in n8n

What you'll be able to do

Explain the MCP access: one endpoint, your Token, a catalog of Tools.
Build a first connection from n8n — and fix the two most common errors yourself.

You already steer — now you build

From the Agentowner course you know the rule: your KI-Agent acts in your name, and nothing becomes real before you approve it. So far the agent has been finished software to you. In this course you build it yourself — out of n8n building blocks. For that, today we look at the exact spot where every agent touches the platform: the MCP access.

Core idea

The Token you created in the Agentowner course is exactly what your agent identifies itself with at this access point. There is no second secret and no hidden machinery: whoever holds the Token acts as your agent — inside your limits. That's why it stays as secret as a password, in n8n too.

Before you start

You've done the Agentowner course: an agent exists, and its Token is stored safely with you.
A running n8n — in the cloud or self-hosted. Verified with n8n 2.4.5; you need a version that offers the HTTP Streamable transport.
For the next lesson: access to a chat model with tool support (this course demonstrates with Anthropic Claude).

Note for Safari & local n8n

If you run n8n locally and use Safari, n8n blocks the sign-in with a message about a "secure cookie". That's an n8n security setting: start n8n with the environment variable N8N_SECURE_COOKIE=false — or use n8n Cloud, where this doesn't occur.

What is the MCP access?

MCP (Model Context Protocol) is the standardized access an AI agent uses to talk to LinkYourSkill. Three things are enough to understand it:

One endpoint: https://app.linkyourskill.ai/mcp — an address that accepts requests via POST.
Your Token: it is sent along with every request as a "Bearer Token" — that's how your agent identifies itself.
Tools: the access offers a catalog of Tools — individual capabilities like search_skillanbieter. Which of them your agent may use is your decision, later.

The first connection — without AI

Before any chat model enters the picture, you prove the line is live. In n8n:

Create a new workflow and add the HTTP Request node.
Set Method to POST — the default is GET, and GET won't work here.
As the URL, enter: https://app.linkyourskill.ai/mcp
Enable Send Headers and set the header Accept to application/json, text/event-stream.
Enable Send Body, choose "JSON" as the Body Content Type, and enter: {"jsonrpc":"2.0","method":"tools/list","id":1}
Execute the node — deliberately without signing in yet. You get an error: "Authorization failed - please check your credentials". Good: the platform doesn't know you yet.
Now the Token: set Authentication to Generic Credential Type → Bearer Auth, create a new credential, and paste your Token into the Bearer Token field.
Execute the node again. The response starts with event: message — and inside it is the complete tool catalog.

Looks raw — but it's right

n8n shows the response as one long text starting with event: message. That's the MCP access's streaming format, not an error. What matters is what's inside: "tools":[ followed by the Tool list. If you spot search_skillanbieter and prepare_order, your line is officially in business.

If it doesn't work

"Method not allowed. Use POST for stateless MCP." — Method is still set to GET. Redo step 2.
"Authorization failed - please check your credentials" — the Token is missing or wrong. Check the Bearer Auth credential; if in doubt, simply create a new Token for your agent.
Just to experiment without your own Token: the platform's API docs offer a public demo key that can only read.

Your turn

Test yourself — retrieving from memory is what builds real retention.

Knowledge check

What does your agent identify itself with at the MCP access?