# Integrations — Private Accounts, Exact Agent Permissions Source: https://mcpscraper.dev/integrations Connected work, without the tab shuffle # Put your AI to work in your email, calendar, analytics, meetings, and ads MCP Scraper connects your accounts to your AI, so drafting replies, prepping tomorrow's meetings, reading traffic, and tuning ad spend happen right where the work lives — remembered in Memory, repeated on the Scheduler. Connect your accounts See what your AI can do Private accounts Every connection belongs to the identity that added it. Writes require approval Connecting an account does not turn on actions. Remember the result Save approved evidence into searchable Memory. Repeat exact work Scheduler receives one account and minimum tool grants. Gmail + Memory ## Your Gmail, fully readable and safely workable Your AI can read complete messages, open the actual attachments, freeze an exact mailbox selection, and preserve the reviewed set in Memory — without treating inbox access as permission to change or delete anything. **Gmail** ****** MCP Scraper · connected work You asked Collect every invoice from last quarter, including attachments, and preserve the reviewed set in Memory. Gmail searched Complete messages inspected Selection frozen Exact set reviewed for 24 hours Memory plan Messages and files ready Result ### The source archive is ready for review Every selected message has a complete record, every attachment has a preservation state, and the import plan shows what will be stored before the first Memory write. Reviewed selection · no mailbox mutation Gmail search → immutable selection → reviewed Memory import Google Calendar + Zoom ## Your Calendar and Meetings, Prepped Before You Ask Google Calendar and Zoom in one view — your AI checks tomorrow's schedule, briefs you on who you're meeting, spins up the Zoom link, and books the follow-up, only when you confirm it. **Google Calendar** **Zoom** **Gmail** ****** MCP Scraper · connected work You asked Prepare tomorrow's meetings and tell me which one needs a follow-up booked. Schedule read 3 meetings tomorrow Context assembled Threads and attendees matched Follow-up proposed Awaiting confirmation Result ### Tomorrow is briefed The relevant history, open questions, and Zoom details sit beside each meeting instead of in three other tabs. 3 briefs · 1 proposed event · 0 events created Calendar + Gmail + Zoom → meeting brief → Memory receipt Google Analytics + Search Console ## Your Traffic, Read and Remembered Google Analytics and Search Console, answered in chat — your AI pulls this week's clicks, spots what dropped, finds the pages losing ground, and logs every check in Memory so trends surface themselves. **Google Analytics** **Google Search Console** ****** MCP Scraper · connected work You asked What changed in organic traffic this week, and is this a new problem? GA4 read Organic sessions compared Search Console Losing queries isolated Memory comparison Four prior checks recalled Result ### Three pages are losing ground The change is compared with prior checks, so the answer distinguishes a one-day wobble from a developing trend. Saved to Memory · Marketing / Weekly traffic GA4 + Search Console → prior Memory checks → trend report Meta Marketing + Ad Libraries ## Your Ad Spend and Their Ads, in One Conversation Meta Marketing connected, ad libraries watched — your AI reads your campaign performance, pulls the competitor creatives running right now, transcribes their videos, and tells you what's working on both sides of the auction. **Meta Marketing** **Facebook Ads** **Video transcription** ****** MCP Scraper · connected work You asked Compare our strongest campaign with the competitor creatives running now. Owned performance Campaign results inspected Live ad library Current creatives retrieved Video analysis Hooks and claims transcribed Result ### The gap is in the opening hook Your performance sits beside public creative evidence, with transcripts and sources attached to the recommendation. 5 creatives · 3 transcripts · sources retained Meta performance → live ad-library evidence → transcript comparison Connect once. Control every use. ## Useful access without silent authority OAuth is the handshake, not permission to do everything. Reads, live actions, scheduled work, and Memory imports each keep their own boundary. 1. Connect the account Approve the provider's OAuth screen. Credentials remain server-side and private to the identity that connected them. 2. Inspect exact capabilities See which reads exist and which actions can be separately enabled for that provider and account. 3. Ask now Use approved reads in the current conversation. Writes stay off unless you deliberately enable and grant them. 4. Remember or repeat Save an approved result into Memory or give Scheduler one exact account and the minimum tools for the recurring job. All integrations ## Every connected provider, with its real capability status OAuth-connected and action-ready are different states. All 15 rows show what can actually be granted today. ### Google Analytics Ready now Run GA4 reports and metadata reads. Optionally enable property, data-stream, and conversion-event administration. **5** reads **6** actions ### Google Search Console Ready now Read verified properties, Search Analytics performance, sitemaps, and URL inspection results, including quota-conscious API-only batches. Scheduled sync can maintain a typed tenant-owned performance table, but batches do not require a database. Property and sitemap changes remain separately gated and destructive batches default to dry-run. **8** reads **8** actions ### Google Drive Interactive ready Browse shared drives and bounded file pages; inspect metadata, changes, Docs, Sheets, and small documents. Folder creation and file copy are separately gated. Bulk corpus delivery is still in development. **10** reads **2** actions ### Gmail Ready now Read messages, threads, drafts, labels, and filters. Sending remains a separately enabled and explicitly granted action. **9** reads **1** actions ### Google Calendar Ready now Read calendars, events, availability, and upcoming schedules. Event creation remains separately gated. **9** reads **1** actions ### Facebook Pages Ready now Read Pages, posts, comments, scheduled posts, and videos. Optionally enable approved publishing and moderation actions. **10** reads **9** actions ### Meta Marketing Permission-aware ready Inspect and operate campaigns, ad sets, ads, creative media, insights, audiences, catalogs, rules, studies, leads, and brand-safety data. Every mutation is separately gated; effective tools depend on Meta-granted permissions and approved app features. **55** reads **60** actions ### Slack Ready now Read channels, messages, threads, reactions, files, and user context. Message sending remains separately gated. **15** reads **1** actions ### Zoom Ready now Read meetings, registrants, recordings, transcripts, and users. Meeting creation remains separately gated. **9** reads **1** actions ### LinkedIn Core ready Read the connected member profile today. Community Management workflows require a separate approved LinkedIn app. **1** reads **0** actions ### X Ready now Monitor posts, mentions, lists, likes, users, and Spaces. Optionally enable posting, follows, likes, bookmarks, and list actions. **12** reads **13** actions ### YouTube Ready now Read channels, videos, playlists, comments, and captions. Optionally enable playlist, comment, and video actions. **9** reads **12** actions ### GitHub Ready now Read and sync repositories, issues, pull requests, commits, releases, and workflows. Optionally enable exact create, update, merge, run, or delete actions. **27** reads **20** actions ### Resend OAuth MCP ready Read email, inbound mail, delivery logs, contacts, broadcasts, templates, and account configuration. Sending and every mutation remain gated; credential, OAuth, and raw editor-session access stay blocked. **33** reads **45** actions ### Xero OAuth connected The account connection is configured. Live scheduler tools remain unavailable until the deployed Xero function inventory is enabled. **0** reads **0** actions ## Built for work that lives in other tabs From client reporting and follow-up emails to ad audits and meeting prep, MCP Scraper puts your AI inside the accounts where that work already happens — yours and your clients'. ### Founders & Operators Traffic checked, invoices found, the week's meetings prepped, the follow-up drafted — one AI across GA, Gmail, Calendar, and Xero, so Monday morning runs itself before you've opened a tab. ### Agencies & Client Work Connect each client's Search Console, Analytics, and ad accounts — reporting pulled, anomalies flagged, drafts ready — so the monthly report takes one ask instead of one afternoon. ### Developers & Vibe Coders GitHub, Slack, and email in the loop — your AI reads the issue, checks the thread where it was decided, and drafts the reply — context assembled without you alt-tabbing to find it. ### Sales & Relationships Before the call: the last email thread, the LinkedIn page, the calendar history. After it: the follow-up drafted and the next meeting booked — nothing sent or scheduled until you say so. ### Content & Marketing Your own campaign numbers next to the competitor creatives running right now — performance read, videos transcribed, hooks logged — so every piece you ship is briefed by what's actually working. ### SaaS Support & Email Ops Inbound triaged, delivery investigated, broadcasts shipped through Resend — your AI works the support queue and the send calendar from chat, escalating only what needs a human. Pricing ## Connect what you need. Pay for the work it does. Connections are a small monthly add-on, billed in Credits from your balance. Reads, actions, and scheduled work use the same shared Credits as the rest of MCP Scraper. Connected account 15,000Credits/month each Each active Nango connection is a 15,000-credit/month add-on drawn from your balance; no plan includes a connection. - Same-integration replacements inherit the current paid period - Private to the identity that connected it - Actions remain separately gated Connect an account Connected usage 2 + 2Credits Measured provider work spends shared Credits instead of creating another balance. - 2 Credits per connected function run - 2 Credits per provider proxy request - 5 Credits per compute-second See the full rate card Scheduled work 75Credits / run Each started scheduled occurrence has one base charge and one billing identity. - Automatic retries are not charged twice - Agent mode adds 1.5× reported model cost - History records settled usage See the Scheduler Private connections · actions gated · Memory and Scheduler ready ## Put your AI inside the work you already do Start with one account and one job. Add another only when the workflow needs it. Open Integrations ## Frequently asked questions The practical details about connection pricing, permissions, Memory, provider limits, and scheduled work. Does connecting an account enable writes? No. Live actions remain off until deliberately enabled for that account. Scheduled work still needs an exact connection and exact per-tool grant, and destructive provider actions can require additional confirmation or dry-run behavior. How are connected accounts billed? Each active Nango connection is a 15,000-credit/month add-on drawn from your balance; no plan includes a connection. Disconnecting and replacing the same integration during that billing month transfers its paid period instead of charging another 15,000 Credits. One paid period still covers only one active connection. Work through it uses shared Credits: 2 Credits per connected function run, 2 Credits per provider proxy request, and 5 Credits per compute-second prorated from measured milliseconds. The dashboard Credits tab shows the rate card, and History records settled usage. How does connected evidence enter Memory? import_service_connection_to_memory runs exactly one current read tool, labels the provider result as untrusted evidence, writes it to a stable server-generated path, and returns a search_ready receipt. That snapshot path does not paginate. Gmail also has a selection-first bulk path: prepare the exact messages, review the filing and attachment plan, then start or resume the import. Source archives go to Library by default. Relationship filing uses only exact existing People or Organization matches and never infers tasks, deals, projects, or new contacts. What can Gmail and Resend actually do? Gmail has named tools for message search, complete message reads, actual attachment access, immutable selections, full export, reversible bulk changes, separately confirmed permanent deletion, and resumable Memory import. Sending remains a neighboring gated tool. Resend connects through `mcp.resend.com/mcp` and exposes 33 approved reads plus 45 gated actions. Bulk Resend history uses `resend_data`; credential administration remains blocked. What are the provider-specific limits? Gmail selections hold up to 5,000 messages and expire after 24 hours. A reviewed Memory plan can cover up to 10,000 attachments, 25 MiB per attachment, 250 MiB of selected attachment bytes, and 2,000 Memory source parts. Unsupported safe files can be preserved without being indexed; refused files and partial work are reported rather than hidden. Provider-specific bulk data for other supported datasets remains available through export_connected_service_data. Search Console uses search_console_performance and a typed gsc_performance_* table that agents can query without calling Google again. What can Search Console batch safely? API-only Search Console batches do not need that table. The connected account supports URL inspection and Search Analytics reads plus action-gated property and sitemap batches. Every item returns its own receipt, and destructive batches default to dry-run with explicit confirmation.