Giving them to agents
An installed server or skill reaches an agent through a card on the canvas. Add one from the add menu — MCP server or Skill — and choose what it stands for: Browse opens the catalog, or pick one you already installed right on the card.
Connect with an arrow
Draw an arrow between the card and an agent. That’s all:
- The agent gets the server’s tools, or the skill — and no other agent does.
- One card can connect to several agents; one agent can have several cards.
- Delete the arrow and the agent loses it again.
Each card lists the agents it is given to, and what that means for each:
The agent reads its tools when it starts: restart it to pick up a new arrow. Codex CLI and Qwen Code work this way.
Click an agent’s name on the card to fly to it.
The MCP server card
- Header: the server’s name, how many tools it has, and a dot — running, idle (it starts on the first call), starting, failed, or waiting for sign-in.
- Tools: every tool the server offers. The one an agent called last is highlighted, and the card says “by Designer” for a moment.
- Problems in place: “The server did not start” with the last line of its log and Try again; “needs you to sign in” with a Sign in button.
- Settings opens it in the catalog; Change server points the card at another one.
The Skill card
- The skill’s name, where it comes from, its files and whether it has scripts, and its description — the “when to use it” line the agent sees.
- Who loaded it last and how many times.
- Expand the card to read the whole
SKILL.md. - Details opens it in the catalog (update, open folder, uninstall); Change skill points the card at another one.
Zoomed out, the cards become tiles that show the server’s tool count and agents, or the skill’s name.
An agent loads a matching skill before starting the task, on its own — its skill_load tool
lists every connected skill with when to use it. If you want a particular skill used anyway, just
say so: “use the brainstorming skill”.