# mcps Published articles for mcps. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Build with Claude Code: Enrollment for a Two-Day Cohort Course DevFeed: [Build with Claude Code: Enrollment for a Two-Day Cohort Course]() Original publisher: [Read original article]() Author: ByteByteGo Published: 2026-09-15T19:31:01Z Content type: article Language: en Sources: [ByteByteGo]() Topics: [Claude Code](), [Development](), [Code](), [Git]() Tags: [build](), [claude-code](), [code](), [development](), [git](), [hooks](), [how-to](), [learn](), [mcps](), [parallel]() ### AI overview The article announces the relaunch of Build with Claude Code, a two-day cohort-based course taught by John Kim. It covers Claude Code fundamentals and production workflows, including context engineering, memory, Skills, MCPs, hooks, Git worktrees, subagents, and agent teams. ### Source excerpt We're relaunching Build with Claude Code, a 2-day intensive cohort-based course taught by John Kim, who has trained hundreds of engineers at Meta to use Claude Code in real production workflows. ## From AI demos to real work: How Engineering and Operations learn side by side DevFeed: [From AI demos to real work: How Engineering and Operations learn side by side]() Original publisher: [Read original article]() Author: Nubank Editorial Published: 2026-09-14T16:28:23Z Content type: article Language: en Sources: [Nubank]() Topics: [Artificial Intelligence](), [Generative AI](), [AI Development](), [Software Engineering](), [Development]() Tags: [agents](), [ai](), [ai-research](), [applied-ai](), [data-science-machine-learning](), [development](), [engineering](), [mcps]() ### AI overview This article describes Nubank's Ops AI Acceleration Program and an applied AI workshop with PJ Operations. The workshop combined foundational technical concepts about generative AI, agents, models, tools, context, skills, and MCPs with a real operational challenge to connect engineering knowledge with operational expertise. ### Source excerpt Building shared technical understanding so operational expertise can turn AI into practical improvements The post From AI demos to real work: How Engineering and Operations learn side by side appeared first on Building Nubank. ## Let's Learn GitHub Copilot App - Free Virtual Training Event DevFeed: [Let's Learn GitHub Copilot App - Free Virtual Training Event]() Original publisher: [Read original article]() Author: Katie Savage Published: 2026-07-08T17:30:28Z Content type: article Language: en Sources: [Developer Blogs]() Topics: [GitHub Copilot app](), [GitHub](), [Artificial Intelligence](), [Pull Request]() Tags: [agents](), [ai](), [developer-events](), [event](), [free](), [github](), [github-copilot](), [github-copilot-app](), [how-to](), [learn](), [mcps](), [microsoft-for-developers](), [pull-request](), [virtual-event]() ### AI overview This article announces and describes a free, instructor-led virtual training event for learning the GitHub Copilot app. It covers the app's setup, coding assistance, project management, code review, custom instructions, MCPs, Agent Merge, and Canvases. ### Source excerpt Join us for a free online event series kicking off July 16 to learn how to get started with the GitHub Copilot App! The post Let's Learn GitHub Copilot App - Free Virtual Training Event appeared first on Microsoft for Developers. ## A note on Context Windows DevFeed: [A note on Context Windows]() Original publisher: [Read original article]() Author: Sanskar Agrawal Published: 2026-07-03T12:39:24Z Content type: opinion Language: en Sources: [Sanskar's Stuff]() Topics: [context window](), [long-context](), [Claude Code](), [codex](), [Claude]() Tags: [agents](), [claude](), [claude-code](), [codex](), [context](), [context-window](), [cost](), [developers](), [mcps](), [retrieval](), [skills](), [terminal]() ### AI overview This opinion article discusses context-window management in long agent conversations. It argues that auto-compaction may occur too late, retrieval quality can decline as context grows, and larger contexts cost more. It recommends monitoring context usage, starting new conversations, keeping concise project instructions, limiting MCPs, skills and subagents, and using subagents to reduce context inflation. ### Source excerpt In long agent conversations, Developers often lose track of how much context has been used. Tools like Claude Code or Codex have auto-compaction built in, but they compact too late. Opus 4.8 has a mil ## Fin extends Service Agent support to HubSpot and Freshworks DevFeed: [Fin extends Service Agent support to HubSpot and Freshworks]() Original publisher: [Read original article]() Author: Paul Adams Published: 2026-06-09T16:45:42Z Content type: release Language: en Sources: [The Intercom Blog]() Topics: [hubspot](), [Support]() Tags: [agent](), [apis](), [cli](), [customer-experience](), [docs](), [fin](), [fin-for-freshdesk](), [fin-for-hubspot](), [helpdesk](), [hubspot](), [integrations](), [mcps](), [news-updates](), [platform]() ### AI overview Intercom announces that Fin can operate as a Service Agent on top of HubSpot and Freshworks, allowing customers to integrate it without migrating from their existing helpdesk. The article also describes Fin's open-platform approach, including APIs, MCPs, CLI access, and public documentation. ### Source excerpt Fin can be used as a Service Agent on top of HubSpot and Freshworks, meaning you can use the world's best Agent without migrating off your helpdesk. ## Why MCP remains useful despite context-window overhead DevFeed: [Why MCP remains useful despite context-window overhead]() Original publisher: [Read original article]() Published: 2026-03-26T11:30:00Z Content type: opinion Language: en Sources: [Antonio Leiva]() Topics: [Model Context Protocol (MCP)](), [Model Context Protocol](), [anthropic]() Tags: [agents](), [ai](), [anthropic](), [chatgpt](), [context-window](), [mcp](), [mcps](), [tooling]() ### AI overview This opinion article argues that MCP remains useful despite criticism that MCP servers are obsolete. It explains that MCP standardized interactions between AI clients and tool providers, while its main weakness was the context-window overhead created by extensive tool metadata. ### Source excerpt Everything Android, Kotlin and other random topics ## Here's my list of reasons for using Opencode DevFeed: [Here's my list of reasons for using Opencode]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2026-03-17T20:00:00Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [User experience (UX)](), [client](), [servers](), [context]() Tags: [agentic](), [architecture](), [bugs](), [external](), [features](), [mcps](), [models](), [opencode](), [plugins](), [switching](), [tailscale](), [ux]() ### AI overview The author gives five personal reasons for using OpenCode: switching between models, its client-server architecture, subagent and mode features, opinionated user experience, and plugin customization. The article also notes that OpenCode has bugs and missing features, which the author says have not stopped them from using it exclusively for two months. ### Source excerpt Here's my list of reasons for using Opencode. 1. Switch between models on the fly ## I'm often experimenting with the bleeding edge models as they come out. I actively switch between models for tasks and I use them all enough where I can tell the difference. Opencode lets me switch between models mid-task or mid-conversation. Fluidly. 2. client-server architecture (a.k.a built-in remote control) ## I wrote about this and agentic fluidity in more detail but tldr: Opencode has the client/server architecture baked in. So I can just start an opencode server on one machine, expose it through tailscale serve and start using it on my phone or other machines. 3. Subagent + mode features ## I talked about this on my podcast in some detail but Opencode has the best implementation of subagents and modes. You can switch to a subagent definition as your primary mode, then operate other subagents from there. It makes orchestrator-type tasks super easy. 4. Opinionated UX ## I love that OpenCode is opinionated about their UX. They don't try to be Claude Code or Codex. In the process they have some really nice UX patterns like a sidebar with ongoing file changes, context/cost, MCPs connected etc. It's the first time I've not needed to worry about a custom statusline.sh or building one. 5. "Highly" customizable via plugins ## The plugin ecosystem is highly customizable. To the point where you can add new features, integrate with external services or even modify OpenCode's default behavior. The wonderful Jesse Vincent mentioned this to me when I was stupidly contemplating a fork. What's missing # It's not all rainbows and sunshine. Anomaly -- the team behind OpenCode -- is small. Which sometimes shows, because there's definitely bugs and some features missing. But I will say... none that's deterred me from using it for the last two months, exclusively. Go give it a shot. Many of the serious AI coders I know are really liking it and switching. ## OLX Masterclass Frontend 2026 DevFeed: [OLX Masterclass Frontend 2026]() Original publisher: [Read original article]() Author: Isaac Queiroz Published: 2026-02-25T16:16:00Z Content type: news Language: en Sources: [OLX]() Topics: [Front end](), [Model Context Protocol](), [Development](), [CSS](), [React](), [Figma](), [repo](), [configuration]() Tags: [2026](), [agents](), [ai](), [code](), [coding](), [component](), [configuration](), [css](), [development](), [event](), [figma](), [frontend](), [frontend-development](), [masterclass](), [mcp](), [mcps](), [model-context-protocol](), [olx](), [react](), [repo]() ### AI overview OLX announces its 2026 Frontend Masterclass, featuring three sessions on MCP integrations and Figma-to-React workflows, new CSS capabilities, and managing localized websites for multiple brands from a single repository. ### Source excerpt The always-evolving challenges of OLX create a rich environment for innovation, experimentation, and knowledge sharing. In our 2026 Frontend Masterclass, we have three sessions that will shed light on our current development flow. Join us on March 3rd, 2026, from 6:00 pm to 9:00 pm at our OLX Offices in Poznań! Do you want to join us and know what's trending in the latest frontend technology? Check the event information and join here! Can't join it in person? Sign in to this form to receive the online recording of the session! Our Agenda With a broad schedule, our speakers will deliver a mix of technical presentations and demonstrations on multiple subjects. MCP Servers in Action: From Figma Design to React Component in Minutes by Karol Grabowski Part of what changed in our day-to-day flow is how AI is always available to help us. AI assistants and agents are powerful out-of-the-box tools; we can augment our reach by configuring Model Context Protocols (MCPs) to take our setup a step further. Join Karol to explore how the Model Context Protocol turns AI assistants into powerful development partners with direct access to your tools. This talk covers the MCP ecosystem, real OLX integrations, and includes a live coding session demonstrating the Figma-to-code workflow. CSS is no longer "this simple" -- it got _layers_, quite literally by Tomasz "Comandeer" Jakut At the same time that we advance with AI and multiple experiments to learn from our users and make our flows as pleasant as possible, we are still styling our components with the usual suspects, right? Not always! Join Tomasz Jakut and deep dive into CSS's new capabilities that can redefine how we approach styling websites: from @Layer and nesting to container queries, scoped styles, and user preferences. New native features can refresh well-known techniques and make others obsolete. One-product, three brands -- Our strategy for serving different countries from a single repo by Lilian Galezewska We all know how OL ## Turning Hypermedia APIs into MCPs DevFeed: [Turning Hypermedia APIs into MCPs]() Original publisher: [Read original article]() Author: Daniel Doubrovkine (dblock@dblock.org) Published: 2025-09-18T09:00:00Z Content type: tutorial Language: en Sources: [Daniel Doubrovkine]() Topics: [API](), [Model Context Protocol (MCP)](), [MCP Server](), [REST API](), [Ruby](), [Open Source](), [Slack]() Tags: [ai](), [api-design](), [apis](), [hypermedia](), [mcp](), [mcp-server](), [mcps](), [model-context-protocol](), [open-source](), [rest](), [rest-api](), [ruby](), [slack]() ### AI overview This tutorial shows how to expose a Hypermedia API as an MCP server using the Ruby gem hyperclient-mcp. It uses the open-source S'Up Slack bot to demonstrate resource discovery, starting the server, connecting it to Claude, and querying bot and team information. ### Source excerpt I've written and talked extensively about Hypermedia APIs for about a decade. The HATEOAS constraints in representing resources for a RESTful API has numerous advantages in API design, readability, discoverability, and performance over a hand-rolled REST API. Unfortunately, adoption of Hypermedia APIs is very low compared to, for example GraphQL, but I find the implementation a lot simpler and continue adding Hypermedia APIs to my pet projects. At its root a Hypermedia API looks like so. { "_links": { "self": { "href": "https://sup2.playplay.io/api" }, "status": { "href": "https://sup2.playplay.io/api/status" }, "team": { "href": "https://sup2.playplay.io/api/teams/{id}", "templated": true }, ... } } The above example is an extract from this API. For this post we will use one of my Slack bots called S'Up, which generates fresh triads of team members in Slack to meet for coffee every week in an informal standup. The bot is open-source and you can try it here. Because the Hypermedia API structure is fixed with only "resources" and "links" (and similar to API frameworks such as GraphQL) you don't need an application-specific client to interact with the API. In Ruby, the most popular generic Hypermedia client is Hyperclient. With the API above, a client can retrieve the bot status, and using an API token obtained from an existing installation some team information. api = Hyperclient.new('https://sup2.playplay.io/api') do |client| client.headers['X-Access-Token'] = ENV.fetch('TOKEN', nil) end status = api.status puts "Bot is #{status.ping['presence']['presence']}." team = api.team(id: '1234') puts "Team name is '#{team.name}'." This will output "Bot is online." and "Team name is 'dblock'." for my installation. In this case, the generic client knew nothing about "team" - it was discovered programmatically and was, in a way, self-documenting. Unsurprisingly, this idea of templated resources is reused almost exactly the same way in the model context protocol (MCP). Therefor ## Provisioning Machines using MCPs DevFeed: [Provisioning Machines using MCPs]() Original publisher: [Read original article]() Published: 2025-05-07T00:00:00Z Content type: opinion Language: en Sources: [The Fly Blog]() Topics: [Provisioning](), [Model Context Protocol](), [fly.io](), [fly](), [Claude](), [cursor](), [GitHub]() Tags: [api](), [cdn](), [claude](), [close-to-users](), [copilot](), [cursor](), [deploy-app-servers](), [docker](), [elixir](), [fly](), [fly-io](), [github](), [heroku-alternative](), [heroku-competitor](), [hosting](), [i](), [mcps](), [networking](), [postgresql-clusters](), [provisioning](), [servers](), [terraform]() ### AI overview The author describes using MCP with Claude to create and manage Fly.io volumes, including deleting an unattached volume. The article argues that connecting LLMs to infrastructure tools can make application resource management more intuitive than using APIs, CLIs, or dashboards. ### Source excerpt Today's state of the art is K8S, Terraform, web based UIs, and CLIs. Those days are numbered. On Monday, I created my first fly volume using an MCP. For those who don't know what MCPs are, they are how you attach tools to LLMs like Claude or Cursor. I added support for fly volume create to fly mcp server, and it worked the first time. A few hours later, and with the assistance of GitHub Copilot, i added support for all fly volumes commands. This movie summary is from When Worlds Collide, by Nalaka Gunawardene I'm reminded of the memorable scene in the film Star Trek IV: The Voyage Home (1986). Chief Engineer Scotty, having time-travelled 200 years back to late 20th century San Francisco with his crew mates, encounters an early Personal Computer (PC). Sitting in front of it, he addresses the machine affably as "Computer!" Nothing happens. Scotty repeats himself; still no response. He doesn't realise that voice recognition capability hadn't arrived yet. Exasperated, he picks up the mouse and speaks into it: "Hello, computer?" The computer's owner offers helpful advice: "Just use the keyboard." Scotty looks astonished. "A keyboard?" he asks, and adds in a sarcastic tone: "How quaint!" A while later, I asked for a list of volumes for an existing app, and Claude noted that I had a few volumes that weren't attached to any machines. So I asked it to delete the oldest unattached volume, and it did so. Then it occurred to me to do it again; this time I captured the screen: A few notes: I could have written a program using the machines API, but that would have required some effort. I could have used flyctl directly, but to be honest, I would have had to use the documentation and a bit of copy/pasting of arguments. I could have navigated to a list of volumes for this application in the Fly.io dashboard, but there currently isn't any way to sort the list or delete a volume. Had those been in place, that would have been a reasonable alternative if that was something I was active