MCP was always meant to be bi-directional, but most people don't understand it well enough to see the future.
→ View original post on X — @jiquanngiam, 2026-03-28 17:00 UTC
By
–
MCP was always meant to be bi-directional, but most people don't understand it well enough to see the future.
→ View original post on X — @jiquanngiam, 2026-03-28 17:00 UTC
By
–
MCP is so back. Peter Steinberger 🦞 (@steipete) The next version of OpenClaw is also an MCP, you can use it instead of Anthropic's message channel MCP to connect to a much wider range of message providers. (I know, this is awkward) — https://nitter.net/steipete/status/2037715163562815817#m
→ View original post on X — @jiquanngiam, 2026-03-28 16:48 UTC
By
–
I recently learned that "Polsia" is "AI Slop" spelled in reverse.
By
–
We've been liking Vercel Sandboxes. Great product.
By
–
Moderately strong opinion: create custom MCP tools that are tailored towards the custom setup in the CRM. The tools should reflect the schema.
By
–
We're finding MCP apps to be a better alternative to elicitations – make an app to do the elicitation! Have you seen this too?
By
–
I say this as someone very passionate about the promise of AI-enabled productivity. But clankers that scrape and automate web browsers are not the way. Service provider APIs must be respected. MCP servers let them set the terms of what's meant for agents. That is how we all align
→ View original post on X — @jiquanngiam, 2026-03-26 14:56 UTC

By
–
PSA: Stop running local MCP servers. The folks at futuresearch were pwned when a local MCP server pulled in an impacted package. Always run your MCP servers remotely. The blast radius should be limited to the container that it runs in. If you're impacted by the LiteLLM

By
–
PSA: Stop running local MCP servers. The folks at futuresearch were pwned when a local MCP server pulled in an impacted package. Always run your MCP servers remotely. The blast radius should be limited to the container that it runs in. If you're impacted by the LiteLLM