Toolport

Toolport

Toolport

A landing page and docs for an MCP server that lets you ask your issue tracker questions in plain language.

Landed

· Developer tool

· 2024

· Product

Toolport project cover: docs and landing page

The brief

Toolport connects AI coding clients (Claude Code, Codex, Cursor) to your issue tracker through MCP, so you can ask “what’s blocking the release?” and get an answer from real tickets. Developers decide in about thirty seconds whether a tool is worth installing. The first version of the site buried the install command under three screens of marketing.

Dev’s brief was short: “What it does, how to install it in my client, what it can touch. In that order.”

What I did

Three legs, in the order we flew them.

Weeks 1–2

Ask in plain language

The hero shows a real exchange: a question, the tool calls Toolport made, and the answer. A copy-ready install prompt sits beside it, with a tab for each client, so the install is one click from the first screen.

Toolport: Ask in plain language

Weeks 1–2

Ask in plain language

The hero shows a real exchange: a question, the tool calls Toolport made, and the answer. A copy-ready install prompt sits beside it, with a tab for each client, so the install is one click from the first screen.

Toolport: Ask in plain language

Weeks 3–4

One guide per client

Each client got its own install guide: the exact config, where the file lives, and how to check it worked. Margin notes explain the parts people usually get wrong, instead of a FAQ at the bottom.

Toolport: One guide per client

Weeks 3–4

One guide per client

Each client got its own install guide: the exact config, where the file lives, and how to check it worked. Margin notes explain the parts people usually get wrong, instead of a FAQ at the bottom.

Toolport: One guide per client

Weeks 5–6

Docs and permissions

One long docs page with a sticky table of contents: quickstart, tool reference, permissions, self-hosting and troubleshooting. The consent screen states in plain words what Toolport can read and what it can never write.

Toolport: Docs and permissions

Weeks 5–6

Docs and permissions

One long docs page with a sticky table of contents: quickstart, tool reference, permissions, self-hosting and troubleshooting. The consent screen states in plain words what Toolport can read and what it can never write.

Toolport: Docs and permissions

Outcome

Time from landing on the site to a first successful tool call dropped to under three minutes in testing. Developer advocates now link straight to the client guides from support threads.

Past results, not a promise.

After launchPast results
Minutes to first tool callmedian, in testing
Fewer install questionsin support, month one

“Mika moved the install command to the top and cut everything that didn't help someone get running. Our docs went from a thing we apologized for to a thing people share.”

Dev Kapoor

Dev Kapoor

Founder, Toolport

Up next

Winrate project cover: brand, site and ad system

Up next

Winrate project cover: brand, site and ad system

Book a seat for March

Two seats left this season. Fill in the pass, tear off the stub, and I’ll reply within two working days.

Boarding pass

MV 027 · RTM → You

Destination

Class

Thanks, I'll reply within two working days.

Gate · Seat

A reply from me within two working days. No sales calls.

Boarding pass

MV 027 · RTM → You

Destination

Class

Thanks, I'll reply within two working days.

Gate · Seat

A reply from me within two working days. No sales calls.

Create a free website with Framer, the website builder loved by startups, designers and agencies.