103 posts tagged with "MCP"

Most design operations work is repetitive data movement. Audit your component library to find unused styles, then archive them. Sync design token updates from Figma variables to your codebase. Export every frame that matches a naming pattern as 2× PNG. Post review comments on every screen in a flows section. Attach dev resources (component mappings, Storybook links) to library components. Debug why a webhook stopped firing.

Each of those is a 30-minute task across Figma's UI, REST API docs, and your terminal — and a 2-minute task as a chat message — if your AI agent can actually call the Figma API at the right granularity. This guide is the use-case version of "AI + Figma": what you ask, what the agent does, what comes back. The protocol underneath is MCP (Model Context Protocol), the bundle is /skills/figma on MCPBundles, but the framing here is workflow-first.

Most performance-marketing work in Google Ads is repetitive cognitive labour. Pull a search-term report, find the queries that wasted spend last week, write the negative-keyword list. Look at device performance, find that mobile CPC is up 40% with the same conversion rate, draft a bid adjustment. Spin up a campaign for next week's promo: budget, ad group, 15 keywords, an RSA with 11 headlines and 4 descriptions, all in PAUSED so nothing goes live by accident.

Each of those is a 20-minute task in the Google Ads UI and a 30-second task as a chat message — if your AI agent can actually call the Google Ads API. This guide is the use-case version of "AI + Google Ads": what you ask, what the agent does, what comes back. The protocol underneath is MCP (Model Context Protocol), the bundle is /skills/google-ads on MCPBundles, but the framing here is workflow-first.

Every other LinkedIn MCP server on GitHub is either a scraper that violates LinkedIn's Terms of Service or a thin wrapper around unofficial endpoints that can break at any time. Some use Patchright (a Playwright fork) to automate the browser. Others reverse-engineer private APIs. LinkedIn actively blocks these — and your account is at risk if you use them.

MCPBundles ships two LinkedIn MCP servers that work the way LinkedIn allows you to work:

• LinkedIn — built on LinkedIn's official REST API with OAuth 2.0. Manages company pages, publishes posts with images and carousels, engages with comments and reactions, runs ad campaigns, and tracks analytics.
• LinkedIn Sales Navigator — drives Sales Navigator search, profile lookups, InMail, and inbox as your connected LinkedIn account. Sign in once on a hosted page (no cookies, no extensions, no scraping); the bundle then runs SN-grade prospecting and outreach with built-in per-account rate caps so a careless agent can't get the seat banned.

You can connect either or both. The pages are the canonical product surfaces — keep this article open if you want the comparison; jump to the skill page when you're ready to use one.

Browser automation is how you test web apps end-to-end, scrape structured data from public sites, debug production issues by replaying user journeys, and automate repetitive form-filling workflows. Navigate to any page, read its content, click buttons, fill forms, take screenshots, inspect network traffic, run JavaScript, check console errors — all programmatically through natural language.

Playwright is the industry standard for browser automation: fast, reliable, cross-browser (Chrome, Firefox, WebKit), built for modern web apps. The MCPBundles browser bundles expose Playwright as MCP tools you can call from any AI agent, with two deployment modes: Local Browser (Chrome on your machine via the desktop proxy) and Remote Browser (cloud-hosted Chrome with no local install). This guide is the use-case version of "AI + Browser": what you ask, what the agent does, what comes back.

Most small-business accounting is repetitive operational work. Create an invoice for last week's hours, send it to the customer, and record the payment when it hits the bank. Pull a P&L for the quarter, export an aged-receivables report, check which customers are 30+ days overdue. Batch-update item prices, void an invoice that was sent to the wrong contact, reconcile what changed this week across customers, invoices, bills, and payments.

Each of those is a 5–10 minute task in the QuickBooks UI and a 20-second task as a chat message — if your AI agent can actually call the QuickBooks API. This guide is the use-case version of "AI + QuickBooks": what you ask, what the agent does, what comes back. The protocol underneath is MCP (Model Context Protocol), the bundle is /skills/quickbooks on MCPBundles, but the framing here is workflow-first.

Your vulnerability scanner dumps 200 CVEs. You sort by CVSS score. The CVSS 9.8 at the top gets your attention. You patch it first.

Meanwhile, a CVSS 5.0 three pages down is in active ransomware campaigns. CISA added it to the Known Exploited Vulnerabilities catalog last week. EPSS gives it an 80% exploitation probability. Nobody looked at it because it was page three.

CVSS tells you how bad a vulnerability could be. It says nothing about whether anyone is actually exploiting it. For that, you need two more data sources — and nobody combines all three in one place.

Until now. vulnerability-intelligence-mcp is an open-source MCP server that pulls from NIST NVD, CISA KEV, and FIRST.org EPSS, computes a composite risk score, and gives your AI 30 tools for CVE analysis, watchlist tracking, and scanner triage.

Stanford's Digital Economy Lab just published The Enterprise AI Playbook — a 116-page study of 51 successful enterprise AI deployments across 41 organizations, 9 industries, and 7 countries. The research team, led by Erik Brynjolfsson (one of the most-cited economists on technology), interviewed executives and project leads who deployed AI at scale and measured actual results.

The headline finding: the technology was never the hard part. In 77% of cases, the hardest challenges were invisible — change management, data quality, and process redesign. Not model selection. Not prompt engineering. Not which AI provider to use.

This post pulls out the findings that matter most for anyone building or buying AI tooling today.

The terminal is having its best year since the invention of cloud infrastructure.

Every major AI lab shipped a coding agent CLI. Every major SaaS company shipped or meaningfully updated a service CLI. And a new category is emerging — CLIs that connect the two, giving your coding agent access to production services without leaving the terminal.

We've been running MCPBundles for over a year — a platform where teams connect AI agents to production APIs. We built a CLI because we kept watching agents context-switch between writing code and needing to call Stripe, query a database, or check analytics. This guide covers everything worth installing in 2026, organized by what it actually does for you.

OpenClaw — the open-source personal AI assistant with over 340,000 GitHub stars — now supports MCP. That means it can connect to any MCP server and use external tools as first-class capabilities. Your personal AI can go from answering questions to actually doing things across your services.

We've been watching OpenClaw's growth since late 2025. It runs on your hardware, works with Claude, GPT-4, Gemini, DeepSeek, and local models through Ollama, and connects to 20+ messaging platforms — WhatsApp, Telegram, Discord, Slack, Signal, iMessage. It already had 3,200+ skills on ClawHub. What it didn't have was a standardized way to reach the services those skills talked about.

MCP changes that. And MCPBundles makes it trivial.

MCP Apps look simple in the spec. Your tool returns HTML, the host renders it in an iframe, the user sees a dashboard instead of a wall of JSON. Build one app, it works everywhere.

In practice, I've shipped MCP Apps to both ChatGPT and Claude over the past few months and learned that "works everywhere" requires handling a surprising number of sharp edges — iframe sandboxing, data format differences, a picky initialization handshake, and an interactive tool-calling pattern that's barely documented anywhere.

Here's everything I've learned, with the exact code for each one.

There's a war happening on Reddit right now, and it's getting heated.

On one side: developers who believe the Model Context Protocol is overengineered middleware — that AI agents should just call gh issue create and curl like any terminal user. On the other: engineers running MCP in production who say the skeptics will inevitably reinvent every feature MCP provides, just worse.

Both sides are partially right. But the debate itself is framed wrong.

I spent the last day using our MCPBundles CLI to search Reddit via MCP tools — browsing posts, pulling comment threads, analyzing arguments — all through authenticated MCP tool calls executed from the command line. The irony was not lost on me: I was using CLI to call MCP to read arguments about whether we need MCP or CLI.

The answer, as it turns out, is both. But not in the way most people think.

We ran into a problem a few weeks ago that none of our tools could solve. It wasn't a technical problem — the code was fine, the infra was fine. We just needed someone to go do a thing on a website. Sign up, click around, grab some information, paste it into a form. Repeat a bunch of times.

AI couldn't do it. The sites had captchas, email verification, multi-step flows. We tried browser automation and it broke immediately. We needed a person.

So we thought: what if our AI agent could just hire one?

Most Obsidian MCP servers give you six tools: read a file, write a file, search, list, patch, delete. Basic CRUD over Markdown. That's table stakes.

This one does things the others can't. Your AI sees images in your vault — diagrams, whiteboard photos, screenshots — through actual vision, not file paths. It traverses your wikilink graph and finds orphaned notes nothing links to. It edits a specific section of a document by heading or block reference without overwriting the rest. It lists every open task across your entire vault. It runs Obsidian commands directly from the command palette.

It works with Claude Desktop, ChatGPT, Cursor, Windsurf, or any MCP client. No npm install, no local server, no JSON config. One remote URL and your AI has the tools.

The Glama directory lists 22,775 MCP servers as of May 2026. Most are weekend projects. Some are brilliant. BlueRock Security found 36.7% of public MCP servers carry SSRF vulnerabilities, 41% have no authentication at all, and only 8.5% use OAuth — so a "list of every MCP server" is not a useful list.

This guide is the opposite: the ~80 servers that real teams run in production, grouped by job. Four to five of them will cover 80% of what you ask your AI to do. We've been running MCPBundles for over a year — a platform where teams connect their AI agents to production APIs — and have tested, wrapped, and maintained MCP servers for hundreds of services. This is what we've learned about which ones are worth your time, what to skip, and why.

Claude Code ships with built-in MCP (Model Context Protocol) support. Add external tools — databases, APIs, SaaS platforms — directly from the terminal with claude mcp add. This page covers every command, config option, and common fix.