Google Tasks MCP Server

Created By
ktmagea year ago
AI assistants and Google Tasks integration through Model Context Protocol.
Overview

What is Google Tasks MCP Server?

Google Tasks MCP Server is an implementation that allows AI assistants to interact with Google Tasks API through the Model Context Protocol (MCP). It enables task management features from MCP-compatible clients.

How to use Google Tasks MCP Server?

To use the server, clone the repository, install dependencies, configure Google Cloud Project, and run the server. You can then integrate it with MCP-compatible IDEs like Cursor.

Key features of Google Tasks MCP Server?

  • Fetch task list collections
  • Get tasks within a specific task list
  • Create new tasks
  • Mark tasks as completed
  • Delete tasks

Use cases of Google Tasks MCP Server?

  1. Integrating AI assistants with Google Tasks for task management.
  2. Automating task creation and management through MCP-compatible applications.
  3. Enhancing productivity tools with task management capabilities.

FAQ from Google Tasks MCP Server?

  • What is the purpose of this project?

This project is designed to practice implementing an MCP server for educational purposes.

  • Is there any support for issues?

Users are encouraged to report issues or suggest fixes via GitHub.

  • What are the prerequisites for running the server?

You need Node.js 16 or higher, npm, and a Google Cloud Project account.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ktmage
Star
0
Language
TypeScript
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