Inbox MCP

Created By
darinkishorea year ago
A Model Context Protocol (MCP) server for email integration via Nylas. Enables AI assistants to effortlessly batch-triage, organize, and automate email through natural language interactions.
Overview

What is Inbox MCP?

Inbox MCP is a Model Context Protocol (MCP) server designed for email integration via Nylas, enabling AI assistants to efficiently manage, triage, and automate email tasks through natural language interactions.

How to use Inbox MCP?

To use Inbox MCP, set up a Nylas account, connect your email, and install the Inbox MCP package using a simple command. You can then interact with your inbox using conversational commands.

Key features of Inbox MCP?

  • Automates email management using natural language.
  • Supports batch processing and triaging of emails.
  • Compatible with multiple email services including Gmail and Outlook.
  • Provides tools for filtering, archiving, and summarizing emails.

Use cases of Inbox MCP?

  1. Automating the organization of emails based on priority.
  2. Summarizing important emails for quick review.
  3. Archiving old emails while preserving important ones.

FAQ from Inbox MCP?

  • Can Inbox MCP integrate with any email service?

Yes! It works with Gmail, Outlook, iCloud, Yahoo, and any IMAP service.

  • Is there a cost to use Inbox MCP?

Inbox MCP offers 5 free connected accounts for users to get started.

  • How does Inbox MCP handle email requests?

It processes requests using conversational language, making it user-friendly and efficient.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
darinkishore
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago