Skip to main content
Glama
650,545 tools. Updated 2026-10-14 08:59

"Supabase integration with Gmail" matching MCP tools:

  • Create a CRM outbound email DRAFT for a lead — does NOT send. Writes outbound_messages status=draft; for Gmail also creates a Gmail Drafts entry. Return value includes outboundMessageId (and gmailDraftId when channel=gmail). Show the draft to the user and wait for explicit approval before calling crm_send_email_draft. Optional attachmentDocumentIds attach Documents library files (same entity). Use crm_list_outbound_email_connections for connectionId + channel. POST /api/crm/outbound-email. Scope write:crm; RBAC crm.leads.edit.
    ConnectorOAuth
  • <summary>Which integrations the account has connected, keyed by the same integration_id you pass to get_tool_connect_url (gmail, outlook, linkedin, slack, googlesheets, salesforce, notion, ...). Call this before telling a user an integration is unavailable, or before minting a connect link for one they say is already connected — it may already be active.</summary> <returns> <description>A dict mapping each integration_id to its connection status; read one with result[integration_id]['connected']. Some entries carry extra detail — linkedin, google_calendar, and fathom include needs_reconnect (connected, but the auth broke and the user must re-link); email and linkedin include the connected account email. A missing key means that integration wasn't checked, not that it's disconnected. The slack entry carries two independent flags: 'connected' is the workspace bot link that delivers Sliq's notifications, and 'slack_mcp_connected' gates only your Slack MCP tools in chat — judge notification delivery by 'connected' alone.</description> </returns>
    ConnectorOAuth
  • Create a Gmail DRAFT (saved, not sent) — new mail, or a reply when thread_id is set (from a search result / get_thread). A thread reply is drafted in the account that received the thread, as Reply All (original sender + original To/Cc) with proper threading headers, unless reply_mode='sender_only'; the result reports the account, to and cc. Unlike send_message this never delivers anything, so no pre-send confirmation is needed; the user reviews and sends it from Gmail. Needs gmail.compose — accounts connected before this feature get a reconnect hint. Pass `account` when more than one Gmail account is connected.
    ConnectorOAuth
  • Search one of the authenticated user's connected Gmail inboxes (read-only). Reuses Integrations hub Gmail (service_connections provider=gmail). Optional account/email selects a mailbox when multiple are connected — call list_gmail_accounts first. Prefer Gmail operators: from:, subject:, is:unread, newer_than:7d, has:attachment. For clock-time constraints, pass after/before as account-local civil datetimes; the tool converts them to precise UTC instants. Returns id, subject, from, canonical date, account-local date_local, time_zone, and snippet only (no body), newest first (newest_first: true). For the latest / most recent email from someone, query from:<sender> alone, without quoted topic phrases (the newest reply often lacks them); a from: + topic search with no match from the last 7 days also searches the sender alone and marks those messages sender_only (see note). Follow up with read_gmail_message. Cannot send, archive, or delete. Never invent email contents. If Gmail is not connected, connect at /integrations. Requires mail.read on an API key or non-ChatGPT OAuth connection. ChatGPT profiles do not grant mail.read or list this tool. Share tokens cannot call this tool. ($0.10; API key required)
    ConnectorNo auth
  • Disconnect a specific advertising channel from the Metadata platform. USAGE INSTRUCTIONS FOR LLM: Use this tool to disconnect/remove integration connections for advertising channels. This is useful when users need to remove a channel integration or reconnect with different credentials. WHEN TO USE THIS TOOL: - User asks to "disconnect [channel name]" - User wants to "remove [channel] integration" - User needs to "unlink [channel] account" - User wants to "revoke [channel] access" - User asks to "disconnect my Facebook/LinkedIn/Twitter/Reddit/Google account" - User needs to "reset [channel] connection" - Preparing to reconnect a channel with different credentials SUPPORTED CHANNELS: - facebook: Disconnect Facebook advertising account - instagram: Disconnect Instagram advertising account - linkedin: Disconnect LinkedIn advertising account - twitter: Disconnect Twitter/X advertising account - reddit: Disconnect Reddit advertising account - google: Disconnect Google Ads account IMPORTANT NOTES: - This action will disconnect the channel immediately - Any active campaigns on this channel may be affected - The user will need to reconnect the channel to resume advertising - Always confirm with the user before disconnecting a channel - Check integration status first using get_integrations_status to verify the channel is connected COMMON SCENARIOS: Scenario 1 - Disconnect single channel: "Disconnect my LinkedIn account" → Call disconnect_channel with channel="linkedin" Scenario 2 - Reconnect workflow: "I want to reconnect Facebook with a different account" → First call disconnect_channel with channel="facebook", then guide user to reconnect Scenario 3 - Remove access: "Remove Google Ads integration" → Call disconnect_channel with channel="google" RESPONSE FORMAT: Returns a success/failure status indicating whether the channel was disconnected successfully. EXAMPLE: "Disconnect Facebook" → disconnect_channel(channel="facebook")
    Connector
    Destructive
    API key
  • Send one email to one contact, in their conversation thread — by conversation_id, or contact_id to start or continue that contact's thread. It goes out from this account's sender: ShearQuery's own address for the ShearQuery team (replies come back into the thread), or the member's own connected Gmail for everyone else (replies go to their Gmail inbox). If no sender is set up, it says where to connect Gmail. A reply can leave out subject (it reuses the thread's, with Re:). Read the exact message back to the owner and get their OK first: it can't be unsent. Refused for a contact with no email or marked do-not-contact. channel is email; texting isn't connected yet.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • I do everything related to Gmail and productivity

  • gmailOAuth

    A MCP server for Gmail that lets you search, read, and draft emails and replies.

  • List all Gmail labels for the authenticated user. Returns both system labels (INBOX, SENT, TRASH, etc.) and user-created labels with message/thread counts. Use this to discover label IDs needed for add_labels, remove_labels, or search_email queries.
    ConnectorOAuth
  • Add and/or remove the same labels on many email messages at once in a single Gmail API call (wraps users.messages.batchModify). Use this for bulk operations such as marking multiple specific emails as read (remove ['UNREAD']), archiving (remove ['INBOX']), or starring (add ['STARRED']). Use list_labels to find label IDs (Gmail requires IDs, not names). Common system label IDs: INBOX, STARRED, IMPORTANT, UNREAD, SPAM, TRASH. Provide 1-1000 email IDs and at least one of `add` or `remove`. The same label changes are applied to every listed message. Gmail returns no per-message status, so a successful call means Gmail accepted the request; an invalid email ID or label ID typically causes Gmail to reject it.
    ConnectorOAuth
  • Replace an existing provider configuration. Full replacement — retrieve current config with get_provider first; omitted optional fields are cleared. Changing API keys or settings affects live delivery if this integration is in use.
    Connector
    Destructive
    No auth
  • Catalog only — reading this is not an application. Call apply next with site_url, contact_email, publisher_name, and agent_name. Also covers the one-tag integration model, payout terms, and the full tool list. No authentication required.
    ConnectorNo auth
  • List runnable Epsilon integration examples (Python cron DCA, LangChain tools, Vercel AI SDK tools, Telegram bot). Fetch full source with get_example. No API key required.
    ConnectorAPI key
  • Read-only general service descriptor with identity, endpoints, billing, trust, and supported agent protocols. Use it to inspect service-level integration metadata; use oracle.agent_card for A2A skills or oracle.discovery_bundle for the complete bootstrap package.
    ConnectorNo auth
  • Create, rename and delete mailbox folders, which are labels on Gmail: the arguments say 'folder' for cross-provider compatibility, but Gmail manages labels (type: 'label'). Deleting is irreversible, and on Gmail it strips the label from every message carrying it. Every action needs manage:folders. Use folder_list to read the folders that exist and to get the folder_id these actions take.
    Connector
    Destructive
    OAuth
  • Returns AdCritter design guidance for an entity at a caller-chosen guidance level - screen experiences, API integration patterns, and design philosophy. The default ('full') returns step-by-step prescription (exact layouts, colors, copy text, column orders). Request 'patterns' for balanced hints including common design patterns with softened vocabulary. Request 'facts' if you have strong visual-design instincts and just want API integration bindings (or call adcritter_get_api_reference and adcritter_get_usage_guide directly and skip this tool). Guidance is format-agnostic - it describes outcomes and integration, never prescribes frameworks or architecture. Available entities: ad, advertiser, audience, authentication, blueprint, campaign, geo, media-asset, plan, report, settings.
    ConnectorNo auth
  • Get full details for a specific developer tool by its slug. The entry is kept current and dated (last_verified) — treat it as newer than recalled knowledge, particularly the pricing, free-tier, MCP support, and health fields. Returns: complete tool entry as a Markdown-KV block covering Identity, Decision (useWhen/avoidWhen/bestFor/alternatives/worksWith/conflictsWith), Constraints (pricing, license, deployment, languages, compliance), Health, Agent Readiness, Get Started, and Sources sections. Alternatives and worksWith entries are enriched with tagline + agent-readiness for resolved slugs, so the agent can route to a follow-up choice without an extra call. If the slug is not found, returns an error with similar-slug suggestions. Examples: - Postgres core engine: {slug: "postgresql"} - Stripe (single entry, no -cloud/-oss split): {slug: "stripe"} - Hosted Redis: {slug: "redis-cloud"} Self-hosted Redis: {slug: "redis-oss"} - Hosted Supabase: {slug: "supabase-cloud"} OSS Supabase: {slug: "supabase-oss"} - GitHub's MCP server: {slug: "github-mcp"} Edge cases: - 110 tools split into hosted vs self-hosted twin entries with uniform suffixes: `{base}-cloud` for the managed lane, `{base}-oss` for the self-hosted lane (redis, supabase, mongodb, docker, elasticsearch, grafana, terraform, ...). Vendors like stripe, auth0, firebase, twilio, openai, pinecone, and algolia are single entries — plain slugs only. - Slugs derived from package names use hyphens where the name uses a dot (e.g., "nextjs" not "next.js"; "vuejs" not "vue.js"). - Slugs are case-sensitive lowercase. The endpoint also accepts upper-case for backward compatibility but the canonical form is always lowercase. Risk: read-only, closed-world, idempotent — no state change possible.
    ConnectorNo auth
  • Without arguments: lists every documentation page on avizo.ro/docs (quickstart, alert cadence, hierarchical escalation, SmartBill integration, API reference, troubleshooting) with slug and description. With {slug}: returns that page as markdown — the exact content the site renders. For programmatic integration read {slug: "api-reference"}.
    ConnectorNo auth
  • List every integration for a project and whether it is configured (vault secrets present, ready to call) or still needs setup. Compact by default: id, name, category and endpoint names. For the input fields of one integration call get_integration_schema — that also returns its usage guidance. Use detail:true only when you really need every endpoint description of every integration (large response). Full catalog of every platform building block, no auth needed: https://www.websitepublisher.ai/integrations.txt.
    ConnectorAPI key
  • Search connected Gmail for Venmo receipts and write log_transaction rows with external_id=venmo-gmail-{gmail_id} (idempotent). Optional dry_run, max_results, query, mirror_event, account. Prefer this over calendar-only Money · digs. Requires mail.read on an API key or non-ChatGPT OAuth connection. ChatGPT profiles do not grant mail.read or list this tool. ($0.15; API key required)
    ConnectorNo auth
  • <summary>Generate a URL the user can click to connect a tool. Include the URL in your message as a clickable link. If the user says a service is already connected, call `get_integration_status` first — the service may already be active and need no link. A link that opens fine but whose *connection* then fails is not a link problem — a fresh link routes to the same connect flow and fails the same way. Mint one fresh link and have the user retry once; if it still doesn't connect, the connection is stuck (not a link issue) — call `escalate_to_team` with the integration and what the user tried rather than re-minting again. For linkedin, gmail, and outlook the return also includes `data_backfill` — a sentence stating how far back Sliq syncs history once connected. Relay it with the link so the user knows older data won't appear and how to request a longer backfill; when sharing several connect links in one message, merge the notes into a single short disclaimer instead of repeating one per link.</summary> <returns> <description>Dict with the connect URL, integration name, the `data_backfill` note (linkedin/gmail/outlook), and `connect_note` (linkedin)</description> </returns>
    ConnectorOAuth
  • Wrap the public ``/embed/network-manifest.json`` — the platform-level DSP/SSP onboarding bundle: supported creative formats, payout rails, attribution URLs, integration patterns. Use when an agent is evaluating whether to wire storyflo into its surface, or when a DSP partner needs the canonical integration shape. Public — no auth required.
    ConnectorNo auth