Productivity · Local MCP server
Pylos MCP
Read-focused, prompt-injection-hardened email MCP server for any IMAP provider.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.adamVass/pylos-mcp- Version
- 0.2.0
- Status
- Active
- Category
- productivity
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-01
- Updated
- 2026-09-01
- Publisher
- adamVass (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/adamVass) · how
- Listed under
- Email MCP servers
- Repository
- github.com/adamVass/pylos-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | pylos-mcp | 0.2.0 | stdio |
How to connect Pylos MCP
Pylos MCP runs locally from a Node.js package published to the npm registry: pylos-mcp version 0.2.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y pylos-mcp@0.2.0. It reads these environment variables: EMAIL_USER (required), EMAIL_PASSWORD (secret), PROVIDER, IMAP_HOST and CAPABILITIES; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"pylos-mcp": {
"command": "npx",
"args": [
"-y",
"pylos-mcp@0.2.0"
],
"env": {
"EMAIL_USER": "<value>",
"EMAIL_PASSWORD": "<secret>",
"PROVIDER": "<value>",
"IMAP_HOST": "<value>",
"CAPABILITIES": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| PubSec RadarFederal sales intelligence: expiring-contract triggers, agency spend intel, deal qualification. | Remote · HTTPLive check: ✓ handshake |
| PumpGTM MCP serverFind buyers, run LinkedIn, email and X outreach, and answer replies from your AI. | Remote · HTTPLive check: sign-in required |
| Puptra PDF SnapshotOne-call URL-to-PDF and full-page screenshot API with Puppeteer's page.pdf()/page.screenshot()... | Remote · HTTPLive check: ✓ handshake |
| PuzzleTideWord search, crossword, and sudoku generators, printable PDF worksheets, and verifiable LLM evals. | Local · stdio |
| qarera.comSearch jobs, manage resumes, and track applications on Qarera from your AI chat client. | Remote · HTTPLive check: sign-in required |
| QoramiCheck an email before an AI agent sends it: send / ask a human / block. Detects prompt injection. | Local · stdio |
| QualeQuest - AI Agent Governance PlatformMulti-agent governance: task orchestration, compliance, decision validation, and ML predictions. | Remote · HTTPLive check: sign-in required |
| Qualisend Email VerificationVerify email addresses and clean lists to improve deliverability and sender reputation. | Remote · HTTPLive check: ✓ handshake |