yagms

Created By
acro5pianoa year ago
Yet Another Gmail MCP Server
Overview

what is yagms?

Yagms is a Gmail Model Context Protocol (MCP) server that allows users to interact with their Gmail accounts programmatically.

how to use yagms?

To use yagms, set up OAuth credentials for the Gmail API, build the project using Bun, authenticate your Google account, and then run the server to access various email functionalities.

key features of yagms?

  • List emails from your inbox with filtering options.
  • Retrieve specific emails by ID.
  • Search for emails using Gmail's search syntax.
  • Get all Gmail labels.

use cases of yagms?

  1. Automating email retrieval for data analysis.
  2. Integrating Gmail functionalities into other applications.
  3. Customizing email management workflows.

FAQ from yagms?

  • What is the purpose of yagms?

Yagms serves as a server to interact with Gmail using the Model Context Protocol, enabling programmatic access to email functionalities.

  • Is yagms free to use?

Yes! Yagms is open-source and free to use under the MIT license.

  • What are the prerequisites for using yagms?

You need to create OAuth credentials for the Gmail API and have Bun installed to build and run the project.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
acro5piano
Star
0
Language
JavaScript
License
MIT 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