AGENT SKILL

cooper-mcp

Connect or troubleshoot the hosted Cooper Email MCP server (https://cooperemail.com/mcp) in Cursor, Claude Code, Claude.ai, ChatGPT, VS Code, Windsurf, Codex, or any Streamable HTTP MCP client. Use for installation, OAuth sign-in, Bearer API-key headers, 401 errors, or missing tools. Do not use when the connection already works and the user just wants to send, read, or manage mail; use the sibling Cooper skills for that.

License 许可
MIT
所属仓库
bg-szy/TOP-SKILLS
最近更新
2026-11-15
Stars
★ 6
Forks
0

01 前言 Front Matter

name
cooper-mcp
license
MIT
metadata
{ "version": "1", "homepage": "https://cooperemail.com/docs/mcp" }
description
Connect or troubleshoot the hosted Cooper Email MCP server (https://cooperemail.com/mcp) in Cursor, Claude Code, Claude.ai, ChatGPT, VS Code, Windsurf, Codex, or any Streamable HTTP MCP client. Use for installation, OAuth sign-in, Bearer API-key headers, 401 errors, or missing tools. Do not use when the connection already works and the user just wants to send, read, or manage mail; use the sibling Cooper skills for that.

02 资源文件 1

03 SKILL.md 正文

Cooper Email MCP

Hosted Streamable HTTP server (no local process):

https://cooperemail.com/mcp

/api/mcp is an alias. The server publishes 61 tools today; clients read the live catalog, so do not depend on a copied count.

Cursor (this plugin)

The plugin registers the server with the bare URL. Cursor signs in with OAuth 2.1 + PKCE the first time a tool needs auth: on Cooper's consent screen you can create a new inbox or paste an existing key. No key goes in the config.

To use an API key instead (scripts, or a client without OAuth), add the server to .cursor/mcp.json or ~/.cursor/mcp.json with a header:

{
  "mcpServers": {
    "cooper-email": {
      "url": "https://cooperemail.com/mcp",
      "headers": { "Authorization": "Bearer ${env:COOPER_API_KEY}" }
    }
  }
}

Keys start with coop_live_. Keep them in an environment variable or secret store, never in a committed file or in chat.

Other clients

  • Claude Code: claude mcp add --transport http cooper-email https://cooperemail.com/mcp (add --header "Authorization: Bearer $COOPER_API_KEY" to use a key), or the plugin: /plugin marketplace add cooper-email/cooper-email, then /plugin install cooper-email@cooper-email.
  • Claude.ai and Claude Desktop: Settings, Connectors, Add custom connector. Name Cooper Email, URL https://cooperemail.com/mcp, then connect (OAuth).
  • ChatGPT: connect through the public Cooper Email listing, or add the MCP URL with OAuth.
  • VS Code, Windsurf, Codex, Goose: copy-paste configs at https://cooperemail.com/integrations

No account yet

cooper_onboard needs no auth. It creates an account, one username@cooperemail.com inbox, and an API key shown once. With OAuth, the consent screen does the same thing.

Verify

  1. Reload Cursor (Developer: Reload Window) or start a new session.
  2. Check the MCP status in Cursor settings and finish sign-in.
  3. Call cooper_whoami (shows auth_type oauth or api_key) and cooper_list_inboxes as read-only smoke tests.

Troubleshoot

  • 404: the URL is missing /mcp.
  • 401 with "needs an OAuth access token or Authorization: Bearer": the connection is not signed in. Finish OAuth, set the header, or call cooper_onboard.
  • "API key or OAuth access token is not recognized": the key is wrong, revoked, or expired, or COOPER_API_KEY was not visible to the client process. Reconnect with OAuth, or mint a new key from a working session over HTTP (POST /api/v1/keys) so the secret stays out of the chat.
  • 403 permission_denied: the key is limited to one inbox or a permission list; cooper_whoami shows the scope.
  • Discovery: /.well-known/oauth-protected-resource, /.well-known/oauth-authorization-server, /.well-known/mcp.json, and the catalog at /api/v1/mcp/tools.

Docs: https://cooperemail.com/docs/mcp · https://cooperemail.com/llms.txt

04 同仓库更多 Skills

bg-szy
bg-szy/TOP-SKILLS

serpmaven

Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-landing-page-audit

Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-growth-context

Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-get-listed

Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-ai-readiness-audit

Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

proxy-troubleshooting

Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.

★ 6