Notion Developers
218 posts

Notion Developers
@NotionDevs
Connect Notion to the tools you use every day.




MCPs were supposed to be the new universal plug for AI agents. So why are MCPs suddenly being dropped for the old school CLI? Eric Goldman (@goldmanem), MJ Felix (@MarissaJFelix), and Modi (@akm_io) dug out the signal from the noise on MCPs vs CLIs and how model capabilities are dramatically changing what’s possible under the hood, all from the frontier of of our team building real workflows with (and for 👀) agents. Some highlights: → MCP's promise was real — plug-and-play with just a URL. But it became a lowest-common-denominator abstraction that jammed product intent, workflows, and agent assumptions into one layer. → Models outgrew MCP faster than it could evolve. Early MCPs were simplified for weaker models. By the time teams shipped them, the models didn't need the guardrails. → Every MCP layer burns tokens. Viewing a long page costs 50k tokens through MCP. With a CLI, you pipe to head and grab what you need. → CLI is the new (old) frontier. Models are now strong enough to write code and compose tools directly with CLIs. But what are the downsides to that? → More tools, not fewer. Conventional wisdom said keep tool count low. We're moving toward agents that can handle hundreds of tools instead of a dozen. → Integrations will disappear. The future is agents writing scripts per workflow, talking directly to other agents, and using the same tools humans use. Oh...and pay attention. They may have let a few dev platform updates slip 👀



Vercel now powers the Notion agent platform. Not only are they a great company and product I use daily, I think they're going to be one of the big winners of the agent era. The main 'runtime' of an agent is English (natural language) documents and specs. The other ingredient is access to data and integrations. Notion is at the center of both.

Vercel powers @NotionHQ's developer platform. Notion Workers use Vercel Sandbox to safely run code, giving agents the power to sync data, trigger automations, and call any API. vercel.com/blog/notion-wo…




I fully automated monthly client invoicing with @NotionHQ custom agents and workers Every month my custom agent: - Pulls billable hours from @toggl, my team's time tracking app - Calculates $ amounts accurately with Python in a @vercel sandbox - Creates an invoice in @mercury for the correct customer with the right $ amounts, dates, etc - Drafts an email to my client with a link to the invoice - Pings me on slack that the invoice is ready to review All I have to do is press send No reason I couldn't automate this fully. I will eventually once I trust it's 100% accurate.





