MCP Enabled Email Reader

Created By
Safe-Swiss-Cloud-AGa year ago
MCP server to connect to an email server and search emails
Overview

What is MCP Enabled Email Reader?

MCP Enabled Email Reader is a tool that connects to an email server and allows users to search emails, download attachments, and list folders using the Model Context Protocol (MCP).

How to use MCP Enabled Email Reader?

To use the MCP Enabled Email Reader, install Claude Desktop or another MCP-enabled AI tool, set up Python, and configure the necessary settings in the claude_desktop_config.json file with your email server details.

Key features of MCP Enabled Email Reader?

  • Connects to email servers using MCP.
  • Allows searching of emails, downloading attachments, and listing folders.
  • Compatible with Claude Desktop and other MCP-enabled tools.

Use cases of MCP Enabled Email Reader?

  1. Automating email retrieval and processing for applications.
  2. Integrating email functionalities into AI-driven tools.
  3. Enhancing productivity by managing emails through MCP.

FAQ from MCP Enabled Email Reader?

  • What is required to run MCP Enabled Email Reader?

You need Claude Desktop, Python 3.10 or higher, and the uv package installed.

  • Is there a risk with storing sensitive information in the configuration file?

Yes, the configuration file contains sensitive information like email passwords, so ensure it is stored securely.

  • Can I contribute to the MCP Enabled Email Reader project?

Yes, contributions are welcome through issues and pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Safe-Swiss-Cloud-AG
Star
0
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago