SShortSingh.
Back to feed

8 Role-Based AI Agents You Can Build Using MCP Servers

0
·75 views

A practical guide from DEV Community outlines how to build Model Context Protocol (MCP) agents tailored to specific workplace roles, including sales, marketing, support, and engineering. Each agent is defined by four core components: a language model, two to three MCP servers, a system prompt, and a write guardrail. The guide recommends a three-server limit per agent, as connecting more degrades tool-selection accuracy and consumes context window space. Server combinations vary by role — for example, sales agents pair HubSpot with Exa and Google Calendar, while engineering agents connect GitHub, Sentry, and Linear. A key safety rule emphasized throughout is that agents should propose write actions rather than execute them automatically, to prevent unintended changes to live data.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Analysis finds new iPhone apps earning revenue before getting many reviews

A study of 142,506 iPhone apps released between August and November 2026 examined the 200 with the highest estimated monthly revenue. Of these, 83 were games, while the remaining 117 were mostly small apps with few ratings. Most categories, including Music, Photo & Video, and Developer Tools, were dominated by apps with fewer than 500 ratings, suggesting newcomers can still gain traction. The figures are estimates pulled from appsout's catalog on 15 November 2026, and the analysis only covers apps that succeeded, not those in the same niches that earned nothing.

0
ProgrammingDEV Community ·

Six Blacksmith alternatives for GitHub Actions, ranked by Linux rate at 2 vCPU

A comparison of six vendors that can replace Blacksmith as a GitHub Actions runner, ranked by their published Linux rate for 2 vCPU as of September 20, 2026. Blacksmith's Ubuntu x64 rate of $0.004 per minute sits mid-table, while its ARM rate of $0.0025 ranks joint third. The article notes Blacksmith's strength in single-core performance and its 3,000 free monthly minutes, but flags add-on caching fees and unpublished billing granularity as reasons teams switch. Ubicloud, Namespace, Latchkey, and Depot are each highlighted for a distinct advantage, such as lower rates, more cores per dollar, reduced re-run waste, or included Docker caching. The comparison covers costs for 10,000 Linux minutes, where Blacksmith x64 comes to $28 per month against $42 for GitHub-hosted Team.

0
ProgrammingDEV Community ·

Guide Shows Linux Users How to Inspect and Unlock Their Own Protected PDFs

A DEV Community tutorial explains how Ubuntu and other Linux users can deal with PDFs they have locked out of, such as their own forgotten-password files. It distinguishes between open passwords needed to view a document and owner passwords that only restrict printing, editing, or copying. The guide walks readers through installing open-source tools like qpdf, PDFtk, John the Ripper, and Poppler utilities via the terminal. It also covers inspecting encryption settings, backing up files first, and creating an unlocked copy when the file's permissions allow it.

0
ProgrammingDEV Community ·

CISA Flags SSH Flaw CVE-2026-123158 in Alpine Linux Systems Under Active Exploitation

CISA added CVE-2026-123158, nicknamed "SSHole", to its Known Exploited Vulnerabilities catalog on November 9, 2026, citing evidence of active attacks. The flaw lets an attacker log in over SSH using a long password on certain Linux systems that use the musl C library without PAM, with Alpine Linux as the main example. The problem stems from musl's crypt() rejecting passwords over 256 bytes and returning "*", which matches the "*" placeholder on accounts without valid passwords. OpenSSH released version 10.6p2 on November 5 with a workaround, and Alpine shipped patched packages the same day. Researchers reported an attempt less than nine hours after disclosure, and managed platforms are largely unaffected, while self-managed Alpine hosts and containers running an SSH server face the greatest risk.