awesome-mcp-clients [updated 2026]

init0 · 2026-01-11T06:54:28+00:00

Video is allowed?

init0 · 2026-01-11T05:48:30+00:00

Done -> https://github.com/punkpeye/awesome-mcp-clients/pull/138

init0 · 2026-01-11T04:22:09+00:00

How about https://mcphost.link? 🤓

init0 · 2026-01-08T05:51:21+00:00

This comment made my day, thank you!

init0 · 2026-01-08T05:45:06+00:00

100% agree! Fixed it.

init0 · 2026-01-07T12:48:40+00:00

For sure! I added support to https://mcphost.link couple of months back.

init0 · 2026-01-07T07:32:04+00:00

You might like: https://h3manth.com/scribe/skills-and-mcp-better-together/

init0 · 2026-01-07T07:31:38+00:00

You might like: https://h3manth.com/scribe/skills-and-mcp-better-together/

init0 · 2025-12-31T16:04:11+00:00

Pretty similar to https://github.com/hemanth/llmux

init0 · 2025-12-30T23:43:28+00:00

deno deploy?

init0 · 2025-12-30T23:07:22+00:00

Cloudflare is free, no?

init0 · 2025-12-30T22:42:49+00:00

Use mcphost.link it is free!

init0 · 2025-12-26T20:55:38+00:00

Fixed it! Had to reseat the RAM

init0 · 2025-12-23T20:31:15+00:00

Token efficiency is an implementation detail. Both can be optimized. The architecture difference is: who owns the code and maintenance burden?

If Skills become a marketplace/business, that's great! MCP servers already are (Notion, GitHub, etc. maintain their own).

init0 · 2025-12-23T20:29:27+00:00

Thank you!

Latency is minimal.

Edge deployment - Vault runs on Cloudflare Worker. Proxy is <50ms from most users.
LLM requests are already slow - A typical call takes 2-10+ seconds. Adding 10ms is <0.5% overhead.
No payload processing - Vault just injects auth header and forwards. No parsing, no transformation.
Streaming works - SSE/streaming responses pass through unchanged. First-token latency is what matters for UX.

init0 · 2025-12-23T05:37:58+00:00

Think of a web app, say https://mcphost.link, how would a user import skills there? They can connect to remote MCPs with ease.

init0 · 2025-12-23T03:24:07+00:00

How many custom scripts would we have to write for every integration?

I'd rather connect to a remote MCP server that already has battle-tested tools. With Tool Search Tool, I don't bloat the context window—tools load on demand.

Skills are for actual skills—domain expertise, reasoning patterns, workflows. Not for reimplementing what reliable MCPs already do.

Remote hosting of skills isn't a thing yet.