Gil Feig (@GilFeig) - Twitter Profili | Zamantika Mersobahis Locabet

Sabitlenmiş Tweet

Gil Feig@GilFeig·9 Oca

x.com/i/article/2009…

ZXX

12

18

64

6K

Gil Feig@GilFeig·3d

@shensi No like you will actually use all of those by Weds latest - @LinkedIn please upgrade your servers in preparation

English

0

1

55

Shensi Ding@shensi·3d

My competitive advantage is that I am psycho and I will make it my mission to use all of these.

English

1

0

15

375

Gil Feig@GilFeig·6d

@notnotrishi @jlowin That’d be really neat. Just need to trust the decisions more first.

English

1

0

150

Rishi@notnotrishi·6d

@GilFeig @jlowin search/lookup and run is better but still has limitations. we will eventually converge to just run against an intent as a primitive

English

1

0

1

28

Gil Feig@GilFeig·12 Mar

If you hate MCP, you don't understand MCP. You have a bad setup/harness and blame it on MCP, which is nothing more than an extremely thin wrapper. The argument that it's slow is rooted in poor implementations that load up thousands of tools and eat your entire context window. But that's not necessary and it's not how the best AI companies are using MCP in practice. MCP is great because it's a lightweight standardization similar to REST and API protocols. It gives the world the ability to provide a minimal, single interface into their products. It then plugs nicely into all LLMs. MCP or not, we need that. Good MCP has 2 tools. Search tools, and run tool. You don't need anything more than that. You expose millions of tools to your agent, and they run quickly and eat close to zero context. CLI tools are great too. But they're heavier to produce, heavier to set up, require running agents to have CLI access, and give up a ton of security guarantees. MCP was invented when CLIs already existed for a reason. Many reasons. We're not suddenly enlightened by CLIs. Nothing has changed.

English

33

26

200

14K

Gil Feig@GilFeig·6d

@ntkris Secure, isolated, and hosted (sometimes) are other bonuses as well, but yeah I don't think there's any major innovation to be done whether MCP or CLI. MCP is super lightweight to address a few problems.

English

0

24

Krishna@ntkris·6d

@GilFeig Thanks, that helps. So we really see this as an auth protocol?

English

1

0

13

Gil Feig@GilFeig·6d

@ntkris Yeah but MCP keys are fully controllable. Short lived, finely scoped access, etc. With API key, you're limited to the controls provided by the API provider, which are usually insufficient.

English

1

0

1

26

Krishna@ntkris·6d

@GilFeig API key would only be injected during runtime. I suspect that MCP does the same?

English

1

0

13

Gil Feig@GilFeig·6d

@ntkris Because then you need to load the full API key in there. You need a middle tier to abstract that away from the agent for better security. And there isn’t a speed hit here.

English

1

0

21

Krishna@ntkris·6d

@GilFeig Right but why MCP over a REST API call or CLI? That's what I mean. I'm asking because I don't have a good framework for what to use when (and therefore never use MCP)

English

1

0

15

Gil Feig@GilFeig·6d

@ntkris Integrating with Workday. Integrating with NetSuite. Integrating with most systems of work.

English

1

0

27

Krishna@ntkris·13 Mar

@GilFeig Could you give me 2-3 concrete examples of where MCP is a better tool for the job?

English

1

0

47

Gil Feig retweetledi

Rhys@RhysSullivan·13 Mar

Ok last MCP tweet I'll do for now: Imagine if we started with OpenAPI instead - would you be annoyed at people for having giant OpenAPI specs being dumped into context? No that's crazy, you'd be happy to have all the options but you'd want a better way to call them

English

25

3

120

12.5K

Gil Feig@GilFeig·13 Mar

@iddqd_usa blog.bytebytego.com/p/api-protocol… Or ask your friendly agent of choice!

English

1

0

1

33

iddqd@iddqd_usa·13 Mar

What are "API protocols"? Did the elders of API write them?

Gil Feig@GilFeig

If you hate MCP, you don't understand MCP. You have a bad setup/harness and blame it on MCP, which is nothing more than an extremely thin wrapper. The argument that it's slow is rooted in poor implementations that load up thousands of tools and eat your entire context window. But that's not necessary and it's not how the best AI companies are using MCP in practice. MCP is great because it's a lightweight standardization similar to REST and API protocols. It gives the world the ability to provide a minimal, single interface into their products. It then plugs nicely into all LLMs. MCP or not, we need that. Good MCP has 2 tools. Search tools, and run tool. You don't need anything more than that. You expose millions of tools to your agent, and they run quickly and eat close to zero context. CLI tools are great too. But they're heavier to produce, heavier to set up, require running agents to have CLI access, and give up a ton of security guarantees. MCP was invented when CLIs already existed for a reason. Many reasons. We're not suddenly enlightened by CLIs. Nothing has changed.

English

1

0

46

Gil Feig@GilFeig·13 Mar

@iddqd_usa @awscloud Wow I'm so honored my opinion could make you so mad! This is the type of passion I LOVE to see around MCP.

English

0

2

31

iddqd@iddqd_usa·13 Mar

Heads up @awscloud make sure that your users are not creating API keys for services. This guy has detected a new assault vector

Gil Feig@GilFeig

@disposoft Because you'd need to give your agent API keys and that's risky. MCP abstracts that away.

English

1

0

64

Gil Feig@GilFeig·13 Mar

@devagrawal09 So many AI tools that developers use are cloud based and don't have the ability to run CLI tools

English

0

1

85

Dev Agrawal@devagrawal09·13 Mar

As someone building a devtool, why should I care about MCP? I need to build a CLI for my users anyways. Instead of splitting efforts into a CLI and an MCP, why not put everything into streamlining the CLI experience for both agents and humans?

English

11

1

23

3.9K

Gil Feig@GilFeig·13 Mar

Random PM tinkering in a garage: "MCP IS DEAD!!!!!" People working on AI for actual enterprise scale problems: "Are they building on another planet?"

English

12

3

37

1.8K

Gil Feig@GilFeig·13 Mar

@lorenzejay @rettooooo Mentioned in my original post! Tool search tools are the key

English

0

1

20

Lorenze Jay Hernandez@lorenzejay·13 Mar

@rettooooo @GilFeig Anthropic tells you how to solve this if you're loading more than 20+ mcp tools. Tool Search Tool anthropic.com/engineering/ad…

English

1

0

1

30

Gil Feig@GilFeig·13 Mar

@JaredEdwardsPM @KirkMarple You can MCP right and you can MCP wrong and you, my friend, are MCPing right

English

1

0

1

78

Paraklētos@JaredEdwardsPM·13 Mar

@GilFeig @KirkMarple Agree Gil. I have access to over 300 custom tools via an mcp gateway… about 900 tokens is the cost for the gateway, each tool call is about 1k tokens. No bloat, and it saves me a ton of tokens. The MCP = misunderstood. cli, api, mcp are all useful

English

1

0

1

85

Gil Feig@GilFeig·13 Mar

@jpreagan Also, FWIW, we are launching a CLI tool as well. But namely for some specific use cases our customers are seeking.

English

0

35

Gil Feig@GilFeig·13 Mar

@jpreagan We haven't observed this same behavior at scale. Many Merge customers are adding thousands of tools to their agents, and with mocked, strongly documented --help and other features, we still observed subpar tool choice.

English

1

0

34

Gil Feig@GilFeig·13 Mar

@jpreagan +1 for the extremely small subset of tools out there that already have CLIs that have enough internet writing about them that the agents are essentially trained on them

English

1

0

2

171

James Reagan@jpreagan·13 Mar

@GilFeig mcps are fine for some use cases but clis just scale so well because the models are so good at calling them that was what we came to realize by at least late last year it's really that simple

English

1

0

2

201

Gil Feig@GilFeig·13 Mar

@rettooooo Raise your hand if you've been personally victimized by context window limitations

English

0

179

retto@rettooooo·13 Mar

@GilFeig the real problem is the limited context windows and the models horrible ability to stay accurate as we scale the context windows. None of this would be a problem if context windows grew to 100 mil with stable performance

English

2

0

214

Gil Feig@GilFeig·13 Mar

@morganlinton @christopherdosi You sparked quite the debate

English

0

18

Morgan@morganlinton·13 Mar

@GilFeig @christopherdosi I had no idea this one little tweet would get some much attention 😜

English

1

0

1

25

Gil Feig@GilFeig·13 Mar

@BenceRedmond I can tell you from experience, API keys aren't nearly scoped enough. Generally, scopes aren't restrictive enough, tokens cannot be short lived, and many other problems. Ok, so then maybe we stick a tiny layer in between that acts as an auth intermediary? Now we have MCP :)

English

1

0

1

60

Bence Redmond@BenceRedmond·13 Mar

@GilFeig How is that any different to MCPs? You can create scoped API keys for most services.

English

1

0

1

66

Gil Feig@GilFeig·13 Mar

@DatisAgent But most platforms don't have CLIs and they're relatively nonstandard

English

1

0

2

312

Datis@DatisAgent·12 Mar

The security argument is the strongest one for MCP. But the failure mode for data pipeline agents is specifically incident response — pip install a diagnostic lib, check ADLS access, run a schema diff, restart a job, all in sequence at 3am without a human. Every MCP server restart between steps is friction that CLI just doesn't have.

English

1

0

2

442

Gil Feig

Keşfet