Skip to content

docs: add Mailtrap MCP server guide - #371

Closed
dieudonneAwa wants to merge 1 commit into
warpdotdev:mainfrom
dieudonneAwa:add-mailtrap-mcp-guide
Closed

dieudonneAwa wants to merge 1 commit into
warpdotdev:mainfrom
dieudonneAwa:add-mailtrap-mcp-guide

Conversation

@dieudonneAwa

@dieudonneAwa dieudonneAwa commented Jul 24, 2026

Copy link
Copy Markdown

Adds a setup and usage guide for the official Mailtrap MCP server (github.com/mailtrap/mailtrap-mcp) under agent-platform/.

Covers:

  • Prerequisites and credentials setup
  • MCP server configuration for Warp
  • Usage examples for sending emails, sandbox testing, delivery logs, and template management

Mailtrap is a trusted email delivery platform used by 150,000+ developers. The MCP server installs via npx with no cloning required.
Closes #381

Adds a setup guide for the official Mailtrap MCP server under agent-platform/, covering configuration, credentials, and usage examples for sending emails, sandbox testing, and delivery management from within Warp.
@cla-bot

cla-bot Bot commented Jul 24, 2026

Copy link
Copy Markdown

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @dieudonneAwa on file. In order for us to review and merge your code, each contributor must visit https://cla.warp.dev to read and agree to our CLA. Once you have done so, please comment @cla-bot check to trigger another check.

@vercel

vercel Bot commented Jul 24, 2026

Copy link
Copy Markdown

@dieudonneAwa is attempting to deploy a commit to the warpdotdev Team on Vercel.

A member of the Team first needs to authorize it.

@warp-for-oss

warp-for-oss Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

@dieudonneAwa

Every PR must be linked to a same-repo issue before Oz can review it.

This PR is linked to #381, but no linked issue is marked ready-to-implement yet. Only repository maintainers apply that label, so please wait for a maintainer to mark the issue. Once it is marked, push a new commit or comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

@warp-for-oss warp-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dieudonneAwa

Every PR must be linked to a same-repo issue before Oz can review it.

Next step: open or find a same-repo issue describing this change, then link it to this PR by adding Closes #123 to the PR description (or using the "Development" sidebar on GitHub). A maintainer will mark the issue ready-to-implement when it is ready. Once it is marked, comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

@dieudonneAwa

Copy link
Copy Markdown
Author

@cla-bot check

@cla-bot cla-bot Bot added the cla-signed label Jul 26, 2026
@cla-bot

cla-bot Bot commented Jul 26, 2026

Copy link
Copy Markdown

The cla-bot has been summoned, and re-checked this pull request!

@dieudonneAwa

Copy link
Copy Markdown
Author

@cla-bot check

@cla-bot

cla-bot Bot commented Jul 26, 2026

Copy link
Copy Markdown

The cla-bot has been summoned, and re-checked this pull request!

@dieudonneAwa

Copy link
Copy Markdown
Author

/oz-review

@warp-for-oss warp-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dieudonneAwa

Every PR must be linked to a same-repo issue before Oz can review it.

This PR is linked to #381, but no linked issue is marked ready-to-implement yet. Only repository maintainers apply that label, so please wait for a maintainer to mark the issue. Once it is marked, push a new commit or comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

@hongyi-chen

Copy link
Copy Markdown
Collaborator

Thanks so much for taking the time to put this together and contribute to the Warp docs. At the moment, we don’t add setup guides for individual MCP servers to our docs. We reserve server-specific guides for official MCP partnerships, so we’re going to close this PR and the related issue.

We appreciate the contribution and hope you’ll consider contributing again in the future.

@hongyi-chen hongyi-chen closed this Aug 3, 2026
@darynaivanova-mt

Copy link
Copy Markdown

Hey @hongyi-chen , thank you for the feedback! We at Mailtrap would love to explore official MCP partnership with Warp. Would you be open to discussing it via email?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add Mailtrap MCP server guide to agent-platform docs

3 participants