A place for developers to talk about building on Farcaster.

/dev

Capabilities have been too underutilized.
MCP might finally popularize them.
I've been a fan of capabilities and API discoverability for a long time.

The open web is dead, long live the open web. ⌐◨-◨

Building /farcaster

— gabrielayuso.com

Curious about your opinion on how generalisable the MCP client layer is?

Feels like Agent to Agent is the right abstraction layer, with each agent having its own MCP subgraph

Designing and building AI systems

https://agents.gladio.ai

I have little experience with MCP but from what I can tell it's basically an adapter layer on top of APIs that is very generalizable since it supports multiple transports and a very basic interface that can accommodate any arbitrary function/API (name + params).

It's useful for Agents but it's useful outside of the AI context as well. Arguably you can have this between FC clients and mini apps for example, and between mini apps. Adds a layer of "matchmaking" without hardcoding things.

@meb I think both are good. For ex I have an MCP server around the service and it’s meant to be a quick addition to your agent.

A2A implies I would build a tip agent, but don’t want to got that route just yet.