Social feeds are where conversations, customers, and culture show up first. If your AI can only read static docs, it is blind to the channels people actually use. MCP servers bridge that gap: they expose platform APIs as tools your agent can call — read threads, run searches, pull analytics, and (where you allow it) post or react — with credentials and scopes you control instead of ad hoc scripts.

This post maps each major platform to what exists on MCPBundles versus what you still wire up yourself, so you can plan one architecture instead of ten side projects.

Discord​

On MCPBundles: 13 tools — messages, threads, reactions, pins, and server management workflows your agent can drive through structured calls. Authentication is OAuth2 with a bot model, so access stays explicit and revocable.

Why it matters: Community support, dev relations, and internal team servers all live on Discord. MCP gives your agent the same surface a well-scoped bot would — without you maintaining custom glue for every client.

Go deeper: Discord MCP Server · Discord MCP Server blog post

Reddit​

On MCPBundles: 36+ tools — browse, search, post, comment, vote, subscribe, and message flows, with OAuth2 and three permission tiers so you can start read-only and expand only when the workflow needs it. Full read/write is available at the appropriate tier.

Why it matters: Reddit is a primary source for public sentiment, niche expertise, and support escalations. Tooling that mirrors the real API beats brittle scraping for anything you want to run repeatedly.

Go deeper: Reddit MCP Server · Reddit MCP Server blog post

X / Twitter​

On MCPBundles: 24+ tools — full-archive tweet search, engagement analytics, follower graphs, lists, and bookmarks, depending on how you authenticate. Bearer token (app-level) supports strong read-only workflows; OAuth2 unlocks read and write where your policy allows it.

Why it matters: X remains the real-time pulse for news, brands, and support. Your agent needs search and graph tools, not just a single “latest tweet” endpoint.

Go deeper: X MCP Server · X / Twitter MCP Server blog post

YouTube​

On MCPBundles: No provider yet. The platform is usually reached through the YouTube Data API; community MCP servers wrap that API with tools such as video search, channel metadata, playlist listing, and comment retrieval.

Official MCP from Google: No — there is no first-party YouTube MCP product; integrations are third-party or self-hosted.

Why it matters: Long-form video and comments are a distinct data layer from short posts. When MCPBundles adds a hosted path, expect the same pattern: OAuth, clear quotas, and tools aligned to API reality.

WhatsApp​

On MCPBundles: No provider yet. Serious automation runs through Meta’s Business / WhatsApp Business API — outbound messages, templates, and account management — not consumer hacks.

Official MCP from Meta: No.

Why it matters: WhatsApp is default communication in many markets; demand for agent-safe messaging is climbing. A future MCP layer will need Business API compliance from day one.

Telegram​

On MCPBundles: No provider yet. The Telegram Bot API is approachable; community MCP servers typically cover send/receive messages, group administration, and inline bot patterns.

Official MCP from Telegram: No.

Why it matters: Bots are already a native concept on Telegram — MCP is a natural fit once credentials and hosting are centralized.

Instagram​

On MCPBundles: No provider yet. Programmatic access for brands flows through the Meta Graph API for business accounts: publishing, insights, comments, and stories where permitted.

Official MCP from Meta: No.

Why it matters: Instagram is visual distribution plus social proof; agents need insights and moderation hooks, not just image URLs in a chat window.

Substack​

On MCPBundles: 4 tools — browse any publication's posts, read full article content with HTML body, explore all 31 categories, and access your personalized reader feed. Authentication via session token from substack.com/settings.

Official MCP from Substack: No.

Why it matters: Newsletters are a parallel social graph to feeds; sales, PR, and research workflows care about who publishes and how big their list is.

Go deeper: Substack MCP Server · Substack MCP Server blog post

TikTok​

On MCPBundles: No provider yet. TikTok’s APIs cover areas such as content publishing and analytics for approved developers; any MCP layer maps onto those contracts.

Official MCP from TikTok: No.

Why it matters: Short video is its own engagement loop; when MCP catches up, expect tools centered on upload, status, and performance series — not generic “scrape the app.”

Pinterest​

On MCPBundles: No provider yet. Interest in Pinterest + MCP is rising quickly; future integrations would lean on Pinterest’s developer APIs for boards, pins, and analytics where available.

Official MCP from Pinterest: No.

Why it matters: High-intent discovery traffic differs from chatter on X or Reddit; tooling should reflect saves, boards, and catalog-style metadata.

At a glance​

The MCPBundles advantage​

One hub, many networks. Where MCPBundles hosts the provider — today Discord, Reddit, X, and Substack — you enable bundles once, attach credentials per workspace, and your AI sees a single MCP surface. No separate config file per platform, no juggling four OAuth flows across four local processes for the same agent session.

Scoped power. Read-only versus write-capable paths differ by platform (X bearer vs OAuth, Reddit tiers, Discord bot scopes). MCPBundles keeps that explicit so production agents do not accidentally inherit posting rights.

Room to grow. YouTube, WhatsApp, Telegram, Instagram, TikTok, and Pinterest are the next frontier; this roundup will age — bookmark it and watch the catalog as new hosted providers land.

FAQ​

Which social media platforms have MCP servers?​

Any platform with a documented API can have an MCP server built on top — usually community or hosted. On MCPBundles today, you get hosted MCP tools for Discord, Reddit, X (Twitter), and Substack author intelligence. YouTube, WhatsApp, Telegram, Instagram, TikTok, and Pinterest do not have MCPBundles providers yet; you would rely on community servers or custom code until those ship.

Can AI post to social media via MCP?​

Yes, when the integration and credentials allow writes. On MCPBundles, Reddit supports posting and engagement at the appropriate OAuth tier, X supports read and write via OAuth2 (Bearer-token mode is read-oriented), and Discord uses bot OAuth for channel actions your scopes permit. Always match credential scope to the least privilege the workflow needs.

Is there an official Twitter, Reddit, or Discord MCP?​

No. X (Twitter), Reddit, and Discord do not ship vendor-maintained MCP servers for third-party AI clients the way some developer platforms ship reference integrations. MCPBundles provides hosted MCP tools that call each platform’s APIs using credentials you configure — see the linked skill pages and deep-dive posts for each.

What’s the best MCP server for social media monitoring?​

It depends which surface you monitor. For broad public discussion, Reddit and X toolsets on MCPBundles are the strongest hosted options (search, threads, graphs, lists). For community servers, Discord is the right fit. For newsletters and authors, use Substack author intelligence. Combine them through one MCPBundles hub so the same agent can cross-reference signals without separate server sprawl.

Substack is one of the largest homes for independent newsletters: journalists, analysts, founders, and operators build serious audiences there — often six figures for top writers. But the platform does not ship an official MCP server, and direct API access is thin. That leaves a gap between "read a Substack link in the chat" and "have the AI systematically research, compare, and monitor publications."

MCPBundles closes that gap with a hosted Substack provider (substack) exposing 4 MCP tools — browse any publication's posts, read full article content with HTML, explore all 31 Substack categories, and access your personalized reader feed.

What Your AI Can Do​

Read any publication​

Discover & explore​

Personalized feed​

Real Workflows​

"Read the latest posts from a competitor's Substack."

Your AI calls substack_get_posts with the publication subdomain, gets back titles, dates, and reaction counts. Then substack_get_post on the most-engaged posts to read the full content and summarize themes, positioning, and audience response.

"Compare how two fintech newsletters cover the same topic."

substack_get_posts on both subdomains, filter by date range, then substack_get_post on relevant slugs from each. The AI reads both and produces a side-by-side comparison of framing, depth, and audience engagement.

"What's trending in the Technology category on Substack?"

substack_get_feed with tab: technology surfaces what Substack is promoting in that vertical — publications, posts, and trending writers with their leaderboard positions and bestseller tiers.

"Monitor my Substack feed for posts about AI agents."

substack_get_feed returns your personalized feed. The AI filters for relevant topics across your subscriptions and produces a digest of what your followed writers are saying.

"Research a journalist's Substack before pitching them."

substack_get_posts on their publication subdomain to see what they write about and how much engagement they get. Then substack_get_post on their recent articles to understand their tone, topics, and audience before outreach.

How It Works​

1. Enable the Substack bundle on MCPBundles
2. Add your session token from substack.com/settings — this is your Substack session cookie
3. Connect your AI client (Claude, ChatGPT, Cursor, or any MCP host) to your MCPBundles workspace
4. Ask your agent in natural language — e.g. "Read the latest posts from tonylewislondon.substack.com and summarize them"

The session token enables your personalized feed and author lookups. Publication browsing and post reading work for any public Substack content.

Key Concepts​

• No official Substack MCP — MCPBundles fills the gap with a maintained, hosted tool surface.
• Full post content — Not just titles and links. substack_get_post returns the complete HTML body, so your AI can read and reason over the full article.
• Any publication — Browse posts from any Substack by subdomain. No need to be subscribed.
• 31 categories — Discover the entire Substack taxonomy for systematic exploration.
• Personalized feed — Your subscriptions, recommendations, and trending content in one API call.
• Session token auth — Get your token from substack.com/settings. It expires after ~30 days.

FAQ​

Is this the official Substack MCP?​

No. Substack does not publish an official MCP server. MCPBundles provides a hosted integration that calls Substack's API on your behalf using your session token.

Can my AI read full Substack posts?​

Yes. The substack_get_post tool returns the complete HTML body of any public post — not just a preview or excerpt. Paid-only posts return truncated content unless you're subscribed.

Do I need a Substack account?​

A session token from substack.com/settings enables all features including your personalized feed and author lookups. Publication browsing and post reading work for any public content even without authentication.

What is the session token?​

It's your Substack session cookie, available at substack.com/settings. It authenticates your requests and provides access to your personalized feed. Tokens expire after approximately 30 days — get a new one from the same page when needed.

Can I read any publication or just my own?​

Any publication. Provide the subdomain (e.g. tonylewislondon for tonylewislondon.substack.com) and the tools return posts and content from that publication. You don't need to be subscribed to browse public posts.

arXiv hosts more than 2.4 million papers across physics, mathematics, computer science, quantitative biology, and more. Researchers, ML engineers, and academics increasingly want the same thing from their AI stack: search papers, read abstracts, follow citations, track new work in a field, and go deeper into full text — all without leaving the chat.

arXiv does not ship an official MCP server. Community implementations exist on GitHub, but they vary in quality, transport, and maintenance. MCPBundles hosts a dedicated arXiv provider (arxiv) with 4 MCP tools backed by the official arXiv Atom API — no API key required, no self-hosting, no config files. Enable the bundle, connect your AI client, and start searching.

What Your AI Can Do​

Search & discovery​

Query syntax (the operators agents use most)​

arXiv's search syntax is what makes the search tool powerful beyond simple keywords:

• All fields: all:transformer — searches title, abstract, authors, comments
• Title: ti:"attention is all you need" — exact phrase in title
• Author: au:"Vaswani" — author name search
• Category: cat:cs.CL — restrict to a subject class
• Abstract: abs:"reinforcement learning" — abstract-only search
• Boolean: AND, OR, ANDNOT — combine clauses
• Date range: submittedDate:[20240101 TO 20240331] — filter by submission window

Combine operators: e.g. cat:cs.AI AND ti:"large language model" AND submittedDate:[20250101 TO 20260401] for targeted discovery.

Popular arXiv Categories​

Agents that use the cat: filter should know these common labels:

• cs.AI — Artificial Intelligence
• cs.CL — Computation and Language (NLP)
• cs.CV — Computer Vision and Pattern Recognition
• cs.LG — Machine Learning
• stat.ML — Machine Learning (Statistics)
• cs.CR — Cryptography and Security
• cs.SE — Software Engineering
• math.OC — Optimization and Control
• q-fin — Quantitative Finance

These classes appear constantly in LLM, RLHF, vision, and systems papers — good defaults for filters and alerts.

Real Workflows​

"Find the latest papers on RLHF from the last month."

Your agent runs arxiv_search_papers with all:RLHF AND cat:cs.CL, sort_by: submittedDate, and a submittedDate range. Returns titles, authors, abstracts, and PDF links. Summarize the top results into a digest without leaving the chat.

"Read the full text of arXiv:2402.05964 and summarize the key contributions."

arxiv_get_paper to pull metadata and abstract, then arxiv_read_paper to fetch the complete PDF. The AI reads the paper inline and provides a structured summary — not just the abstract, the full content.

"Compare these three papers on diffusion models."

arxiv_get_papers with 2402.05964,2302.14017,2301.00001 fetches all three in a single request. The AI gets titles, abstracts, authors, and categories side by side for a comparative analysis without three separate calls and rate-limit waits.

"Track new papers from a specific research group this quarter."

arxiv_search_papers with au:"Hinton" and submittedDate:[20260101 TO 20260401], sorted by submission date. The agent returns the latest work and can cross-reference with previous results you've saved.

"Literature review on transformer architectures since 2023."

Run arxiv_search_papers for architecture keywords and recent dates, then for each shortlisted paper call arxiv_read_paper to go beyond abstracts. Pair with Semantic Scholar on MCPBundles for citations and related work to widen the review systematically.

Complementary Research Tools on MCPBundles​

arXiv gives you the preprint corpus. For a complete research workflow, pair it with other hosted providers:

• Semantic Scholar — 200M+ papers with citation graphs, author profiles, and recommendations. Enrich an arXiv hit with citation counts and related work.
• Europe PMC — Biomedical literature when your thread crosses from CS preprints into life sciences.
• Zenodo — Open-access research outputs, datasets, and software-linked publications for artifacts and supplementary material.

Practical combo: search on arXiv, pull citations through Semantic Scholar, and retrieve datasets from Zenodo — all in the same conversation, one MCPBundles hub.

How It Works​

1. Enable the arXiv bundle on MCPBundles
2. No credentials needed — arXiv's API is public. Just enable the bundle and you're ready.
3. Connect your AI client (Claude, ChatGPT, Cursor, or any MCP host) to your MCPBundles workspace
4. Ask your agent in natural language — e.g. "Search arXiv for papers on MCP and tool use in LLMs, sort by most recent"

arXiv enforces rate limits of roughly 1 request per 3 seconds. MCPBundles respects these limits. For bulk lookups, use arxiv_get_papers (batch up to 20) instead of sequential single calls.

Key Concepts​

• No auth required — arXiv's API is free and public. No API key, no OAuth, no signup. Enable the bundle and go.
• Full PDF reading — Not just metadata and abstracts. arxiv_read_paper delivers the actual PDF as an embedded resource your AI can read.
• Batch efficiency — arxiv_get_papers fetches up to 20 papers in one call, avoiding the 3-second rate limit penalty between sequential requests.
• Advanced query syntax — Category filters, date ranges, author search, boolean operators — the same power as the arXiv API, accessible through natural language prompts.
• Complements citation tools — arXiv is the discovery layer. Pair with Semantic Scholar for citation graphs and impact metrics.

FAQ​

Is this the official arXiv MCP?​

No. arXiv does not publish an official MCP server. MCPBundles hosts a dedicated arXiv provider that calls the official arXiv Atom API — the same public API that powers third-party arXiv tools.

Do I need an API key?​

No. The arXiv API is free and does not require authentication. You enable the arXiv bundle on MCPBundles and start searching immediately — no credentials to configure.

Can my AI read full papers, not just abstracts?​

Yes. The arxiv_read_paper tool downloads the full PDF and returns it as an embedded resource. On clients that support PDF reading (like Claude), the AI can read and reason over the complete paper content, not just the abstract.

What about rate limits?​

arXiv enforces rate limits of roughly 1 request per 3 seconds. MCPBundles handles this with built-in delay between calls. For batch lookups, use arxiv_get_papers to fetch up to 20 papers in a single request instead of calling arxiv_get_paper 20 times.

What is the difference between arXiv and Semantic Scholar MCP?​

arXiv is the preprint corpus — what dropped today, what a specific author published, what's in cs.CL this month. Semantic Scholar is a broad literature graph with citations, author profiles, and recommendations across all venues. Use arXiv for discovery and full-text reading; use Semantic Scholar for citation context and related work. Both are available as hosted bundles on MCPBundles.

MCP Apps are interactive tool outputs that render as rich HTML and CSS inside supported AI clients. Instead of stopping at plain text or raw JSON, an MCP tool can return a full, styled experience: dashboards, charts, forms, data tables, and cards that users can read and interact with in context.

The Model Context Protocol already made it possible for assistants to call tools against live systems. MCP Apps extend that idea: they turn those calls into something that feels closer to a small application than a chat transcript. For anyone searching mcp app or mcp apps, this guide explains what that means technically, why teams care, and how to build one.

Traditional MCP tools return text. AI clients display text well. Many real workflows still need visual output — a stock dashboard, a compliance summary, a project status board, a customer profile. MCP Apps bridge the gap between “the model called a tool” and “the user got something they can actually use on screen.”

What MCP Apps Are (and What They Are Not)​

An MCP App is not a separate product category bolted onto MCP. It is a pattern: your tool’s response includes HTML (or HTML produced by a library) that the host recognizes and renders in a sandboxed presentation surface (for example, an iframe). The assistant still invoked a normal MCP tool; the difference is the payload shape and how the client displays it.

What MCP Apps are not:

• They are not a replacement for MCP tools — they are a richer output from those tools.
• They are not guaranteed to render the same in every client; host support varies (see Host compatibility below).

Why MCP Apps Matter for Agents and Teams​

Agents excel at reasoning over data, but humans still digest layout, hierarchy, and visuals faster than walls of text. When the same tool run can produce:

• trend lines instead of comma-separated numbers,
• color-coded risk instead of prose paragraphs,
• tabular drill-down instead of nested JSON,

…the conversation stays in the assistant while the artifact carries the detail. That matters for analytics, operations, sales workflows, and anywhere “show me” beats “tell me.”

Search interest around mcp app and mcp apps has grown sharply as teams adopt MCP across Claude, ChatGPT, and developer tooling — people want visual, interactive results from their agent workflows, not only token streams.

How MCP Apps Work: Architecture in Four Steps​

1. Tool execution — In your MCP tool’s handle_call, you return HTML. That may be hand-authored markup or HTML generated by a library such as mcpbundles-app-ui (see the next section).
2. Wire format — The AI client receives this content as a special content type associated with app-style UI (exact details depend on the host’s MCP implementation).
3. Sandboxed rendering — The client loads the HTML in a sandboxed iframe (or an equivalent isolated surface), so styling and layout apply without escaping into the host chrome.
4. User experience — The end user sees charts, cards, and structured layout — an mcp applications-style view — instead of a single monospace blob.

The platform or host is responsible for where that iframe lives and which capabilities (scripts, network, storage) the sandbox allows. Your job as the author is to produce valid, self-contained HTML that behaves well inside those constraints.

The mcpbundles-app-ui Library​

mcpbundles-app-ui is an open-source Python package for building MCP App UIs with consistent layout and theming:

• Install: pip install mcpbundles-app-ui
• Core types: App, LightTheme, Stats, Stat, Card
• Purpose: Responsive layout, theming, and patterns that work across clients that support MCP Apps (e.g. Claude and ChatGPT), so you spend less time fighting CSS and host quirks.

You subclass App, compose Stats, Card, and your own HTML fragments, and return the generated markup from handle_call. The library is aimed at mcp tools ui authors who want maintainable structure rather than one-off inline strings for every tool.

Examples of Real MCP Apps​

These are representative patterns teams implement once HTML output is available:

1. Stock Intelligence Dashboard — Real-time quotes, price charts, analyst ratings, and key financial metrics in one visual surface instead of disconnected text blocks.
2. SEO Performance Report — Traffic trends, top landing pages, and keyword movements as cards and simple charts for quick scanning.
3. Customer Profile Card — CRM fields rendered as a styled contact card with recent deal history and timeline cues.
4. Code Execution Results — Formatted output with syntax highlighting, optional charts, and data tables when the agent runs analysis or scripts.
5. Compliance Screening Report — Sanctions or watchlist-style results with risk indicators, match summaries, and clear hierarchy for reviewers.

Each example shares the same idea: structure + visual encoding so the user grasps outcomes faster than from unstructured text alone.

Building an MCP App (High-Level)​

1. Install mcpbundles-app-ui in your tool’s environment.
2. Subclass App and configure theme (e.g. LightTheme) as needed.
3. Compose the UI with Stats, Stat, Card, and any additional HTML your product needs.
4. Return the resulting HTML string from your tool’s handle_call.
5. Rely on the host to render that HTML in its sandboxed app surface when supported.

On hosts without iframe-style app rendering, users may still see a text-oriented representation of the tool result — plan copy and fallbacks accordingly.

Host Compatibility: Claude, ChatGPT, and IDEs​

Treat mcp ui as progressive enhancement: the tool should remain correct when only text is shown, and delight when the host renders full HTML.

FAQ​

What's the difference between MCP tools and MCP Apps?​

MCP tools are callable functions exposed over MCP (inputs, execution, outputs). MCP Apps describe a class of tool outputs where the result is HTML meant for interactive or rich visual rendering in the client. Every MCP App is still delivered through an MCP tool; not every MCP tool is an MCP App.

Which AI clients support MCP Apps?​

Claude Desktop and ChatGPT support rendering MCP App HTML in sandboxed surfaces aligned with their product UX (artifacts and canvas, respectively). Many IDE-integrated MCP clients currently surface tool results primarily as text; HTML may appear escaped or flattened.

Can I build my own MCP App?​

Yes. Install mcpbundles-app-ui, subclass App, build your layout, and return HTML from handle_call. Keep markup self-contained and safe for sandboxed iframes; avoid assuming browser APIs that the host disables.

Do MCP Apps work offline?​

No. MCP Apps are rendered by the client after a networked tool invocation. Without connectivity to the MCP host and backend, the tool cannot run and the HTML cannot be produced or updated.

Are MCP Apps secure?​

Hosts isolate MCP App HTML in sandboxes (commonly iframes with restricted capabilities). You should still treat app HTML like untrusted UI: avoid embedding secrets in markup, validate data before display, and follow your organization’s content security policies. Security is a shared responsibility between the tool author and the host.

Teams want X (Twitter) in the same place as the rest of their AI stack: searchable, scriptable, and safe behind the right credentials. The platform does not ship an official MCP server you can drop into Claude, ChatGPT, or Cursor. That leaves a gap between “ask the model a question about social data” and “actually query the live network with correct auth and rate limits.”

MCPBundles closes that gap with the x provider: 24+ MCP tools (and growing) backed by X API v2, two authentication paths, and a standout capability for research and brand intelligence — full-archive tweet search (the entire history of public tweets, not a rolling seven-day window).

No Official Twitter MCP — Hosted Tools on X API v2​

MCPBundles is not affiliated with X Corp. What we provide is a hosted MCP integration: your agent calls standard MCP tools; we call X’s documented REST endpoints with your stored credentials.

Pick Bearer for unattended research and monitoring. Pick OAuth when the agent should act as a signed-in user (posting, social actions, user timeline).

What Your AI Can Do​

Read — Search & discovery​

Read — Timelines, threads & social graph​

Read — Lists, bookmarks & moderation state​

Write — OAuth user actions​

Analysis & monitoring​

Additional read helpers (for example x_list_tweets in narrow listing flows) round out the bundle so agents can paginate and drill down without hand-rolled HTTP.

Search query operators (the ones agents use most)​

X’s search syntax is the difference between noisy results and signal:

• Authors & targets: from:username, to:username, @mention
• Media: has:media, has:images, has:videos, has:links
• Noise control: -is:retweet, -is:reply, is:verified
• Locale & place: lang:en, place_country:US
• Threads: conversation_id:123
• Boolean: AND, OR, NOT with quotes for exact phrases

Combine operators: e.g. "your brand" OR @yourhandle -is:retweet lang:en with a multi-year start_time / end_time range for long-horizon studies.

Real Workflows​

"Search every tweet mentioning our company in the last three years."

Your agent runs x_search_tweets with a tight boolean query, -is:retweet, and ISO8601 start_time / end_time — full archive, not a seven-day cap.

"Monitor @competitor's tweets and analyze their content strategy."

x_monitor_accounts pulls fresh posts across handles; x_engagement_analytics (and direct metric fields on tweets) summarizes what resonates.

"Find the most influential people tweeting about AI agents."

x_search_tweets for the topic, then x_fetch_user / x_fetch_user_by_username for follower counts, bios, and verification — rank by public_metrics or your own scoring.

"Build a thread analysis of the viral discussion about MCP."

Start from a root tweet or known conversation_id, then x_get_thread to walk the conversation tree and summarize themes, participants, and peak engagement.

How It Works​

1. Open the X (Twitter) bundle on MCPBundles.
2. Choose FIELDS (Bearer) for read-only full-archive search, or OAuth 2.0 for read + write; complete credential setup in the product UI.
3. Connect your AI client to your MCPBundles Hub URL and enable the bundle for your workspace.
4. Prompt with concrete operators and time bounds — e.g. "Full-archive search for mentions of our product since 2023, excluding retweets, English only."

Bearer access is ideal for data pipelines and research. OAuth is required for any action that must appear from a human account (posts, likes, follows).

FAQ​

Is this the official Twitter / X MCP?​

No. X does not publish an official MCP server for third-party clients. MCPBundles implements MCP tools that call X API v2 on your behalf using your credentials.

What is the difference between App Bearer Token and OAuth?​

Bearer (FIELDS) is application-level, read-oriented access — strong fit for full-archive search and large-scale read workflows without a user login loop. OAuth 2.0 (PKCE) ties tools to a specific X account, which unlocks posting, likes, retweets, follows, bookmarks, and other user-context endpoints per your app’s approved scopes.

Can my AI post tweets?​

Yes, when you connect with OAuth and your developer app includes the write scopes X requires. Read-only Bearer tokens cannot post.

What is full-archive search?​

It is access to X’s full-archive search endpoint (tweets/search/all at the API level): public tweets across history, subject to your developer project tier, query rules, and X’s policies — contrasted with recent-only search that covers roughly the last seven days.

What about rate limits?​

Throughput and quotas are governed by X API v2 and your project / product tier. MCPBundles does not bypass X limits; heavy jobs should paginate with next_token, use narrower queries, and spread work over time. See X’s current developer documentation for endpoint-specific caps.

Reddit is one of the web’s largest public discussion graphs: subreddits, threads, votes, and millions of daily posts. Teams use it for community support, product feedback, developer relations, and research. But wiring that into an AI workflow today usually means brittle scripts or one-off bots — not something you can hand to Claude, ChatGPT, or Cursor with clear boundaries.

Reddit does not ship an official MCP server. Community implementations tend to be thin or bot-shaped: enough to post a link, not enough to explore, reason, and act with structured tools. MCPBundles closes that gap with a hosted Reddit provider (reddit) that exposes 36+ MCP tools behind Reddit OAuth2 and three explicit permission tiers, so your agent gets the API surface it needs without over-scoping credentials.

Beyond Basic Bots: What MCPBundles Adds​

MCPBundles is not a scraper or a single-purpose posting script. The Reddit bundle maps Reddit’s API into first-class MCP tools: browse and search posts, pull subreddit metadata and rules, read wikis, inspect user history, manage your account views (saved, votes, multis), handle inbox and messages, and — when you choose a higher tier — submit posts and comments, vote, edit, delete, subscribe, and more. Everything runs through proper Reddit OAuth scopes with tiered consent, not a shared API key you hope nobody misuses.

What Your AI Can Do​

Read & discovery​

Your account (authenticated)​

Messaging​

Write & engagement​

Exact availability of each write tool follows the permission tier you authorize at connect time (see below).

Permission tiers​

Pick the smallest tier that matches the workflow. Research and monitoring rarely need Full Access; community engagement and support bots need it only when they must post or DM.

Real Workflows​

"Monitor r/programming for posts mentioning our product"

Your AI runs search_posts (and browse_posts where needed), filters titles and bodies for your product name or domain, and returns a shortlist with links — ideal for a daily digest or triage queue.

"Summarize the top posts in r/machinelearning this week"

browse_posts with an appropriate sort, then get_post_details on the top threads for full text and comment signal, producing an executive summary without leaving the chat.

"Reply to every unanswered question in r/learnpython that I can help with"

browse_posts and get_post_details to find threads with no replies (or shallow threads), draft answers in context, then submit_comment only where you explicitly want action — still gated by Full Access and your own review habits.

"Track my karma and see which of my comments got the most engagement"

get_my_karma, get_my_profile, and user-history tools (get_user_comments / overview-style reads) let the AI correlate activity with scores over time.

How it works​

1. Enable the Reddit bundle on MCPBundles
2. Complete OAuth2 with Reddit and select a permission tier (Read Only, Read + Engage, or Full Access)
3. Connect your MCP client (Claude, ChatGPT, Cursor, CLI, etc.) to your MCPBundles workspace
4. Ask your agent in natural language — e.g. "Search Reddit for posts about our launch in the last 24 hours"

Reddit applies rate limits; MCPBundles’ Reddit integration is documented around 60 requests per minute — plan batching and caching for high-volume monitors.

Key concepts​

• No official Reddit MCP — MCPBundles fills the gap with a maintained, hosted tool surface.
• OAuth2 + scopes — Credentials are Reddit tokens with scopes that match your tier; not a single mega-key for every feature.
• Tiered trust — Read Only for research; Engage when the agent should vote or save; Full Access only when it must post, comment, or message.
• Structured tools — Each capability is a named MCP tool (browse, search, vote, submit, etc.), not free-form HTML parsing.
• Rate limits — ~60 req/min; design workflows to avoid hammering listing endpoints in tight loops.

FAQ​

Is this the official Reddit MCP?​

No. Reddit does not publish an official MCP server. MCPBundles provides a hosted Reddit integration with OAuth2 and tiered tools so MCP clients can use Reddit like any other provider on the platform.

What permission tier should I choose?​

Use Read Only for search, monitoring, and summaries. Add Read + Engage if the agent should vote, save, or subscribe on your behalf. Choose Full Access only when it must submit posts or comments, send messages, or edit/delete content.

Can my AI post to Reddit?​

Yes, when you authorize Full Access and the underlying Reddit account has permission to post in the target subreddit (rules, bans, and automoderator still apply). Lower tiers intentionally block posting.

Is there rate limiting?​

Yes. Reddit enforces API rate limits; expect on the order of 60 requests per minute for typical usage. Space out bulk reads and avoid redundant get_post_details calls when a lighter tool suffices.

Can I access private subreddits?​

Only if the authenticated Reddit account is a member and Reddit’s API returns that content for those OAuth scopes. The MCP tools do not bypass Reddit’s access controls.

Grafana is where engineering teams go to understand what's happening in their infrastructure. Dashboards, alerts, logs, metrics — it's all there. But when something goes wrong at 3am, the workflow is still manual: open Grafana, find the right dashboard, scan the panels, correlate timestamps, dig into logs.

MCP changes that. With a Grafana MCP server, your AI agent can search dashboards, pull panel data, read alert states, create annotations, and explore datasources — answering "what happened?" conversationally instead of through dashboard clicking.

Grafana Has an Official MCP Server — But It's Local Only​

Grafana Labs maintains mcp-grafana — an open-source Go binary with 40+ tools. It's well-built and actively maintained. The catch: it runs locally via uvx or Docker with stdio transport. You install it on your machine and point it at your Grafana instance.

MCPBundles takes a different approach. Our Grafana tools are hosted — they run on our infrastructure and connect to your Grafana instance through the local proxy tunnel. No binary to install, no process to manage. Your AI in Claude, ChatGPT, Cursor, or any MCP client connects to MCPBundles, and we tunnel securely to your Grafana.

What Your AI Can Do​

Dashboards​

Your AI can answer "which dashboard shows our payment service latency?" without you remembering where you put it.

Datasources & Queries​

Direct datasource access means your AI can answer questions that aren't on any dashboard yet. "What's the p99 latency for the checkout service over the last hour?" — your AI writes the PromQL and gets the answer.

Alerts​

When something's on fire, your AI can tell you exactly which alerts are firing, what their conditions are, and how long they've been active.

Annotations & Events​

Annotations are how teams mark "what changed" on their graphs. Your AI can create deployment markers, incident start/end times, or any custom event — programmatically, as part of a workflow.

Real Workflows​

"Why did latency spike at 3am?"

Your AI searches for the relevant dashboard, reads the panels around that time window, pulls the alert history, and checks annotations for recent deployments. Full incident context in one conversation.

"Are any alerts firing right now?"

Alert state across all rules, grouped by severity. Your AI identifies which services are affected and pulls the relevant dashboard panels for visual context.

"Show me error rates for the payments service this week"

If there's a dashboard for it, your AI finds it and reads the data. If there isn't, your AI queries the Prometheus datasource directly with PromQL.

"Mark this deployment on all production dashboards"

Your AI creates annotations on the relevant dashboards with the deployment version, commit hash, and timestamp. The next person looking at the graphs sees exactly when the deploy happened.

"What datasources do we have configured?"

Full inventory of every datasource — type, URL, access mode, default status. Useful for understanding what data is available before building new dashboards or queries.

Connecting to Your Grafana​

Most Grafana instances run on internal infrastructure — not publicly accessible. MCPBundles handles this through the desktop proxy:

1. Install the CLI: pip install mcpbundles
2. Start the proxy: mcpbundles proxy start
3. Enable the Grafana bundle and enter your Service Account Token
4. Your AI connects to your Grafana through the secure tunnel

Grafana Cloud instances with public URLs connect directly — no proxy needed.

How Authentication Works​

Grafana uses Service Account Tokens — a dedicated auth mechanism for programmatic access:

1. In Grafana: Administration → Users and access → Service Accounts
2. Create a service account with the appropriate role (Viewer for read-only, Editor for annotations/modifications)
3. Generate a token and enter it on MCPBundles

The token inherits the service account's permissions. A Viewer token can search and read dashboards but can't create annotations. An Editor token can do both.

Setup​

1. Enable the Grafana bundle on MCPBundles
2. Create a Service Account Token in your Grafana instance
3. Add your credentials (token + optionally enable local proxy)
4. Ask your AI: "Search for dashboards related to our API"

FAQ​

How is this different from Grafana's official MCP server?​

Grafana's official mcp-grafana is a Go binary that runs locally via uvx or Docker. MCPBundles hosts the tools on our infrastructure and tunnels to your Grafana — no local process to install or manage. Both connect to the same Grafana HTTP API.

Does this work with Grafana Cloud?​

Yes. Enter your Grafana Cloud instance URL and service account token. No local proxy needed for cloud instances.

What about private/on-premise Grafana?​

That's where the local proxy shines. Run mcpbundles proxy start and your AI connects to your internal Grafana through a secure tunnel without exposing any ports to the internet.

Which datasource types are supported?​

Any datasource that Grafana can query — Prometheus, Loki, InfluxDB, Elasticsearch, CloudWatch, PostgreSQL, MySQL, and all others. The tools query through Grafana's datasource proxy, so if Grafana can reach it, your AI can query it.

Can my AI create or modify dashboards?​

Write operations depend on the service account's role. A Viewer token is read-only. An Editor or Admin token can create annotations and modify dashboards.

Snowflake doesn't have an official MCP server. For a platform where most users interact through SQL, that's a meaningful gap — every question an analyst has starts with "what tables do we have?" and ends with a query, and that's exactly the workflow MCP is built for.

MCPBundles provides a purpose-built Snowflake toolset that connects your AI agent directly to your Snowflake account through the SQL REST API. Your AI can explore databases, navigate schemas, inspect table structures, execute arbitrary SQL, manage warehouses, and review query history — all authenticated with a Programmatic Access Token.

What Your AI Can Do​

Explore Your Data Warehouse​

Your AI can orient itself in an unfamiliar Snowflake account in seconds: list databases, drill into schemas, find the tables, and describe their structure — all before writing a single query.

Execute SQL​

This isn't limited to SELECT. Your AI can run DDL (CREATE TABLE, ALTER), DML (INSERT, UPDATE, DELETE), Snowflake-specific commands (SHOW, DESCRIBE, CALL), and analytics queries. Results come back as structured rows with column metadata.

Override the warehouse, database, schema, or role per query — useful when your AI needs to run something against a different context without changing the session defaults.

Manage & Monitor​

Query history is particularly useful for debugging. Your AI can pull the last 100 queries, filter by warehouse, and identify the slow ones — with compilation time, execution time, and error messages all visible.

Real Workflows​

"What's in this Snowflake account?"

Your AI lists all databases, picks the relevant one, shows its schemas, and describes the key tables. Full orientation without opening the Snowflake console.

"How many orders did we process last week?"

SQL execution against your warehouse. Your AI writes the query, runs it, and returns the result — with the option to break it down by day, region, or product category if you ask follow-up questions.

"Which queries are running slow?"

Query history filtered by warehouse, sorted by execution time. Your AI identifies the heaviest queries and can suggest optimizations by examining the SQL and table structures.

"Create a staging table for the new data feed"

DDL execution — CREATE TABLE with the right column types, constraints, and clustering keys. Your AI can describe existing tables first to match the schema conventions already in use.

"Compare this month's revenue to last month"

Time travel queries (SELECT ... AT(TIMESTAMP => ...)) or standard date-filtered aggregations. Your AI handles the SQL, and you get the answer in natural language.

How Authentication Works​

Snowflake tools use Programmatic Access Tokens (PATs) — a Snowflake-native auth mechanism that doesn't require a full OAuth flow or key-pair setup:

1. Generate a PAT in your Snowflake account (ALTER USER ADD PROGRAMMATIC ACCESS TOKEN)
2. Enter the token and your account URL on MCPBundles
3. Optionally set a default warehouse, database, and role

PATs are scoped to the user's role permissions, so your AI can only access what that user can access. Tokens are configurable from 1 to 90 days before expiry.

Snowflake-Specific Gotchas Your AI Knows​

• Identifiers are uppercase by default — unquoted identifiers are stored as uppercase in Snowflake. The tools handle quoting automatically.
• Warehouse must be running — queries require an active warehouse. If it's suspended, Snowflake auto-resumes it (adds a few seconds of latency).
• Semi-structured data — VARIANT, OBJECT, and ARRAY types work with : and [] path notation. Your AI can query JSON-like data natively.
• Time travel — historical queries with AT(TIMESTAMP => ...) or BEFORE(STATEMENT => ...) for point-in-time analysis.

Setup​

1. Enable the Snowflake bundle on MCPBundles
2. Add your account URL and Programmatic Access Token
3. Ask your AI: "List all databases and show me what tables are in each one"

FAQ​

Is there an official Snowflake MCP server?​

No. Snowflake does not publish an official MCP server. MCPBundles connects to Snowflake through the SQL REST API using Programmatic Access Tokens.

Can my AI modify data in Snowflake?​

Yes. The SQL execution tool supports INSERT, UPDATE, DELETE, and DDL operations. Access is governed by the Snowflake role associated with your PAT — if the role can't delete, neither can your AI.

Does this work with Snowpark or Cortex AI?​

The SQL execution tool can run any SQL that Snowflake supports, including CALL statements for stored procedures and Snowpark-based UDFs. Cortex AI functions (like SNOWFLAKE.CORTEX.COMPLETE()) work as regular SQL calls.

What about multi-cluster warehouses and auto-scaling?​

The list warehouses tool shows cluster state, size, and auto-suspend configuration. Your AI can monitor warehouse utilization and help you decide when to resize or adjust auto-suspend settings.

How is this different from connecting Snowflake to a BI tool?​

BI tools give you dashboards. MCP gives your AI direct SQL access so it can answer ad-hoc questions, explore unfamiliar schemas, and run one-off analyses without building a dashboard first. They're complementary — use BI for recurring reports, MCP for the questions you think of on the fly.

Supabase ships an official MCP server that gives your AI access to the full Supabase platform — Postgres databases, authentication, storage, edge functions, and project management. It's one of the more complete official MCP implementations, covering both development workflows and production operations.

This guide covers what the Supabase MCP server offers, how to set it up, and how to access it through MCPBundles alongside your other tools.

What the Supabase MCP Server Covers​

Supabase's MCP server is broad because Supabase itself is broad — it's an entire backend platform, not just a database.

Database (Postgres)​

• Run SQL queries — SELECT, INSERT, UPDATE, DELETE against your Supabase Postgres database.
• Manage tables — Create, alter, and drop tables through your AI.
• Schema inspection — List tables, columns, types, and relationships.
• Migrations — Generate and apply database migrations.

Authentication​

• Manage users — List, create, and manage auth users.
• Auth configuration — View and update auth settings.

Storage​

• Manage buckets — Create and configure storage buckets.
• File operations — Upload, download, list, and delete files.

Edge Functions​

• Deploy functions — Create and update edge functions.
• Function management — List, inspect, and manage serverless functions.

Project Management​

• Project settings — View and update project configuration.
• API keys — Access project API keys and connection strings.
• Logs — Query project logs for debugging.

Setup Options​

Option 1: Direct Connection (npm)​

Install and run the official Supabase MCP server locally:

npx supabase mcp

Or add to your MCP client configuration:

Claude Desktop:

{
  "supabase": {
    "command": "npx",
    "args": ["-y", "@supabase/mcp-server"],
    "env": {
      "SUPABASE_ACCESS_TOKEN": "your-access-token"
    }
  }
}

Claude Code:

claude mcp add supabase -- npx -y @supabase/mcp-server

You'll need a Supabase access token from your project settings.

Option 2: Through MCPBundles​

MCPBundles hosts the Supabase MCP server alongside 500+ other tools. No npm install, no local process management.

1. Enable Supabase on MCPBundles
2. Connect with your Supabase credentials
3. Supabase tools appear alongside all your other MCP tools

Useful when you're working across multiple services — your AI has Supabase, Stripe, GitHub, and everything else through one connection.

Real Workflows​

"Create a users table with email, name, and created_at"

Your AI generates the SQL, creates the table, and sets up appropriate indexes. No pgAdmin or SQL editor needed.

"What tables exist in my database and how are they related?"

Schema inspection across all tables. Your AI maps foreign keys, identifies relationship patterns, and gives you a clear picture of your data model.

"Deploy an edge function that sends a welcome email on user signup"

Your AI writes the function, deploys it to Supabase Edge Functions, and confirms it's running. End-to-end from prompt to production.

"Show me all users who signed up in the last 7 days"

SQL query against the auth users table, filtered by creation date. Your AI formats the results and highlights trends.

"Set up a storage bucket for user avatars with a 5MB size limit"

Bucket creation with size limits and access policies. Your AI configures the bucket and generates the client-side upload code.

FAQ​

Is this the official Supabase MCP server?​

Yes. Supabase maintains the official MCP server as an npm package (@supabase/mcp-server). MCPBundles provides hosted access to the same capabilities without running a local process.

Does this give full database access?​

Yes. Your AI can run any SQL against your Supabase Postgres database — reads and writes. Use with appropriate caution on production databases.

Can my AI deploy edge functions?​

Yes. The MCP server supports creating, updating, and managing Supabase Edge Functions directly from your AI client.

Do I need to run anything locally?​

With MCPBundles, no. The server runs hosted. If you prefer running locally, npx @supabase/mcp-server works with Claude Desktop, Cursor, and other MCP clients.

Linear has one of the best official MCP servers in the ecosystem. Built in partnership with Cloudflare and Anthropic, it runs as a remote hosted server at mcp.linear.app/mcp with OAuth 2.1 authentication and 25+ tools for managing your entire project workflow.

This guide covers what the Linear MCP server can do, how to set it up across different AI clients, and how to access it through MCPBundles for a hosted experience alongside your other tools.

What the Linear MCP Server Can Do​

Linear's MCP server gives your AI full access to your project management workflow:

Issues​

• Create issues — Title, description, assignee, priority, labels, project, cycle. Your AI creates issues from natural language.
• Update issues — Change status, priority, assignee, or any field. "Move all P0 bugs to In Progress" becomes one instruction.
• Search issues — Find issues by keyword, status, assignee, label, or project.
• Get issue details — Full issue data including comments, attachments, and history.

Projects & Cycles​

• List projects — See all active projects with progress and status.
• Create projects — Set up new projects with descriptions, leads, and target dates.
• Manage cycles — View sprint cycles, add issues to cycles, track progress.

Teams & Organization​

• List teams — Browse your Linear workspace teams.
• List users — See team members for assignment.
• Search documentation — Query Linear's docs for API and feature information.

Recent Updates (2026)​

Linear's MCP server has been actively improved:

• save_issue consolidates create and update into one tool — fewer calls, less latency.
• Branch name integration — Issues include branchName for coding tools like Claude Code and Cursor to check out the right branch automatically.
• SSE deprecation — The /sse endpoint is being removed in favor of mcp.linear.app/mcp (streamable HTTP).

Setup Options​

Option 1: Direct Connection​

Add Linear's official MCP server directly to your AI client:

Claude Desktop — Settings → MCP → Add Server:

{
  "linearMcp": {
    "url": "https://mcp.linear.app/mcp",
    "transport": "streamable-http"
  }
}

Claude Code:

claude mcp add linear --transport http https://mcp.linear.app/mcp

Cursor — Settings → MCP Servers → Add:

• URL: https://mcp.linear.app/mcp
• Transport: Streamable HTTP

ChatGPT — Supports Linear MCP through the settings panel.

OAuth authentication is handled automatically — your browser opens, you authorize, and the connection is established.

Option 2: Through MCPBundles​

MCPBundles hosts the Linear MCP server alongside 500+ other tools. One connection gives you Linear plus everything else — Stripe, HubSpot, GitHub, Postgres, and more.

1. Enable Linear on MCPBundles
2. Connect via OAuth
3. All Linear tools appear alongside your other MCP tools

The advantage: one MCP endpoint, all your tools. No separate server configurations per service.

Real Workflows​

"Create a bug report for the login page crash on mobile"

Your AI creates an issue with title, description, priority (Urgent), label (Bug), and assigns it to the mobile team. Includes device details and reproduction steps from your conversation.

"What's blocking the v2.0 release?"

Your AI searches for all P0 and P1 issues in the v2.0 project, filters by status (Blocked, In Progress), and summarizes the blockers with owners and timelines.

"Move all completed issues from this sprint to Done"

Bulk status update across a cycle. Your AI lists issues in the current cycle, identifies which are marked complete, and updates their status.

"Create issues for each item in these meeting notes"

Your AI parses meeting notes, extracts action items, creates a Linear issue for each one with appropriate assignees, priorities, and project linkage.

FAQ​

Is this the official Linear MCP server?​

Yes. The server at mcp.linear.app/mcp is built and maintained by Linear, developed in partnership with Cloudflare and Anthropic. MCPBundles provides hosted access to the same server.

Do I need a paid Linear plan?​

The MCP server works with all Linear plans. Your API access follows the same permissions as your Linear account.

Can my AI create and assign issues?​

Yes. Full create, update, and search capabilities. Your AI can create issues, assign them, set priorities, add labels, link to projects, and add to cycles.

Does it work with Claude Code for branch names?​

Yes. Linear issues include branchName in the response. Claude Code and Cursor can use this to automatically check out the correct git branch for an issue.

There's no official PostgreSQL MCP server from the PostgreSQL Foundation — and there probably won't be, since PostgreSQL is an open-source project without a commercial entity pushing integrations. The community implementations that exist are mostly thin wrappers around psql — run a query, get results.

MCPBundles provides 20+ purpose-built tools that go far beyond raw SQL. Your AI explores schemas, profiles columns, analyzes index health, detects data quality issues, finds duplicates, explains query plans, and exports data — all without you writing a single SQL statement. And if you do want raw SQL, that's there too.

Beyond Raw Queries​

The difference between a SQL tool and a database intelligence tool:

What Your AI Can Do​

Explore​

Analyze​

Data Quality​

Read & Write​

Real Workflows​

"What's in this database?"

Your AI lists all tables, generates an AI narration of the schema, and shows you sample data from the key tables. Full orientation in 30 seconds.

"Are there data quality issues?"

Data quality report on each table: null percentages, constraint violations, columns with suspicious patterns. Your AI identifies the problems and suggests fixes.

"Why is this query slow?"

EXPLAIN ANALYZE on the query. Your AI reads the plan, identifies sequential scans that should be index scans, missing indexes, and join order issues. Then suggests the specific index to create.

"Find all duplicate customer records"

Duplicate detection on email + name columns with configurable similarity thresholds. Your AI groups the duplicates and recommends which to keep.

"Export last month's orders as CSV"

SQL query filtered by date, exported to CSV. One prompt, file ready to share.

Connecting to Local Databases​

Most PostgreSQL databases run on localhost. MCPBundles supports this through the desktop proxy:

1. Install the CLI: pip install mcpbundles
2. Start the proxy: mcpbundles proxy start
3. Enable "Connect via Local Proxy" when adding credentials
4. Your AI connects to localhost:5432 through the tunnel

Cloud databases (RDS, Supabase, Neon, etc.) connect directly — just enter the connection string.

Setup​

1. Enable the PostgreSQL bundle on MCPBundles
2. Add your connection details (host, port, database, user, password, SSL mode)
3. Ask your AI: "List all tables and describe the schema"

FAQ​

Can my AI modify data?​

Yes. INSERT, UPDATE, and DELETE are supported. The rollback preview tool lets your AI dry-run destructive queries first — showing exactly which rows would be affected before committing.

Does this work with local PostgreSQL?​

Yes. Install the mcpbundles CLI and run mcpbundles proxy start to tunnel from your local machine to the cloud platform. Enable "Connect via Local Proxy" in the credential settings.

What about managed databases (RDS, Supabase, Neon)?​

Direct connection. Enter the hostname, port, database, user, and password. Use SSL mode require for cloud databases.

Is there a risk of accidental data loss?​

The rollback preview tool exists specifically for this. Your AI can preview what a DELETE or UPDATE would do before executing it. And all queries run with ACID transaction guarantees.

What's the "AI description" tool?​

It generates a natural-language narration of your database schema — tables, relationships, column purposes, and entity patterns. Useful for onboarding your AI (or yourself) onto an unfamiliar database.

Discord doesn't have an official MCP server. The community implementations that exist are mostly basic bot wrappers — a few tools for sending messages and reading channels. None of them cover the full range of what you'd actually want your AI to do in a Discord server.

MCPBundles provides 13 structured tools built on the official Discord API v10 with proper OAuth2 bot authorization. Your AI reads messages, posts replies, manages threads, reacts to messages, pins important content, and looks up member profiles — all through authenticated API calls with proper permission scoping.

What Your AI Can Do​

Read and Navigate​

Write and Engage​

Thread Management​

Threads are first-class in Discord and in our tools. Your AI can:

• Create threads from existing messages (discussion threads)
• Create standalone threads (topic threads)
• Read and post in threads using the same message tools — threads are just channels with a parent

Real Workflows​

"Summarize what happened in #general today"

Your AI reads the last 50 messages from #general, identifies key discussions, and posts a summary to #daily-digest. No scrolling through hundreds of messages.

"Reply to every unanswered question in #support"

Read messages from #support, identify questions without replies, draft responses, and post them as threaded replies. Your AI handles the triage, you review if needed.

"Create a thread for each agenda item and post the meeting notes"

Your AI reads the agenda from a pinned message, creates a thread for each item, and posts relevant notes into each thread. Meeting follow-up automated.

"React with a checkmark to every message that contains a completed task"

Read messages, filter for task completion patterns, add ✅ reactions. Visual progress tracking without manual work.

How It Works​

Setup uses Discord's OAuth2 bot flow:

1. Enable the Discord bundle on MCPBundles
2. Authorize the bot to your Discord server (OAuth prompts you to select which server)
3. The bot receives scoped permissions — view channels, send messages, manage messages, create threads, pin messages, add reactions
4. Ask your AI: "List the channels in my Discord server"

The bot token is managed by the platform. Your AI makes calls through MCPBundles, which handles authentication, rate limiting (50 req/sec global), and error handling.

Key Concepts​

• Guild = Discord server. The bot joins a guild when you authorize it.
• Channel IDs and Message IDs are snowflake strings (e.g., 1234567890123456789). Your AI handles these automatically.
• Threads have their own channel ID — your AI reads and posts in them like any other channel.
• Reactions use Unicode emoji (👍, ❤️, 🔥) or custom server emoji in name:id format.
• Pagination uses before/after message IDs for efficient history traversal.

FAQ​

Is this a Discord bot?​

It uses Discord's bot infrastructure for authentication and permissions, but it's controlled by your AI agent rather than running as a standalone bot. Your AI decides when to read, post, react, or manage threads based on your instructions.

What permissions does the bot need?​

View channels, send messages, manage messages (for pins and deletions), read message history, add reactions, create threads, and send messages in threads. All scoped during the OAuth authorization step.

Can my AI read DMs?​

No. The bot only has access to server channels where it's been authorized. Private messages and DMs are not accessible.

Does this work with multiple Discord servers?​

Yes. Authorize the bot to each server you want your AI to access. The tools let you list all authorized servers and work with any of them.

Is there rate limiting?​

Discord enforces 50 requests/second globally with per-route limits. MCPBundles handles rate limiting automatically — your AI won't hit 429 errors.

MCP (Model Context Protocol) solves this by letting AI agents call Figma as a set of typed tools. Instead of pasting screenshots into ChatGPT or manually describing your component hierarchy, the AI reads your files, inspects your components, checks your variables, and posts comments — all programmatically.

There are two ways to connect Figma via MCP: Figma's official MCP server and MCPBundles' 47-tool REST API bundle. This guide covers both.

Two Ways to Connect​

1. Figma's Official MCP Server​

Figma launched their own MCP server at https://mcp.figma.com/mcp. It uses OAuth 2.1 with the mcp:connect scope and exposes Figma's capabilities through dynamically discovered tools.

Pros: First-party support, maintained by Figma, OAuth-based auth. Cons: Tool surface is defined by Figma — you get what they expose.

On MCPBundles, this is available as the Figma MCP bundle (figma-mcp). Connect with OAuth or a personal access token, and the tools are discovered automatically from Figma's server.

2. MCPBundles REST API Bundle — 47 Tools​

MCPBundles also wraps Figma's full REST API into 47 structured MCP tools organized around real design workflows. This gives you granular control over every Figma API surface — files, nodes, components, styles, variables, comments, webhooks, dev resources, activity logs, payments, and library analytics.

Pros: Full API coverage, every tool individually callable, structured parameters with validation. Cons: REST-based (not the official MCP transport).

Both bundles are available on MCPBundles — pick the one that fits your workflow, or enable both.

What AI Agents Can Do With Figma​

Access and Explore Design Files​

The foundation of any Figma integration is reading design files. AI agents can pull file metadata, navigate the node tree, and export images — all without opening the Figma UI.

Tools: figma_get_file, figma_get_file_nodes, figma_get_images, figma_get_file_meta, figma_get_file_versions, figma_get_image_fills

Key detail: The file key comes from the Figma URL — figma.com/file/ABC123/Name → key is ABC123. Node IDs come from the document tree. The AI learns this pattern once and reuses it across all file operations.

Work With Components and Styles​

Component libraries are the backbone of design systems. AI agents can inspect individual components, browse team-level libraries, and read style definitions — making design system audits and documentation automatic.

Tools: figma_get_component, figma_get_team_components, figma_get_file_components, figma_get_component_set, figma_get_team_component_sets, figma_get_file_component_sets, figma_get_style, figma_get_team_styles, figma_get_file_styles

Example workflow: "Audit our design system" → List team components → Check for missing descriptions → List styles → Cross-reference with code variables → Generate documentation.

Manage Design Variables (Design Tokens)​

Figma Variables are design tokens — colors, spacing, typography values that drive your entire design system. AI agents can read local and published variables, and even create or update them programmatically.

Tools: figma_get_local_variables, figma_get_published_variables, figma_post_variables

Why this matters: Design tokens are the bridge between design and code. AI agents that can read and write Figma Variables can keep design systems in sync, flag drift between local and published tokens, and automate token migration across files.

Collaborate via Comments​

Design reviews happen in comments. AI agents can read, post, and manage comments and reactions — enabling automated review workflows, status updates, and feedback collection.

Tools: figma_get_comments, figma_post_comment, figma_delete_comment, figma_get_comment_reactions, figma_post_comment_reaction, figma_delete_comment_reaction

Monitor Team Activity and Analytics​

For design ops teams, understanding how your component library is used across the organization is critical. AI agents can pull activity logs and library analytics to surface adoption metrics and usage patterns.

Tools: figma_get_activity_logs, figma_get_library_analytics_component_actions, figma_get_library_analytics_component_usages, figma_get_library_analytics_style_actions, figma_get_library_analytics_style_usages, figma_get_library_analytics_variable_actions, figma_get_library_analytics_variable_usages

Automation Workflows​

Design System Documentation​

Workflow: Read components → Read variables → Read styles → Generate docs

1. figma_get_team_components to list all components with descriptions
2. figma_get_published_variables to get all design tokens
3. figma_get_team_styles to get color, text, and effect styles
4. AI generates structured documentation from the data

Design Review Automation​

Workflow: Read comments → Analyze feedback → Post summary → Track resolution

1. figma_get_comments to pull all comments on a file
2. AI categorizes feedback (bug, suggestion, question, approval)
3. figma_post_comment to post a summary of open items
4. Track resolution status over time

Design-to-Code Sync​

Workflow: Read variables → Compare with code tokens → Flag drift

1. figma_get_local_variables to get current design tokens
2. Compare against your codebase token definitions
3. Flag mismatches — new tokens, changed values, missing tokens
4. figma_post_variables to update Figma if code is the source of truth

File Export Pipeline​

Workflow: Read file → Identify assets → Export at multiple scales

1. figma_get_file to read the document tree
2. Identify exportable nodes (icons, illustrations, photos)
3. figma_get_images to export each node at 1x, 2x, 3x scales
4. Download and organize by category

Connecting Figma​

Authentication​

Personal Access Token (quickest): Generate a token at figma.com/developers/api → Settings → Personal Access Tokens. Add it as a credential on MCPBundles.

OAuth 2.0 (team-wide): Figma supports OAuth with scopes for files, comments, dev resources, and webhooks. MCPBundles handles the OAuth flow — connect once, and the token refreshes automatically.

Getting Started​

1. Enable the Figma bundle on MCPBundles
2. Add your personal access token or connect via OAuth
3. Ask your AI agent: "List all components in my design system file"

The AI has access to all 47 tools and will pick the right ones based on what you ask.

Frequently Asked Questions​

Q: Which Figma bundle should I use — Figma MCP or Figma (REST)?

If you want Figma's officially supported MCP server, use Figma MCP (figma-mcp). If you want full REST API coverage with 47 individually callable tools, use Figma (figma). You can enable both — they use separate credentials.

Q: Do I need a paid Figma plan?

The REST API works with any Figma plan. Some features (library analytics, activity logs, published variables) require a Figma Organization or Enterprise plan. The tools will return appropriate errors if your plan doesn't include a feature.

Q: How do I find a file's key?

From the URL: figma.com/file/ABC123/My-Design → the file key is ABC123. The AI learns this pattern and extracts it automatically.

Q: Can AI agents modify my designs?

The current tool set is primarily read-oriented. Write operations are available for comments (post/delete), comment reactions, variables (create/update), dev resources, and webhooks. The AI cannot directly modify design elements like shapes or text on the canvas.

Q: What about rate limits?

Figma's API rate limit is roughly 100 requests per minute. The tools handle rate limiting gracefully — if you hit the limit, the error message tells the AI to wait and retry.

Ready to connect Figma to your AI workflow? Enable the Figma bundle and start exploring your design files, components, and tokens with AI — no Figma UI required.

Google Ads is where most B2B and B2C teams spend their performance marketing budget — campaigns, keywords, RSA ads, budgets, search term reports, geographic and device breakdowns. AI agents that can read and manage Google Ads campaigns can research keywords, build ad groups, write copy, analyze performance, and optimize spend — all through natural language.

MCP (Model Context Protocol) gives AI agents structured access to the Google Ads API. There are two ways to connect: Google's official MCP server and MCPBundles' 24-tool campaign management bundle. This guide covers both.

Two Ways to Connect​

1. Google's Official MCP Server​

Google released an official Google Ads MCP server (googleads/google-ads-mcp) in early 2026. It exposes two tools: list_accessible_customers (list your accounts) and search (run raw GAQL queries). GAQL (Google Ads Query Language) is powerful — you can query any resource, metric, or segment in Google Ads — but you need to know the syntax and resource names.

Pros: First-party, maintained by Google, direct GAQL access for complex queries. Cons: Requires GAQL knowledge, no structured write operations (create campaigns, add keywords, write ads), local Python + OAuth + developer token setup.

On MCPBundles, Google's official server is available as a hosted option — connect with OAuth and use GAQL without managing a local Python process.

2. MCPBundles Campaign Management Bundle — 24 Tools​

MCPBundles wraps the full Google Ads API into 24 structured MCP tools organized around real advertising workflows. Your AI creates campaigns, researches keywords, writes RSA ads, manages budgets, analyzes performance by geography and device, and reviews search term reports — all through natural language, no GAQL required.

Pros: Full campaign lifecycle (read + write), keyword research, structured parameters with validation, hosted setup. Cons: REST-based (not Google's official MCP transport).

Both options are available on MCPBundles — use Google's official server for raw GAQL flexibility, the structured bundle for campaign management, or enable both.

What Each Option Covers​

Google's official server gives you direct access to the full GAQL query surface — anything you can express in GAQL, you can query. The structured bundle trades that flexibility for ease of use: your AI doesn't need to construct GAQL strings, and it gets write operations that the official server doesn't offer.

What AI Agents Can Do With Structured Tools​

Research Keywords Before Spending​

Two tools that complement the official server's GAQL-only approach:

• Keyword ideas: Give your AI seed keywords or a URL, get back search volume, competition, CPC estimates, and related keyword suggestions. "Find keyword opportunities for our landing page" becomes actionable data.
• Keyword volume: Check exact monthly search volumes, competition index, and top-of-page CPC bids for specific keywords. The same data from Google Ads Keyword Planner — available to your AI in one call.

Build and Manage Campaigns​

Full campaign lifecycle from creation to removal:

1. Create campaign — Set name, type (Search, Display, Shopping), daily budget, and targeting. Campaigns start PAUSED by default so nothing goes live accidentally.
2. Create ad groups — Organize keywords and ads under campaigns with CPC bids.
3. Add keywords — Broad, phrase, or exact match. Add negative keywords at campaign or ad group level to control where ads don't show.
4. Create RSA ads — 3-15 headlines (30 chars each), 2-4 descriptions (90 chars each). Your AI writes the copy, the tool handles formatting and validation.
5. Update budgets — Change daily budget on any campaign.
6. Remove campaigns — Permanent removal when a campaign is done (or pause for temporary stops).

Analyze Performance​

Seven dedicated analytics tools, each returning structured data your AI can reason about:

Run Custom GAQL Queries​

For anything the structured tools don't cover, the GAQL tool gives your AI the same raw query capability as Google's official server. Use structured tools for common operations, GAQL for edge cases.

Real Workflows​

"What keywords should we target for our new product?"

Your AI calls keyword ideas with your product URL, gets back 50 suggestions with volume and CPC, filters to high-volume low-competition terms, and presents a prioritized list. No Keyword Planner UI needed.

"Create a search campaign for our spring sale"

Your AI creates a paused campaign with a $50/day budget, builds an ad group, adds 15 keywords (mix of broad and exact match), writes an RSA ad with 11 headlines and 4 descriptions, adds negative keywords to exclude irrelevant traffic. You review and enable.

"How did our campaigns perform last month by device?"

Your AI pulls device performance for the date range, spots that mobile CPC is 40% higher than desktop with the same conversion rate, and recommends a bid adjustment.

"What are people actually searching to find our ads?"

Search term report for the last 30 days. Your AI identifies wasted spend on irrelevant queries and recommends negative keywords to add.

RSA Ad Best Practices (Built Into the Skill)​

Every Google Ads connection on MCPBundles comes with a skill — structured domain knowledge your AI reads before making calls. For RSA ads, it knows:

• 11+ headlines and 4 descriptions for Good+ ad strength
• Zero pins — pinning all positions guarantees Poor strength
• Keywords in 2-3 headlines — match ad group themes
• Diverse remaining headlines — features, benefits, CTAs, social proof (not synonyms)
• Ad strength ≠ performance — Adalysis data on 1M+ ads shows no correlation between strength score and CTR/CPC

Your AI applies these patterns automatically. You describe what the ad should say, it writes copy that follows best practices.

Setup​

1. Enable the Google Ads bundle on MCPBundles
2. Connect via OAuth (one click — your Google account is linked automatically)
3. Ask your AI: "List my Google Ads accounts and show me last month's performance"

No developer token to manage, no GAQL to learn, no local Python environment to configure.

FAQ​

What's the difference between this and Google's official MCP server?​

Google's official server (googleads/google-ads-mcp) provides raw GAQL query access — powerful if you know the syntax. MCPBundles adds 24 structured tools for campaign creation, keyword management, RSA ad writing, and analytics reports. You can use both: the official server for complex GAQL queries and the structured bundle for common operations.

Can my AI create live campaigns that spend money?​

Yes, but with a safety default: all campaigns are created in PAUSED status. Your AI builds the campaign structure, you review it in Google Ads UI, and you enable it when ready. Budget updates on existing campaigns take effect immediately.

Does this work with Manager (MCC) accounts?​

Yes. If you manage multiple accounts through an MCC, provide the login_customer_id (manager account ID in XXX-XXX-XXXX format). Your AI can then access any child account under the manager.

How does keyword research work without opening Google Ads?​

The keyword ideas and keyword volume tools connect directly to Google's Keyword Planner API. Your AI passes seed keywords or a URL and gets back the same data you'd see in the Keyword Planner UI — monthly search volume, competition, CPC estimates, and related suggestions.

Is this read-only?​

No. You get full read and write access: create campaigns, ad groups, keywords, and RSA ads; update budgets and campaign settings; remove campaigns. All write operations require the adwords OAuth scope, which is requested during setup.

Every 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 is the only LinkedIn MCP server built entirely on LinkedIn's official REST API with proper OAuth 2.0 scopes. Your AI manages company pages, publishes posts with images and carousels, engages with comments and reactions, runs ad campaigns, and tracks analytics — all through authenticated API calls that LinkedIn explicitly supports.

Why the Official API Matters​

The community LinkedIn MCP servers fall into two categories:

Scrapers (e.g., eliasbiondo/linkedin-mcp-server): Use headless browsers to navigate LinkedIn's web UI. Profile scraping, search automation, connection requests. LinkedIn detects and blocks these. Your account can be restricted or banned.

Unofficial API wrappers (e.g., some repos using undocumented endpoints): These use internal LinkedIn API paths that aren't part of any public contract. They work until LinkedIn changes the endpoint — which happens regularly.

MCPBundles uses the LinkedIn Marketing API and Community Management API with OAuth 2.0 scopes (rw_organization_admin, w_organization_social, r_ads, rw_ads, etc.). These are documented, versioned, and supported by LinkedIn. Your AI's actions show up in LinkedIn's official API audit logs.

What Your AI Can Do​

Company Page Management​

Content Publishing​

Your AI creates posts for your personal profile or company page. Every content type LinkedIn supports:

The workflow for image posts is two steps: upload the image (from a URL or base64), then create the post referencing the image URN. Same pattern for documents and carousels. Your AI handles both steps automatically.

Engagement​

• Comments — Read and reply to comments on any post
• Reactions — Like, Praise, Empathy, Entertainment, Interest, Appreciation
• Edit posts — Update post text after publishing
• Delete posts — Remove posts entirely

Advertising​

Full LinkedIn Ads API coverage through the same connection:

1. Ad accounts — List accounts, check status and budget
2. Campaign groups — Top-level organizational containers
3. Campaigns — Create and manage ad campaigns with targeting
4. Creatives — Ad content linked to campaigns
5. Analytics — Performance metrics: impressions, clicks, CTR, engagement, video views

Algorithm Knowledge Built In​

Every LinkedIn connection on MCPBundles comes with a skill that includes current algorithm data your AI reads before posting:

• External links in body: 40-50% fewer impressions (March 2026 update intensified this)
• Link in first comment: Reduces penalty to 5-15%
• Image posts: 87% higher engagement vs text-only
• Carousels (PDF): 3-5x more dwell time than text — highest engagement format
• Personal > company: Personal profiles get 5x more engagement and 2.75x more impressions than company pages
• Golden hour: First 60 minutes determine amplification

Your AI applies these patterns automatically. When you say "post about our new feature with a link to the blog post," it knows to put the link in a comment, not the body. When you say "create a carousel about our product," it formats the content as swipeable slides.

The Personal + Company Page Flywheel​

The skill includes a growth strategy your AI can execute:

1. Post from your personal profile (higher reach) — text or image, no links
2. Company page reshares the personal post (builds org content library)
3. Company page posts product content — personal profile reshares with commentary
4. Both grow together: personal posts drive company page followers

Your AI coordinates this workflow across both accounts.

Why a Hosted Server Matters​

Unlike services such as Figma, Slack, or Sentry — which have released their own official MCP servers — LinkedIn has no first-party MCP offering. The community alternatives are scrapers that violate LinkedIn's ToS. MCPBundles fills this gap with a proper API-based server, and because it's hosted alongside your other MCP connections (Google Ads, HubSpot, Slack, etc.), your AI agent can coordinate cross-service workflows — draft a LinkedIn post referencing your latest campaign metrics, or create a follow-up CRM task after engaging with a prospect's comment.

Setup​

1. Enable the LinkedIn bundle on MCPBundles
2. Connect via OAuth (LinkedIn prompts for permissions)
3. Ask your AI: "List my company pages and show our follower count"

OAuth captures the necessary scopes for organization management, posting, and ads. One connection covers all three.

FAQ​

Is this safe to use? Will my LinkedIn account get banned?​

This is built on LinkedIn's official API with proper OAuth scopes — the same API that LinkedIn's own partners use. Your account won't be restricted for using official API endpoints. Scrapers and unofficial tools are what LinkedIn blocks.

Can my AI post to both my personal profile and company page?​

Yes. Your AI uses your personal URN (urn:li:person:{id}) or organization URN (urn:li:organization:{id}) as the author. It can post, comment, react, and reshare from either identity.

Why can't I see my personal posts?​

Listing personal posts requires the r_member_social scope, which LinkedIn restricts. Your AI can create and manage personal posts, but listing your feed requires organization context. Use organization_id with the list-posts tool to see company page posts.

Does this support LinkedIn ads?​

Yes. Full LinkedIn Ads API coverage: ad accounts, campaign groups, campaigns, creatives, and performance analytics. Create campaigns, manage budgets, and pull engagement metrics.

How is this different from the community LinkedIn MCP servers?​

Community servers either scrape LinkedIn's web UI (violates ToS, accounts get banned) or use undocumented internal APIs (break without notice). MCPBundles uses LinkedIn's official Marketing and Community Management APIs with versioned endpoints and OAuth.

Playwright is the industry standard for browser automation: fast, reliable, cross-browser, built for modern web apps. There are two ways to connect it to AI agents via MCP: Microsoft's official Playwright MCP server and MCPBundles' browser bundles with local and cloud deployment options.

Two Ways to Connect​

1. Microsoft's Official Playwright MCP Server​

Microsoft maintains the official @playwright/mcp server — a local Node.js package that runs a browser on your machine and exposes Playwright actions as MCP tools. It supports snapshot-based interaction (accessibility tree), screenshotting, and JavaScript evaluation. Works with Claude Desktop, VS Code Copilot, and other MCP clients via stdio.

Pros: First-party from Microsoft, actively maintained, lightweight local setup. Cons: Local install required (Node.js + npx), browser runs on your machine, no cloud option, no localhost tunneling for remote access, no network inspection or performance profiling.

2. MCPBundles Browser Bundles — 35 Tools, Local + Cloud​

MCPBundles provides Playwright-based browser automation as 35 hosted MCP tools with two deployment modes:

• Local Browser: Chrome on your machine via the MCPBundles desktop proxy — your cookies, your logins, your localhost:3000. You watch the automation happen in real time.
• Remote Browser: Cloud-hosted Chrome via Steel.dev — zero install, fresh session, with secure tunneling to reach your localhost from the cloud.

Pros: Cloud option with no local install, localhost tunnel for remote browsers, network inspection, performance profiling, cookie/storage access, hosted setup. Cons: REST-based (not Microsoft's official MCP transport).

Both approaches use Playwright under the hood. Use Microsoft's server for a lightweight local setup, MCPBundles for cloud deployment and advanced capabilities like network inspection and localhost tunneling, or use both.

Local vs Cloud Deployment​

Local Browser — Chrome on Your Machine​

The Local Browser runs a real Chrome instance on your machine via the MCPBundles desktop proxy. The AI sees exactly what you'd see — your cookies, your logins, your localhost:3000.

Setup:

pip install mcpbundles
mcpbundles login
mcpbundles proxy start

The proxy opens a Chrome window on your desktop. The AI agent controls it through Playwright's Chrome DevTools Protocol (CDP). You can watch the automation happen in real time.

Best for: Testing local dev servers, automating authenticated workflows (you're already logged in), visual QA on localhost, form filling against internal tools.

Remote Browser — Chrome in the Cloud​

The Remote Browser is a cloud-hosted Chrome instance powered by Steel.dev. No local install, no Chrome on your machine, no Playwright setup. The AI gets a fresh browser session in the cloud.

Best for: Scraping public pages, testing production URLs, running automations without tying up your local machine, CI/CD integration.

Localhost access from cloud: If your AI agent needs the cloud browser to reach localhost:3000, run mcpbundles proxy expose 3000 to create a secure tunnel.

What AI Agents Can Do​

Navigate and Interact With Pages​

The core of browser automation — go to URLs, click elements, type text, fill forms. The AI uses Playwright's accessibility tree (snapshot) to find interactive elements, then acts on them by reference.

Tools: browser_navigate, browser_click, browser_type, browser_fill_form, browser_select_option, browser_hover, browser_drag, browser_press_key, browser_scroll, browser_navigate_back, browser_file_upload

How element interaction works:

1. browser_snapshot returns the page's accessibility tree — every interactive element with a unique ref
2. The AI identifies the target element from the tree
3. browser_click, browser_type, or browser_fill_form acts on the element using its ref

This ref-based approach is more reliable than CSS selectors or XPath — it works even when class names are minified or the DOM structure changes.

Capture Visual Evidence​

Screenshots and PDFs let the AI see the page visually and produce artifacts for documentation, bug reports, or visual regression testing.

Tools: browser_take_screenshot, browser_save_as_pdf, browser_snapshot

Why screenshots matter for AI: browser_take_screenshot returns an ImageContent response — the AI model can actually see the screenshot, not just get raw HTML. This enables visual QA: "Does this button look right?", "Is the layout broken on mobile?", "Compare this to the mockup."

Inspect and Debug​

Read the page's text content, monitor console messages, inspect network requests, check cookies and storage. Essential for debugging and understanding page behavior.

Tools: browser_get_visible_text, browser_console_messages, browser_network_requests, browser_get_network_request, browser_get_console_message, browser_get_cookies, browser_set_cookies, browser_get_storage

Debugging workflow: Navigate to page → Check console for errors → Inspect network requests for failed API calls → Read response bodies → Identify the issue. The AI does this entire flow in one conversation.

Run JavaScript and Custom Code​

For anything the built-in tools don't cover, the AI can run arbitrary JavaScript in the page context or execute Playwright scripts directly.

Tools: browser_evaluate, browser_run_code

browser_evaluate runs a single JavaScript expression in the page. browser_run_code runs a full Playwright script with access to the page object — loops, conditionals, multiple actions, assertions.

Performance and Device Emulation​

Profile page load performance, emulate different devices and network conditions, and test responsive layouts.

Tools: browser_performance_trace, browser_emulate, browser_resize

Session Management​

Control the browser session — manage tabs, handle dialogs, wait for conditions.

Tools: browser_tabs, browser_close, browser_wait_for, browser_handle_dialog, browser_install, browser_click_and_switch_tab

Real-World Workflows​

Automated QA Testing​

Workflow: Navigate → Interact → Screenshot → Assert

1. Navigate to the staging URL
2. Fill the login form and submit
3. Navigate through key pages (dashboard, settings, profile)
4. Take screenshots at each step
5. Check for console errors or broken network requests
6. Report findings with visual evidence

Web Scraping and Data Collection​

Workflow: Navigate → Read → Paginate → Extract

1. Navigate to the target page
2. Get visible text or evaluate JavaScript to extract structured data
3. Click "Next Page" and repeat
4. Collect and structure the data

Form Automation​

Workflow: Navigate → Fill → Submit → Verify

1. Navigate to a multi-step form
2. Fill each step with the provided data
3. Handle dropdowns, checkboxes, file uploads
4. Submit and verify the confirmation page

Visual Regression Testing​

Workflow: Screenshot → Compare → Report

1. Navigate to each critical page
2. Emulate multiple device sizes
3. Take screenshots at each breakpoint
4. Compare against baseline images
5. Flag visual differences

Localhost Development Testing​

Workflow: Navigate localhost → Test → Debug

1. browser_navigate to http://localhost:3000
2. Test the feature under development
3. Check console for errors
4. Inspect network requests to the local API
5. Screenshot the result for review

Connecting​

Local Browser​

pip install mcpbundles
mcpbundles login
mcpbundles proxy start

Enable the Local Browser bundle on MCPBundles. The proxy opens Chrome on your machine — the AI controls it directly.

Remote Browser​

No setup required. Enable the Remote Browser bundle on MCPBundles — you get a cloud Chrome session immediately.

For localhost access from the cloud browser:

mcpbundles proxy expose 3000

Frequently Asked Questions​

Q: How does this compare to Microsoft's official Playwright MCP server?

Microsoft's @playwright/mcp is a local Node.js server that runs a browser on your machine. MCPBundles' browser bundles offer the same snapshot and screenshot capabilities, plus cloud deployment (no local browser needed), localhost tunneling for remote browsers, network traffic inspection, performance profiling, and cookie/storage access. Both use Playwright — you can use either or both depending on whether you need local-only or cloud+local flexibility.

Q: Can I use this with any AI agent?

Yes. Any MCP-compatible client works — Claude Desktop, Claude Code, ChatGPT, Cursor, Windsurf, Cline, or custom agents using the MCP SDK.

Q: Local or Remote — which should I use?

Local if you need localhost access, authenticated sessions (existing cookies), or want to watch the automation live. Remote if you want zero setup, cloud scalability, or don't need localhost.

Q: Can I run headless?

The Local Browser runs a visible Chrome window so you can see what the AI is doing. The Remote Browser runs in the cloud — effectively headless from your perspective, but the AI can still take screenshots.

Q: How does the AI find elements to click?

The AI uses browser_snapshot to get the page's accessibility tree — every interactive element gets a unique ref. The AI then passes that ref to browser_click or browser_type. This is more reliable than CSS selectors because it's based on the element's role and accessible name, not its implementation details.

Q: What about authentication on remote sites?

For the Local Browser, you can log in manually first — the AI inherits your cookies. For the Remote Browser, the AI can automate the login flow (navigate to login page, fill credentials, submit). Cookies persist within a session.

Q: What's the session timeout?

Local Browser sessions last as long as the proxy is running. Remote Browser sessions expire after 2 hours — if the session expires mid-workflow, the AI re-navigates.

Ready to automate your browser with AI? Enable the Local Browser or Remote Browser bundle and start navigating, clicking, and screenshotting — all through natural language.

QuickBooks Online is where millions of businesses manage invoicing, bills, payments, and financial reporting. AI agents that can read and write QuickBooks data can automate invoice creation, pull financial reports, track overdue payments, and reconcile changes — all through natural language.

MCP (Model Context Protocol) gives AI agents structured access to the QuickBooks API. There are two ways to connect: Intuit's official MCP server and MCPBundles' 34-tool accounting bundle. This guide covers both.

Two Ways to Connect​

1. Intuit's Official MCP Server​

Intuit released an official QuickBooks MCP server on GitHub — a Node.js package with ~20 tools covering CRUD operations on core accounting entities (customers, vendors, invoices, bills, payments, estimates). It connects via stdio and handles OAuth.

Pros: First-party, maintained by Intuit, covers core entity operations. Cons: Local npm install and process required, stdio transport (Claude Desktop only).

2. MCPBundles Accounting Bundle — 34 Tools​

MCPBundles wraps the full QuickBooks Online API into 34 hosted tools covering everything in Intuit's official server plus financial reports, batch operations, change data capture, PDF generation, void/credit operations, and a SQL-like query tool. One OAuth connection, hosted — every MCP client gets access.

Pros: Full API coverage, financial reports, batch ops, hosted setup, works with any MCP client. Cons: REST-based (not Intuit's official MCP transport).

Both options work — use Intuit's server for a lightweight local setup, the MCPBundles bundle for full API coverage and hosted access, or enable both.

What Each Option Covers​

The SQL-Like Query Language​

The most powerful read tool in the bundle. QuickBooks Online has its own SQL-like query dialect:

SELECT * FROM Customer WHERE Active = true
SELECT * FROM Invoice WHERE TotalAmt > 100 ORDERBY DueDate
SELECT * FROM Vendor WHERE DisplayName LIKE '%Supply%'
SELECT * FROM Bill WHERE DueDate < '2026-04-01' AND Balance > '0'

Your AI writes these queries naturally. It supports WHERE, ORDERBY, STARTPOSITION, and MAXRESULTS. No JOINs or subqueries — but for targeted accounting lookups, it covers most use cases in a single call.

What Your AI Can Do​

Invoice Management​

The full invoice lifecycle without opening QuickBooks:

1. Create invoice — Line items, customer, due date, terms. Your AI constructs the invoice from a conversation.
2. Send invoice — Email the invoice directly to the customer from QuickBooks.
3. Record payment — Link a payment to an invoice to mark it paid.
4. Download PDF — Get a base64 PDF of any invoice for review or forwarding.
5. Void invoice — Reverse financial impact without deleting the record (audit trail preserved).

Bill & Expense Tracking​

Mirror of invoicing, but for money going out:

1. Create vendor — Add new suppliers.
2. Create bill — Record what you owe.
3. Pay bill — Record payment against a bill from a specific bank account.
4. Purchase orders — Order tracking before goods arrive.
5. Purchases — Direct expense recording without a bill.

Financial Reporting​

12+ report types available through a single tool:

"What's our P&L for Q1?" — answered in seconds, not by navigating through QuickBooks menus.

Batch Operations​

Run up to 30 mutations in a single API call. Create 30 customers, update 30 invoices, or mix operations across entity types. Your AI batches related changes automatically when it makes sense.

Change Data Capture (CDC)​

Ask QuickBooks "what changed since last Tuesday?" and get back every entity that was created, updated, or deleted. This is how sync systems work — and your AI can use it to detect drift, reconcile data, or generate change summaries.

Advanced Operations​

• Credit memos — Issue credits against customer accounts
• Refund receipts — Process customer refunds
• Journal entries — Manual accounting adjustments
• Deposits — Record bank deposits grouping multiple payments
• Transfers — Move money between accounts
• Time activities — Track billable hours per employee
• Attachments — Upload receipts, contracts, or documents linked to any entity

Real Workflows​

"Find all overdue invoices and tell me the total outstanding"

Your AI runs SELECT * FROM Invoice WHERE DueDate < '2026-04-11' AND Balance > '0', sums the balances, and groups by customer. One prompt replaces the aged receivables report.

"Create an invoice for Acme Corp — 10 hours of consulting at $200/hr"

Your AI looks up the Acme customer record, creates an invoice with one line item (10 × $200), sets net-30 terms, and sends it directly to the customer's email.

"What's our cash position?"

Balance sheet report filtered to current period, plus a cash flow statement. Your AI reads both and gives you the headline number and any notable changes.

"Sync everything that changed this week"

CDC query with a timestamp from Monday. Your AI gets back every modified customer, invoice, bill, payment, and vendor — ready for reconciliation with your other systems.

The Upsert Pattern​

Every write tool uses QuickBooks' optimistic concurrency model:

• Create: Omit id and sync_token — returns the new entity
• Update: Provide id plus a fresh sync_token from a recent read — QuickBooks rejects stale tokens to prevent overwrites
• Deactivate: Customers, vendors, and employees can't be deleted — set active: false instead
• Void: Transactions can be voided (preserves audit trail) or deleted

Your AI handles this automatically — it reads before writing to get the current sync token.

Setup​

1. Enable the QuickBooks bundle on MCPBundles
2. Connect via OAuth (QuickBooks prompts you to select the company)
3. Ask your AI: "Show me the company info and list the last 10 invoices"

The OAuth flow captures your Company ID (realm) automatically. Sandbox and production environments are supported — toggle with one checkbox.

FAQ​

How does this compare to Intuit's official QuickBooks MCP server?​

Intuit's official server covers core entity CRUD with ~20 tools via a local npm process. MCPBundles adds financial reports, batch operations, change detection, PDF downloads, void/credit operations, and a SQL-like query tool — 34 tools total, hosted. You can use both: Intuit's for lightweight local access, MCPBundles for the extended API surface.

Can my AI access my live QuickBooks data?​

Yes. After OAuth, your AI has direct access to your QuickBooks Online company data. Every tool call hits the live API. For testing, enable the sandbox checkbox to connect to an Intuit sandbox company instead.

What about multi-entity accounting?​

The SQL-like query tool supports filtering across all entity types. Your AI can query customers, invoices, vendors, bills, accounts, items, and more — each with WHERE clauses, ordering, and pagination.

Is there a sandbox mode?​

Yes. Toggle "Use QuickBooks sandbox API" in the credential settings to route all API calls to Intuit's sandbox environment. Useful for testing without affecting production data.

Can my AI send invoices to customers?​

Yes. The send invoice tool emails the invoice directly from QuickBooks to the customer. Same for estimates — create and send in two calls.

Think about how much of your day involves ad-hoc queries. "How many users signed up this week?" "What's the distribution of plan types?" "Show me the last 10 failed webhook deliveries." Each of these used to mean opening a database client, remembering the schema, writing the SQL, running it, copying the results somewhere useful. With a database MCP server, you describe what you want in plain English and the AI writes the query, runs it, and summarizes the results — in the same conversation where you asked.

We run PostgreSQL MCP as part of our daily workflow at MCPBundles. It handles ad-hoc reporting, data exploration, schema understanding, and debugging. It's the first tool we recommend to anyone evaluating MCP.

Yesterday a support engineer asked "how many workspaces are using custom bundles?" Instead of opening a SQL client, remembering the join between workspace_bundle_access and mcp_bundles, and filtering for user-created bundles — the AI wrote the query, ran it against our read-only replica, and returned the count with a breakdown by plan tier. Thirty seconds from question to answer, including the plan-tier breakdown nobody asked for but everyone wanted.

Quick reference​

Security first: credentials matter more here than anywhere else​

Before we get into the list, a word on something that makes database MCP servers different from every other category: the blast radius of a misconfigured credential is your entire database.

A bad API key to Stripe lets someone read your customer list. A bad database credential lets someone DROP TABLE users. These are not equivalent risks.

Our strong recommendation:

• Use read-only credentials by default. Create a dedicated Postgres role with SELECT-only grants. Every database on this list supports it.
• Only grant write access intentionally. If your AI agent needs to insert rows or run migrations, create a separate credential for that and enable it on a per-bundle basis.
• Encrypt credentials at rest. MCPBundles handles this automatically — credentials are Fernet-encrypted in the database and scoped per workspace. If you're self-hosting an MCP server, make sure you're not storing connection strings in plaintext config files.
• Use connection pooling. AI agents can be chatty. A pooler like PgBouncer prevents your agent from exhausting connections.

The top picks​

1. PostgreSQL — 38 tools​

The most fully-featured database MCP server on the platform, and the one we use every day. 38 tools organized across five specialized bundles:

• Data Exploration — list tables, list rows, sample data, search text, export tables
• Schema Discovery — inspect schema, get enum values, get foreign key graph, get table dependencies, list functions, list triggers
• Performance Analysis — explain query, analyze indexes, find slow queries, check missing indexes, get lock info
• Data Quality — find duplicates, find null patterns, check referential integrity, detect outliers, data quality report, validate constraints
• Development & Operations — create table, alter table, backup/restore, batch execute, rollback preview

The depth here is unusual. Most database MCP servers give you "run a query" and "list tables." PostgreSQL MCP gives you tools like explain_query (with actual EXPLAIN ANALYZE output), find_slow_queries (reads pg_stat_statements), and check_missing_indexes (analyzes table scan frequency). These are the kinds of things that normally require a DBA or a dedicated monitoring tool.

Best for: Teams already on Postgres who want their AI agent to be a genuine database assistant, not just a query runner.

2. Weaviate — 31 tools​

The strongest vector database MCP server available. Weaviate is purpose-built for AI/ML workloads — semantic search, RAG pipelines, multimodal embeddings — and the MCP integration reflects that specialization. 31 tools across four bundles:

• Core — list collections, list objects, upsert, delete, hybrid search
• Schema & Structure (8 tools) — detailed schema inspection, create collection, cross references, reference graph
• Data Quality (10 tools) — find missing vectors, find duplicates, validate properties, check vector quality, check orphaned references, validate schema compliance
• Data Exploration (8 tools) — profile collection, analyze property distribution, analyze vector distribution, sample objects, compare collections, export/backup

The data quality tools stand out. check_vector_quality analyzes the distribution and dimensionality of your vectors. find_missing_vectors catches objects that failed embedding. These are real operational concerns for anyone running a production vector database — and they're hard to inspect manually.

Best for: Teams building RAG, semantic search, or recommendation systems who need operational visibility into their vector data.

3. SQLite — 17 tools​

SQLite is everywhere — local dev databases, mobile apps, embedded analytics, Datasette instances. The MCP server provides 17 tools covering the full lifecycle: list tables, execute queries, inspect the database schema, explain queries, analyze indexes, find duplicates, find nulls, analyze table sizes, get relationships, and suggest indexes.

The suggest_indexes tool is particularly useful — it analyzes your query patterns and recommends indexes that would improve performance. For a database that doesn't have a built-in query planner dashboard, this fills a real gap.

Best for: Local development databases, Datasette-backed data exploration, embedded database inspection.

4. MySQL — 10 tools​

Solid coverage of the essentials: list tables, inspect database, list rows, sample data, execute queries, get table stats, and profile columns. The get_ai_description tool generates natural-language descriptions of your tables and columns, which is genuinely useful when you're working with a legacy schema where tbl_usr_prm_v2 could mean anything.

MySQL MCP is leaner than the PostgreSQL server — no performance analysis or data quality bundles yet — but it covers the 80% case well. If your stack runs on MySQL or MariaDB, this gets an AI agent connected to your data quickly.

Best for: MySQL/MariaDB shops that need query execution and schema exploration.

5. Supabase​

Supabase is more than a database — it's Postgres plus auth, storage, real-time subscriptions, and edge functions. The official Supabase MCP server connects to all of these, giving your AI agent access to the full Supabase platform, not just the database layer.

This is a remote MCP server that connects directly to Supabase's hosted endpoint. Tools are discovered dynamically, which means you get whatever Supabase ships without waiting for a platform update on our side.

Best for: Supabase users who want AI access to their entire backend — database, auth, storage, and functions — through one server.

6. MongoDB — 6 tools​

Document databases present a different challenge for MCP: there's no fixed schema to inspect, and the data model is fundamentally different from relational tables. MongoDB MCP handles this with tools for listing databases, listing collections, searching, fetching documents, getting AI-generated descriptions, and retrieving server info.

The tool count is lower than the relational databases, but document databases also have a simpler query surface. You don't need index analysis or foreign key graphs when your data model is self-contained documents.

Best for: MongoDB users who want AI-driven data exploration and ad-hoc querying of document collections.

7. Neon — Serverless Postgres​

Neon is serverless Postgres with branching, autoscaling, and a generous free tier. The MCP server connects via OAuth and gives your AI agent access to Neon's platform features — not just SQL queries, but branch management, project configuration, and the operational layer that makes serverless Postgres work.

If you're already on Neon, this is the right MCP server for you rather than generic PostgreSQL — you get the platform-specific capabilities on top of standard SQL access.

Best for: Neon users who want AI access to both their data and their Neon project management.

8. Turso — Edge SQLite​

Turso runs libSQL (an open-source fork of SQLite) at the edge, with replication across multiple regions. The MCP server connects to Turso's hosted endpoint, giving your AI agent access to your edge databases without managing connection strings for each replica.

Edge SQLite is a growing pattern for applications that need low-latency reads globally. Turso MCP brings that into the AI workflow.

Best for: Teams using Turso for edge-distributed SQLite who want AI access to their data layer.

Honorable mentions​

Prisma MCP​

Prisma's MCP server gives AI agents awareness of your data model through Prisma schema files. If your application already uses Prisma as its ORM, this server understands your models, relations, and migrations natively. It's less about raw SQL access and more about schema-aware development assistance.

GibsonAI​

A natural-language interface for database management. GibsonAI translates plain English into database operations, which is a different angle from the query-execution approach of PostgreSQL or MySQL MCP. Worth exploring if you want a higher-level abstraction.

PG AIGuide​

A documentation and best-practices server for PostgreSQL. This isn't a query tool — it's a reference tool. Your AI agent can look up PostgreSQL documentation, configuration recommendations, and optimization patterns. Useful as a complement to the main PostgreSQL MCP server when you're making architectural decisions.

How to get started​

The fastest path from zero to querying your database with an AI agent:

1. Pick your database server. If you're on Postgres, start with PostgreSQL MCP — it has the broadest tool coverage. If you're on a managed platform (Supabase, Neon, Turso), use their dedicated servers for platform-specific features.

2. Create a read-only credential. For Postgres: CREATE ROLE ai_reader WITH LOGIN PASSWORD 'xxx'; GRANT SELECT ON ALL TABLES IN SCHEMA public TO ai_reader; Equivalent commands exist for every database on this list.

3. Enable the bundle on MCPBundles. Add your credential, connect your AI client (Claude, Cursor, ChatGPT, or any MCP-compatible host), and start asking questions about your data.

4. Start with exploration, not execution. Ask your agent to list tables, describe the schema, and sample data before you run any analytical queries. Building schema context first leads to much better query generation.

The whole setup takes under five minutes. The time you save on the first ad-hoc query pays it back.

Browse more​

We host 19 backend and database servers across relational, document, and vector databases. The ones in this post are the standouts, but if your stack uses something we didn't cover, it's likely in the catalog.

More vertical guides​

• Best MCP Servers for DevOps — monitoring, incident management, and infrastructure servers that pair with your database layer.
• Best MCP Servers for Sales & CRM — CRM servers for teams that combine database queries with customer data.
• Best MCP Servers for Marketing Teams — analytics and SEO servers for data-driven marketing.

For the full list across all categories, see our Best MCP Servers in 2026 guide.

MCP servers change this by letting AI agents query those tools directly. Instead of navigating a Datadog dashboard, you ask your agent to pull the metric. Instead of clicking through Sentry issues, you ask it to summarize the top unresolved errors from the last 24 hours. The agent handles authentication, pagination, and response formatting — you stay in one interface.

We run MCPBundles and maintain MCP servers across monitoring (21), cloud infrastructure (19), project management (48), and developer tools (184). This guide covers the ones that matter most for DevOps and platform engineering work.

Two Saturdays ago our error rate spiked at 2 AM. Instead of opening Datadog, Sentry, and GitHub in three separate tabs, one prompt: "Show me the error rate for the API service in the last hour, the top 5 unresolved Sentry issues tagged api, and the last three merged PRs." The AI correlated the spike with a dependency update that shipped at 1:47 AM — a library bump that changed how connection timeouts were handled. Rollback PR was up in 15 minutes. Without MCP, the investigation phase alone would have taken longer than the fix.

Quick reference​

Why DevOps teams should care about MCP​

The metric that matters in incident response is MTTR — mean time to resolve. Most of that time isn't spent fixing things. It's spent finding things: which service is affected, what changed recently, who's on call, what does the error rate look like, is this related to that deploy from an hour ago.

MCP servers collapse that investigation phase. An agent with access to your monitoring, deployment, and incident management tools can pull context from all of them in a single request. "Show me the error rate spike in the payments service, the last three deploys, and any open Sentry issues tagged payments" — that's one prompt instead of three browser tabs.

The monitoring category is the most mature for DevOps use. Servers like Datadog and Sentry have deep tool coverage and handle real production workflows. CI/CD and cloud infrastructure servers are still emerging — usable, but with narrower tool sets.

Monitoring & observability​

This is where DevOps MCP servers are strongest. These servers give your agent read access to the dashboards and alerting systems you already use.

Datadog — 43 tools​

The largest monitoring MCP server on the platform. Covers metrics, dashboards, monitors, logs, APM traces, and synthetics. You can ask your agent to query a specific metric over a time range, list firing monitors, search logs by service and severity, or pull APM trace data for a slow endpoint — all without opening the Datadog UI.

43 tools is a lot of surface area. The practical sweet spot is metrics queries, monitor status checks, and log searches. Those three cover most of what you'd do during an incident.

Sentry — 13 tools (API) + Sentry MCP​

We offer two paths to Sentry. Our API-based server (sentry-api) has 13 tools covering error tracking, issue management, release tracking, and project configuration. Sentry also publishes their own MCP server (sentry-mcp) which we host — it connects directly to Sentry's infrastructure.

For most DevOps workflows, the practical use is triaging errors: "What are the top unresolved issues in the API project from the last 24 hours?" or "Show me the stack trace for issue PROJ-1234." Both servers handle this well.

Sentry API on MCPBundles → · Sentry MCP on MCPBundles →

Opsgenie — 9 tools​

Alerting and on-call management. Your agent can list open alerts, check who's on call for a given schedule, acknowledge or close alerts, and pull alert details with full context. During an incident, the ability to ask "who's on call for the platform team right now?" without logging into Opsgenie saves real time.

Pingdom — 7 tools​

Uptime monitoring. Check the status of your monitors, pull uptime percentages, and review recent outages. Straightforward but useful during "is it down?" conversations — your agent can answer immediately instead of you switching to the Pingdom dashboard.

Incident management​

When things go wrong, these servers help your agent participate in the response.

Rootly — 30 tools​

The deepest incident management server we host. Rootly covers the full incident lifecycle: create and update incidents, manage severity levels, track action items, pull retrospective data, and coordinate response workflows. 30 tools gives your agent enough capability to be a real participant in incident response — not just a viewer.

Incident.io — 14 tools​

Incident creation, status updates, role assignments, and follow-up tracking. Tighter scope than Rootly but well-structured for teams that use Incident.io as their primary response platform. Your agent can create an incident, assign a lead, and post status updates without anyone leaving their terminal or chat.

Instatus — 14 tools​

Status page management. Create and update incidents on your public status page, manage components, and track subscribers. When you've identified an outage, your agent can draft and publish a status page update while you focus on the fix.

Error tracking​

Beyond Sentry, several other error tracking servers are available for teams on different platforms.

Bugsnag — 14 tools​

Error monitoring with project and organization management. Similar scope to Sentry's API server — list errors, pull stack traces, manage projects. If your team uses Bugsnag, the MCP server gives your agent the same triage capabilities.

Rollbar — 10 tools​

Error monitoring focused on deployments. Track errors by deploy, manage items and occurrences, and integrate with your release process. Rollbar's deploy-aware grouping translates well to the MCP tool model.

Infrastructure & networking​

Cloud infrastructure MCP servers are earlier in maturity than monitoring. Tool counts are smaller, and coverage tends to focus on read operations — listing resources, checking status — rather than mutating infrastructure.

Cisco Meraki — 20 tools​

Network management for teams running Meraki infrastructure. Manage networks, devices, and configurations. 20 tools is strong coverage for a networking platform.

Fastly — 8 tools​

CDN and edge compute management. Purge caches, check service status, and manage configurations. During a CDN-related incident, being able to ask your agent to purge a specific URL pattern is genuinely useful.

Cloud platforms (MCP-native)​

We also host MCP servers from Render, Netlify, Vercel, and Cloudflare — these connect directly to each platform's infrastructure. They're particularly useful for deployment status checks and service management. Vercel and Netlify are the most mature of this group.

Engineering workflow​

DevOps doesn't happen in isolation. These servers cover the tools that sit alongside monitoring and infrastructure.

GitHub​

PR reviews, issue triage, repository management, workflow runs. Every DevOps team uses GitHub, and the MCP server lets your agent participate in code review, search issues, and check CI status. During an incident, "show me the last 5 merged PRs in the API repo" is a common query.

Shortcut — 24 tools​

Engineering project management. If your team tracks incidents, post-mortems, or infrastructure work in Shortcut, the MCP server gives your agent full access to stories, epics, iterations, and labels.

Qase — 25 tools​

Test management. Create and manage test cases, runs, and results. For platform teams that maintain infrastructure test suites or runbooks in Qase, this connects your agent to your testing workflow.

Honorable mentions​

These servers have narrower scope but fill specific gaps in a DevOps toolkit:

• NinjaOne (8 tools) — remote monitoring and management for teams managing fleets of servers or endpoints. NinjaOne →
• Turso — database management for edge SQLite deployments. MCP-native server.
• Prodvana — deployment management and release orchestration. MCP-native.
• Komodor — Kubernetes troubleshooting and monitoring. MCP-native.
• Render — cloud application deployment and management. MCP-native.

These MCP-native servers connect directly to each platform rather than going through a REST API, which means they can evolve their tool sets independently. Coverage varies — some offer full CRUD operations, others are read-only. All are available through MCPBundles with no additional setup beyond credentials.

How to get started​

The fastest path is to start with the server that matches your highest-frequency dashboard. For most DevOps teams, that's Datadog or Sentry.

1. Browse the monitoring MCP servers or developer tools catalog
2. Enable the server for your workspace — one click, then add your API credentials
3. Start with read-only queries: "What monitors are firing?" or "What are the top Sentry issues today?"
4. As you build trust in the responses, expand to write operations: acknowledging alerts, updating status pages, creating incident tickets

The monitoring servers are the safest starting point because the downside of a bad read is zero — you're just querying data. Write operations (creating incidents, acknowledging alerts) are available but worth approaching incrementally.

The state of DevOps MCP in 2026​

Monitoring is the strongest category. Datadog's 43-tool server and Sentry's dual-path coverage (API + native MCP) are both production-ready for daily use. Incident management is solid — Rootly and Incident.io have enough depth to support real response workflows.

Cloud infrastructure and CI/CD are where the gap is. The servers exist, but tool counts are smaller and coverage skews toward read operations. This will change — every major cloud provider and CI platform is investing in MCP — but today, monitoring and incident management are where DevOps teams will get the most value.

The underlying shift is real: AI agents that can pull from your monitoring stack, correlate across services, and draft incident updates will meaningfully reduce MTTR. The tools are here. The question is which ones your team reaches for first.

Browse monitoring MCP servers → · Browse developer tools →

More vertical guides​

• Best MCP Servers for Databases — PostgreSQL, Weaviate, and 6 more database servers for your data layer.
• Best MCP Servers for Sales & CRM — CRM and pipeline servers, useful when your on-call team also handles customer escalations.
• Best MCP Servers for Marketing Teams — analytics and SEO servers for growth-focused engineers.

For the full list across all categories, see our Best MCP Servers in 2026 guide.

MCP servers change this. Instead of you operating each tool, your AI agent operates them directly — pulling analytics, checking keyword rankings, sending emails, updating CRM records — all from a single conversation. No tab switching, no exports, no manual cross-referencing.

We maintain 88 marketing-category MCP servers on MCPBundles. Some of them are excellent. Some are brand new and still proving themselves. This guide covers the ones we'd actually recommend to a marketing team today, with honest assessments of what works and what's still early.

Here's what this looks like in practice. Last month our blog traffic dropped 15% week-over-week and we had no idea why. One conversation: GSC pulled the top declining pages, Ahrefs showed the keywords that slipped, PostHog confirmed the conversion impact on those pages. Three services, five minutes. The culprit was a competitor who published a nearly identical guide and outranked us on four key terms. We knew what to rewrite before the meeting started.

Quick reference​

The top picks​

These are the MCP servers with real, tested tools that a marketing team can put to work this week.

Google Tag Manager — 23 tools​

Google Tag Manager is one of those servers where the tool count doesn't sound impressive until you realize it covers the entire GTM workflow. Tags, triggers, variables, container versions, workspaces — your AI can manage the full lifecycle.

Why it matters for marketing: Every campaign launch involves tag changes. New conversion pixels, updated event parameters, UTM configurations. Instead of logging into GTM, navigating to the right container, creating a tag, setting up triggers, and publishing — you describe what you need. "Add a Meta Pixel PageView event to the checkout confirmation page" becomes a single prompt.

Real workflow: We use this to audit tag configurations before campaigns launch. "List all tags in the production container that fire on the checkout page" catches issues before they cost ad spend.

HubSpot — 136 tools​

HubSpot is the single largest MCP server we maintain, and for good reason. It covers contacts, companies, deals, engagement timelines, email tracking, forms, lists, workflows, and marketing events. If your marketing org runs on HubSpot, this is the first server you should connect.

Why it matters for marketing: HubSpot is where marketing and sales data lives. Lead scoring, email performance, deal attribution — it's all here. The AI can pull a contact's full engagement history, check which campaigns touched a deal before it closed, or segment a list based on behavior — tasks that normally involve building reports or exporting to a spreadsheet.

Real workflow: "Find all contacts who opened our product launch email last week but haven't been contacted by sales." That's a query that takes 5 minutes to build in HubSpot's list tool. The AI answers it in seconds.

HubSpot CRM — 60 tools​

HubSpot CRM is a focused subset — contacts, companies, deals, and pipeline management without the broader marketing platform tools. If you only need the CRM layer (or you're pairing it with other marketing tools), this is a lighter-weight option.

PostHog — 46 tools​

PostHog gives your AI access to product analytics, funnels, feature flags, and event data. For marketing teams that care about what happens after the click, this is indispensable.

Why it matters for marketing: Campaign performance doesn't end at the landing page. PostHog lets your AI trace the full journey — from ad click through signup to activation. "What's the signup-to-first-project conversion rate for users who came from the Google Ads campaign this month?" is answered from real event data, not approximations.

Real workflow: Before a board meeting, we ask the AI to pull activation metrics segmented by acquisition channel. What used to be a morning of dashboard building is now a conversation.

Ahrefs — SEO powerhouse​

Ahrefs is the deepest SEO toolset available via MCP. Keyword research, backlink analysis, site audits, rank tracking, content gap analysis, competitor research — it's all there. We use it daily alongside Google Search Console.

Why it matters for marketing: SEO is the highest-leverage channel for most B2B marketing teams, and it's also the most data-intensive. Ahrefs via MCP means your AI can research keywords, analyze competitor content strategies, and identify link-building opportunities without you ever opening the Ahrefs dashboard.

Real workflow: "Pull the top 10 ranking keywords for competitor.com that we don't rank for, filtered to keywords with 1,000+ monthly searches and KD under 30." That's a content gap analysis that normally takes 20 minutes of clicking through Ahrefs. The AI does it in one prompt.

Google Search Console — Rankings straight from Google​

Google Search Console is the source of truth for organic search performance. Clicks, impressions, CTR, average position — direct from Google's index. Plus URL inspection and indexing status.

Why it matters for marketing: Every SEO discussion should start with GSC data. It's the only tool that shows you exactly what Google sees. Pairing it with Ahrefs gives you the full picture — Google's actual click data plus Ahrefs' keyword intelligence.

Real workflow: "Which of our blog posts dropped more than 5 positions in the last 30 days?" Immediate triage instead of weekly manual reporting.

Attio — 60 tools​

Attio is a modern CRM with flexible custom objects and relationship intelligence. For marketing teams that outgrew spreadsheets but don't need Salesforce, Attio's dynamic schema means the MCP server adapts to however your workspace is configured.

Why it matters for marketing: Marketing attribution, campaign tracking, partner relationships — Attio handles all of it with custom objects that mirror your actual workflow. The AI can discover your schema and query it without you explaining your data model.

SendGrid — Email delivery at scale​

SendGrid handles transactional and marketing email. Send emails, manage contact lists, check delivery stats, review bounce and suppression lists.

Why it matters for marketing: Email deliverability is invisible until it breaks. With SendGrid via MCP, your AI can monitor bounce rates, check suppression lists before a campaign send, and troubleshoot delivery issues — "Is our domain still authenticated? What's our bounce rate this week?" — without digging through the SendGrid UI.

Resend — Modern transactional email​

Resend is a developer-focused email service that's become popular with modern marketing teams. Clean API, good deliverability, straightforward MCP integration.

Smartlead — Marketing automation​

Smartlead covers marketing automation and outreach. With 4 tools it's smaller than the others on this list, but it handles the core outreach workflow — managing campaigns, tracking engagement, and syncing with your CRM.

Honorable mentions​

These MCP servers are available on MCPBundles in the marketing category but are either newer, more niche, or still building out their tool coverage. Worth knowing about, especially if they match your stack.

• Serpstat — SEO platform with keyword research, site audit, and rank tracking. Available as an MCP server but currently in early-stage integration.
• Singular — Marketing analytics and attribution across paid channels. Useful for teams spending heavily on ads who need unified reporting.
• Lemonado — Conversion optimization tools. Newer entrant in the MCP ecosystem.
• Transform SEO — SEO transformation and optimization tools. Available for connection, still maturing.
• DiscoLike — Content discovery and recommendation. Niche but interesting for content marketing teams.
• WordLift — Structured data and SEO automation with a knowledge graph approach.
• Flywheel — Google and Meta Ads management. If you're running paid campaigns across both platforms, this consolidates the reporting.

A note on honesty: several of these are MCP-only servers with zero pre-built tools. That means the MCP server exists and your AI can connect to it, but the tool definitions are discovered dynamically from the remote server rather than curated and tested. They work — but the experience is less polished than the top picks above. We're actively improving coverage across all of them.

How these servers work together​

The real power isn't any single server. It's combining them in one conversation.

Here's a workflow we run monthly: content performance review. One prompt kicks off the whole thing:

"Pull our top 20 pages by organic clicks from Google Search Console. For each page, get the primary ranking keyword and its search volume from Ahrefs. Then check PostHog for the signup conversion rate from each page. Finally, pull the HubSpot contacts who converted from those pages in the last 30 days."

Four services, one conversation. The output is a content performance report that ties organic traffic to actual revenue — the kind of analysis that usually requires a marketing analyst and half a day.

Getting started​

Every server listed here is available on MCPBundles with one-click setup. Connect your credentials once — OAuth or API key — and every AI session gets access automatically. No JSON config files, no local server processes, no credential management headaches.

pip install mcpbundles
mcpbundles connect my_workspace
mcpbundles init

The CLI works with Claude Code, Cursor, Windsurf, ChatGPT, or any AI agent with terminal access.

Browse all 88 marketing MCP servers — or start with the ones your team already has credentials for. That's always the right first move.

More vertical guides​

• Best MCP Servers for Sales & CRM — if your marketing team works closely with sales, the CRM guide covers HubSpot, Attio, and 10 other CRM servers in depth.
• Best MCP Servers for Databases — for marketing analytics teams that query data warehouses directly.
• Best MCP Servers for DevOps — monitoring and infrastructure servers for teams that ship their own marketing tools.

For the full list across all categories, see our Best MCP Servers in 2026 guide.