Zed is a fast editor with built-in agent support. It speaks MCP, which means you can give it a shorten_url tool the same way you give Cursor, Windsurf, or Claude Code one.
If you work in Zed, here is how to get KooLink into your editor.
Add KooLink to Zed
Zed reads MCP servers from its config. Add this block:
{
"mcpServers": {
"koolink": {
"url": "https://mcp.kool.ink",
"type": "streamable-http"
}
}
}
Reload the MCP servers. KooLink is loaded. The agent now has a shorten_url tool.
No API key to mint, no account to create, no free-tier cap. Free and unlimited.
What it looks like in practice
In a Zed session, wherever you are working:
Shorten the deploy URL for the commit message. Give me a clean kool.ink link for this README badge.
The agent calls shorten_url and hands you back a kool.ink/xyz link. You stay in the editor, in the same context.
Why an MCP server fits Zed
Zed is built to be fast and to keep you in the editor. A browser tab is the opposite of that. A tool the agent already has keeps the flow.
- Latency. A
shorten_urlcall is under a second. - Consistency. The same tool produces the same
kool.ink/xyzslug shape every time. - No state. No API key to rotate, no config drift between projects.
Where else it works
- Cursor, Windsurf — IDE agents
- VS Code with Continue — extension
- Claude Desktop / Claude Code — desktop agent
- Any MCP client that supports streamable-http transport
And in your terminal:
npx @koolink/koolink https://example.com/very/long/path
# → https://kool.ink/xyz
Bottom line
Zed is MCP-native, and KooLink is the only widely-used shortener that ships a hosted MCP server. One config block and your editor can shorten a URL like any other tool.