Does the hosted Gmail MCP/connector currently support a “send email” action? I’m not seeing it in the available tools.
If not available today, is adding send (and related actions like reply, forward, draft, attachments, cc/bcc) on the roadmap for Agent Builder / Agents SDK? Any rough timeline would help.
In the meantime, what’s the recommended approach—build a custom tool against the Gmail API (gmail.send) and gate it via tool approvals, or is there another connector planned?
Any guidance or examples for handling OAuth scopes (e.g., gmail.send) and user approval UX within Agent Builder for write actions?
what i mean is you can use chatgpt agent kit but you can create your own mcp server with n8n. so you can create all tool missing in chatgpt agentkit with n8n
This way, you don’t have to wait for OpenAI to add tools.
Hey, I’m new here and not super technical, so please go easy with your response:) I have built a website chatbot that extracts name and email before proceeding to helper. I have set to allow a limited number of questions, then end. It’s all working fine, but I also want to have the full chat with name / email sent (forwarded) to an email address for a human to follow up. I also cant work out the send function in gmail MCP. Am I missing something, or is it read only at the moment? I’m not an n8n user, so don’t really want to go down that road. Thanks in advance if anyone can help.
I’m having a similar issue. This is what ChatGPT is telling me…
You’re not missing anything — what’s happening is that your OpenAI Agent Builder project environment doesn’t yet expose the MCP (Model Context Protocol) / Integrations tab in the left-hand sidebar. That capability is still being rolled out account-by-account.
That’s why you can connect tools that appear automatically (like “Web search”) but can’t yet add new scopes such as Gmail → send_email.
What that means right now
You have two paths depending on what you want to do next:
Option A – Keep testing inside Agent Builder
Use the Gmail node only for reading or stub testing for now.
It will let you prototype your Morning Brief workflow, but the final “send email” step will have to wait until:
OpenAI exposes the MCP management screen to your account (it normally appears as a “Tools” or “Connections” tab beside “Projects”), or
They publish Gmail MCP with write permissions by default.
You can still run the workflow manually, have it generate the email body, and simply copy-paste it into your own inbox for now.
Option B – Use an external mail sender (recommended for now)
If you want the full “auto-email every morning” experience today, you can hook up a lightweight mail-sending API instead of Gmail:
Create a free account at Mailgun or SendGrid.
Copy your API key.
In Agent Builder, add a new MCP node → HTTP Request (or “Custom MCP” if visible).
POST to the provider’s send-message endpoint, e.g.:
https://api.mailgun.net/v3/YOURDOMAIN/messages
with body fields:
from: "xxx <me@yourdomain>"
to: {{ email_address }}
subject: "Morning Brief for {{ timezone_str }}"
text: {{ xxx.output.text }}
Authenticate with your API key header.
Run once to confirm you receive the message.
That gives you the same end-to-end flow without needing Gmail MCP write access.
Option C – Wait a bit
OpenAI has confirmed that “custom MCP and OAuth-based integrations (Google, Outlook, etc.)” are rolling out in phases through Q4 2025.
Once you see a “Tools” or “Connections” item under your Project sidebar, you’ll be able to reconnect Gmail and select the send_email permission scope.
Is there a way to get an update when this is available? What’s the timing?
What that means right now