Every AI · One channel back

Your AI did the work.
Absorb it in seconds.

Downlink is the channel from your AI back to you — pages you skim, maps you explore, audio for the walk, questions that find your phone. Connect once; it just does it.

$ claude mcp add --transport http downlink https://mcp.usedownlink.com/mcp

Works with Claude Code, Codex, and any MCP-capable agent.

The asymmetry

The bandwidth into AI exploded.
The way back didn't.

You can talk to AI with your voice, screenshots, entire projects of context. It still answers you with a wall of text.

HUMAN → AI
Voice. Screenshots. Codebases. Transcripts. Meetings. Everything.
AI → HUMAN
text, one line at a time…

Everything you can express goes in. One thin stream comes back.

Downlink widens the straw.

The toolbelt

Re-encoded for the way
you actually absorb.

Downlink turns finished work into whichever format lands fastest, and hands you a link that opens anywhere — laptop or phone, now or next week.

downlink.fyi/s/…

Hosted pages

What changed, what it decided and why, before/after — a page that lets you take in an hour of work in thirty seconds, on any device.

Zoomable maps

Architectures, dependencies, how things connect — structure you grasp spatially by panning and zooming, not by parsing a nested bullet list.

Audio recaps

Narration written for listening — not a transcript read aloud. Catch up on what happened during the walk, the drive, away from the screen.

CLAUDE CODE · REFACTOR RUN · 12m ago
Two ways to handle the session migration — zero-downtime dual-write (slower) or a 5-minute maintenance window. Which do you prefer?
Dual-writeWindow is fine

Questions that find you

Your AI parks its questions in a queue that reaches you anywhere. Approve, pick, or comment from your phone — the work keeps moving.

The loop

It goes both ways.

Downlink is the channel to you. Uplink is your answer back. Everything it sends can also take input — so you stay in the loop without hovering over a terminal.

Downlink — to you

The finished work arrives as something you understand instantly: a page you skim, a map you explore, a recap you listen to. No wall of text to decode.

Uplink — back to the agent

Approve a decision, pick a fork, answer a question — right inside the artifact. Your response flows back and the agent keeps going.

Plug and play

Connect once.
It offers itself.

No prompt engineering, no setup files to maintain, nothing to remember. Your AI re-reads Downlink's tools every session and reaches for them at the right moments on its own.

Add one URL

Downlink is a remote MCP server. Point your AI at it and sign in — no code, nothing to host, nothing to maintain.

Your AI gains the toolbelt

Publish a page, publish a map, narrate, ask questions. It offers the right format at the right moment — you never have to ask.

Links arrive, answers return

Everything is a hosted link — shareable, persistent, works on your phone. Your answers flow back into the work.

Widen the channel.

More gets done when more gets through.