18 posts tagged with "agentic-ai"

Every company has at least one of these roles: a highly skilled, well-compensated professional who spends 60% of their day doing something a well-designed system could do automatically. Reading a log. Routing a ticket. Copying a number from one system into another. Writing the same report they wrote last month.

That is not a talent problem. It is an architecture problem. And MCP agents are how you fix it.

This post covers where the highest-impact automation opportunities are across the business — and then builds the DBA case in full detail, because database administration is one of the most expensive, most automatable, and most overlooked targets in the enterprise.

Your data lake and warehouse already hold the answers your business needs. The missing layer isn't more data — it's an intelligent orchestration layer that lets AI agents query, reason, and act on that data reliably.

This post walks through a production-ready architecture that uses dbt as a semantic manifest, Model Context Protocol (MCP) servers as the access layer, and multiple specialized agents to turn your existing Snowflake, Redshift, or BigQuery investment into an active, AI-driven intelligence system.

Most "AI" projects are still just API calls wrapped in if/else logic. True agentic AI gives the model real tools — file access, database queries, API calls — and lets it decide how to use them to accomplish a goal.

Model Context Protocol (MCP), developed by Anthropic, is the emerging open standard for connecting AI agents to those tools in a secure, structured way. In this guide you'll configure two MCP servers, write a simple agent, and automate a daily reporting task — using Claude, OpenAI, or a self-hosted Ollama model.

Security logs are among the highest-volume, most time-sensitive data in any organization. A single mid-sized network generates millions of log events per hour — firewall denies, DNS queries, authentication events, lateral movement signals. Traditional SIEM tools drown in the volume. Manual analysis is impossible at scale.

This post shows how to combine msgspec for high-performance log parsing with an AI agent that correlates events, identifies threat patterns, and generates structured incident reports — without the overhead of a full SIEM platform.

A typical job posting for a technical role receives 200–400 applications. A recruiter manually reviews each one, spending 30–60 seconds per resume to decide whether to advance the candidate. That's 3–6 hours of screening work per role, per round — work that is largely pattern-matching against a known rubric.

A resume screening agent replaces the manual first pass entirely. It evaluates every application against a structured rubric, produces a scored and ranked shortlist with written reasoning, and surfaces only the edge cases that genuinely need human judgment.

Accounts payable is the textbook case for AI automation: it's high-volume, rule-based, document-heavy, and the consequences of errors are clear and measurable. The average AP team processes hundreds to thousands of invoices per month, spending 15–20 minutes per invoice on a workflow that follows the same logic every time.

An AP automation agent handles the full cycle — from invoice receipt to ERP posting — touching humans only for exceptions that genuinely require judgment.

Every engineering and support team drowns in a version of the same problem: tickets arrive faster than they can be read, let alone triaged. The backlog grows. High-priority issues get buried under noise. The team that should be fixing problems spends an hour each morning just sorting them.

A Jira triage agent processes every incoming ticket the moment it arrives — classifies, prioritizes, assigns, and drafts an initial response — before any human reads it. The team starts from an already-organized board, not a raw queue.

Talend runs your ETL. It also fails silently, retries indefinitely, and buries the root cause in a 400-line XML log. An AI agent changes that — it reads the logs, understands the failure, and creates a Jira ticket before your on-call engineer even opens Slack.

Sales reps spend an average of 5–6 hours per week on CRM data entry. They log call notes, update opportunity stages, create follow-up tasks, and capture next steps — after every single call. It's manual, it's inconsistent, and it's the reason CRM data is always slightly out of date.

A meeting notes agent eliminates this entirely. It processes the call transcript, extracts structured data, and updates Salesforce before the rep has finished their post-call coffee.

A single agent with access to all your tools sounds like the simplest architecture. In practice, it's the architecture that breaks first. As tool count grows, context windows fill up, prompts become unwieldy, and the agent starts making worse decisions because it's trying to do too many things at once.

Multi-agent systems solve this by decomposing complex workflows into specialized agents with focused responsibilities, coordinated by an orchestrator. The result is more reliable, more observable, and — counter-intuitively — cheaper to operate.