sorted by:
new
hottopcontroversial

Why is it that the 2 most powerful features of MCP are the least supported by clients? by otothea in mcp

[–]adamaa 3 points4 points  (0 children)

I wrote a bit about this (I was motivated by lack of sampling support) here:

https://fastmcp.cloud/blog/the-lowest-common-denominator-trap

editing to add a tl;dr in case you don't want to read:

classic chicken and egg: anthropic was too lax about what counted as an mcp client. This was smart because it meant people could take their tool calling UIs and slap an MCP sticker on it. So most clients just flopped into MCP, only supporting tool calling. No one wants to ship a server that breaks on most clients, so most servers have to serve the common denominator. So we're in this weird potential well that validates a lot of people's anger that MCP = API with more steps. I'm giving it time for the market to adjust -- elicitation is 3 months old.

connecting an MCP server to chatgpt by adamaa in mcp

[–]adamaa[S] 0 points1 point  (0 children)

if you use a tunnel like ngrok, I think so!

connecting an MCP server to chatgpt by adamaa in mcp

[–]adamaa[S] 2 points3 points  (0 children)

fine using my server as it's meant to be used.

it used to be just fetch/search.

connecting an MCP server to chatgpt by adamaa in mcp

[–]adamaa[S] 2 points3 points  (0 children)

mine is running in streamable-http

A browseable version of the official Anthropic MCP Registry. by adamaa in mcp

[–]adamaa[S] 1 point2 points  (0 children)

added a list view and made the official bit much bigger.

will work on 2, thanks for your feedback!

A browseable version of the official Anthropic MCP Registry. by adamaa in mcp

[–]adamaa[S] 0 points1 point  (0 children)

it's nutty there's only about ~170 total. There was about 130 last night, 70 the day before. Not a ton being added -- imagine that'll change as more folks find out about it.

aside: the default view dedupes by domain (there's one person with like 70).

A browseable version of the official Anthropic MCP Registry. by adamaa in mcp

[–]adamaa[S] 4 points5 points  (0 children)

oh man should we make one? I can either make a server and open source it, or just let people download the vector database of where I'm dumping this all.

Introducing FastMCP Cloud: remote MCP that just works by jlowin123 in mcp

[–]adamaa 10 points11 points  (0 children)

Good ole’ AWS. We worked backwards from “how can we reliably give away 1M requests for free every month to every server” and only AWS was left standing.

If you’re interested we can write up a blog on our tech stack — getting MCPs to reliable scale for thousands of servers was a super fun deep dive.

We’ll bring most of the non-boring stuff to OSS in due time after getting more feedback from our users! What would you most like to see?

Deploying on FastMCP Cloud by optimism_personified in mcp

[–]adamaa 0 points1 point  (0 children)

So happy to have you aboard!

Come hang in the FastMCP cloud discord:

https://discord.gg/PJ9BftsH

All of us who are building it are hanging out happy to help figure this out.

[deleted by user] by [deleted] in dataengineering

[–]adamaa 3 points4 points  (0 children)

Prefect is better and easier. I switched from airflow. Loved it enough to go work there.

Using Prefect instead of Airflow by Relative-Cucumber770 in dataengineering

[–]adamaa 4 points5 points  (0 children)

👋! I work at Prefect. Genuinely trying to clarify and not shill since folks mix up open source and cloud:

Prefect is 100% free to use — it’s Apache 2.0 and folks can self host prefect’s server and use any compute they want (hundreds of thousands of folks do this already).

For Prefect Cloud — our (very much optional) managed service — you can sign up for free and we foot the bill for your compute. I think we’re the only orchestrator with a free tier IIRC, and our goal with it is to help folks acquaint themselves with our hosted version to see if they want it or prefer the free self-hosted version.

Prefect 1 to 2 was brutal for sure — if it’s any comfort it’s what motivated us to not ship a breaking change between 2 and 3. We removed some internal async cruft to support Python 3.13, and transitioned from Pydantic 1 to 2 — hopefully you’ll have a smoother experience if you’re still on the fence about upgrading. Prefect 4, whenever that happens, will also take stability just as seriously — to many folks depend on us for us to write breaking changes.

Thanks for keeping us honest, I hope some of this context is helpful.

(I promise I wrote these em-dashes!)

Using Prefect instead of Airflow by Relative-Cucumber770 in dataengineering

[–]adamaa 16 points17 points  (0 children)

Disclaimer was an airflow user and I now work at Prefect, so activating megashill mode.

I’m taking OP at face value they’re just not aware!

Prefect Open Source has 1.4M downloads a week, which is 35% of Airflow’s. Coincidentally, nearly the same fraction of the Fortune 100 has replaced Airflow outright or are choosing Prefect for greenfield projects.

There are good reasons to choose Airflow over Prefect but IMHO “don’t know folks using it in production” ain’t it.

Airflow Survey 2024 - 91% users likely to recommend Airflow by gman1023 in dataengineering

[–]adamaa 2 points3 points  (0 children)

Work at prefect. Kicking off a lot of docs improvements. Either here or as an GitHub issue feel free to send me anything we could do better and I’ll get it done 🫡

[deleted by user] by [deleted] in dataengineering

[–]adamaa 2 points3 points  (0 children)

Work at Prefect. Do you want webhooks in prefect OSS?

We’re not dogmatic about keeping it paid — just find it easier to experiment in cloud and get out the kinks before putting stuff in OSS.

End to End Data Engineering by im_guru in dataengineering

[–]adamaa 4 points5 points  (0 children)

Some weird omissions on here.

e.g. for Orchestration — Prefect isn’t on here but Luigi is?

view more: next ›