Repository navigation
Add Cooper Email to MCP Servers - #262
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What are you adding?
How is it related to Gemini CLI?
Cooper Email is a hosted Streamable HTTP MCP server at
https://cooperemail.com/mcp(OAuth orAuthorization: Bearer $COOPER_API_KEY). Gemini CLI adds it as a remote server insettings.json("cooper-email": {"httpUrl": "https://cooperemail.com/mcp", "headers": {"Authorization": "Bearer $COOPER_API_KEY"}}) and then has its ownusername@cooperemail.cominbox: send, read, and reply to mail, and wait for replies or sign-up codes (cooper_wait_for_code). One unauthenticated request creates the account, inbox, and key, so the agent can set itself up. Agent docs: https://cooperemail.com/llms.txtChecklist