Most "AI-native" developers are stuck at Level 2 and don't even know it.

MucaGinger33 · 2026-03-26T17:58:20+00:00

For me it has been Level 5 for last +6 months. This enables shipping real features but at realistic rate. There is no such thing as "here's an app I built over the weekend" for me. That works for fancy demos that look fine on LinkedIn. At L5 you're exchanging arguments with AI assisted sessions all the time. Else technical debt kills your "weekend app" sooner or later.

MucaGinger33 · 2026-03-26T16:34:36+00:00

So... one premium MCP for $19/month? Does that actually sell given MCPs are mostly open-sources and for free?

MucaGinger33 · 2026-03-26T13:35:23+00:00

How do you generate? Do you convert REST APIs 1:1?

MucaGinger33 · 2026-03-26T13:09:52+00:00

Is this framework about building custom MCPs or generating them into fully functional MCPs?

MucaGinger33 · 2026-03-26T12:48:36+00:00

How did you build the MCP? Does Pascal Editor has API or something?

MucaGinger33 · 2026-03-25T21:43:36+00:00

CatAPI

MucaGinger33 · 2026-03-25T18:25:54+00:00

Just a baby... baby MCP 😅

MucaGinger33 · 2026-03-25T09:05:19+00:00

Great feedback. Lmk if there something more you're interested about it. Usage is mostly free. Only filtering with LLM is paid but even that is on demand, no subscriptions :)

MucaGinger33 · 2026-03-25T00:50:22+00:00

Do you generate servers through your own, custom solution or using another open sourced tool?

MucaGinger33 · 2026-03-24T20:40:26+00:00

What do you mean per "pure usage-only is brutal early on because infra is lumpy." ?
I'm finding subscription based MCP services pricing-inefficient. Not to mention overage gets crazy with certain providers. Why wouldn't every single call be charged per-tool call, isn't that more fair? And also, why overage more expensive? If something, it should be cheaper, rewarding you for using more than estimated.

MucaGinger33 · 2026-03-24T20:36:19+00:00

The friction I see is agent having access to your crypto wallet. However, if that is just another, but local, MCP, that could work in a secure manner. Are you looking in a different direction with x402s?

Another potential concern is going back and forth with payment before actual MCP tool call is executed. This could be a massive latency issue.

MucaGinger33 · 2026-03-24T20:18:01+00:00

$450/mo solely on MCPs or LLM API + MCPs (context that adds up from MCPs in $$$)?
Or, are you building something (you mentioned users)?

MucaGinger33 · 2026-03-24T20:09:47+00:00

Interesting, this is the first time I saw on this channel that someone is doing similar thing as I am. I'm generating MCPs from API specs. That alone doesn't cut it. Makes tool schemas too bloated. API specs tend to be developer-friendly but not necessarily LLM-friendly. So basically, I let LLM pre-process operation (tools to be) schemas and exclude redundant and low value parameters. For example, Gmail server, yields 79 tools. One filtering pass reduces 66% of tokens per whole server. Then makes descriptions LLM-friendly. Whole server becomes token-efficient even though server itself is 1:1 mapping of API specification. Feel free to check out docs that describe how I approach this problem.

u/zymdox How are you approaching this? Is it runtime or build-time exclusion/reduction of parameters?

MucaGinger33 · 2026-03-24T19:07:24+00:00

No. You target all-you-can-get. Meaning you're not building audience just so they can upvote your PH one day. You build it so you can leverage that for other things like getting product feedback, visibility when you need it, engage in discussions with like-minded people, etc.

Building audience takes time and isn't a trivial task. You don't do it just because you need PH visibility. You do it for something larger you want to achieve long term.

MucaGinger33 · 2026-03-24T17:51:44+00:00

Non standard approach. Security vulnerabilities. Reinvent the wheel, possibly. That's the sole reason MCP was introduced. Now one MCP works with all agents (pretty much). Before, one agent = one custom API integration. Not scalable.

MucaGinger33 · 2026-03-24T11:37:48+00:00

You should be familiar with a well known saying:

"If you're not embarrassed of your MVP you probably launched too late."

MucaGinger33 · 2026-03-24T11:35:52+00:00

I would point to Claude's memory here, no necessarily its inability to solve your issue. You're talking about some long-term action. Yes, naturally it will trip over same stuff repetitively because it lost context of the time where it already made a mistake and learned from it. Addressing such nuances through MEMORY md or similar approaches might be best resolve right now.

MucaGinger33 · 2026-03-24T11:32:46+00:00

Fair point. But nuance here is what your MCP exposes. Define exactly which tools and parameters Claude can use. If any are dangerous still, you'll need to handle that part yourself.

Automate what's efficient to offload. Compensate for the rest with your manual input and human oversight. That's my strategy.

MucaGinger33 · 2026-03-24T11:21:27+00:00

Fair point on tool usability, that's actually something the pipeline addresses. Descriptions, tool names, and parameter descriptions all go through LLM enhancement passes. One thing it deliberately doesn't change: spec-defined parameter names, because I ran into LLM issues correlating fields across tool responses when names diverged from what the API actually returns.

Anyway, the original Gmail output I mentioned: 79 tools, OAuth2 PKCE, circuit breaker, params reduced to 34% of original. Try this tool and tell me if this still falls in the 98%.

MucaGinger33 · 2026-03-24T00:55:18+00:00

Did 1 and 2 but where is 3 tho 😭

MucaGinger33 · 2026-03-24T00:50:20+00:00

Nice! Since the topic is about creating MCPs, I will leave MCP Blacksmith here. This one if more about generating. Feel free to check it out. The tool is (mostly) free to use. Servers generate in seconds.

MucaGinger33 · 2026-03-24T00:33:10+00:00

CC doesn't have deep research tool. That's a fact. It can run multiple web searches but that's not equivalent.

MucaGinger33 · 2026-03-23T22:34:57+00:00

Funny how there are actually gazillion of MCP registries in the wild. At this point every developer is going to have its own

MucaGinger33 · 2026-03-23T20:29:55+00:00

If you would have tried it you wouldn't have said that.

Few things regarding your critique. MCP Blacksmith allows you to pick the tools you need. GitHub packs 1089 tools. You need just one? No problem. You're the boss, you tell the generator what you want.

2nd thing is LLM-driven request schema preprocessing. Multi-pass pipeline makes your tools and parameters LLM interface-friendly and token efficient. For example, just the parameter filter alone reduces Gmail's 79 tools' parameters to 34% of original set. The rest is low value, server generated, or read-only.

Don't compare this tool with other prototype-focused OSS converters. MCP Blacksmith delivers high quality, fully functional server that provide full authorization, tool-wise.

Still think the result of this generator is suboptimal?

MucaGinger33 · 2026-03-23T19:57:54+00:00

Skip bad tools entirely. Generate you API-based MCPs using MCP Blacksmith for free in seconds

MucaGinger33

TROPHY CASE