AI assistants and Google Tasks integration through Model Context Protocol.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"gtasks": {
"args": [
"/full/path/mcp-google-tasks/build/index.js"
],
"command": "node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
AI assistants and Google Tasks integration through Model Context Protocol.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
Local-first AI memory with knowledge graphs and hybrid search. 17+ AI tools via MCP. Free.
MCP server for monday.com integration.
MCP Security Weekly
Get CVE alerts and security updates for Mcp Google Tasks and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
AI assistants and Google Tasks integration through Model Context Protocol.
AIアシスタントとGoogle Tasksを連携させるModel Context Protocol実装。
An implementation for interacting with Google Tasks API through Model Context Protocol (MCP). This server allows you to use Google Tasks task management features from MCP-compatible clients such as Cursor.
This project was created to practice implementing an MCP server, with the goal of enabling AI assistants to interact with Google Tasks management features through the MCP protocol.
This project was created for learning purposes, and there may be issues that I'm not aware of due to my limited knowledge.
Please use at your own risk. The developer cannot take responsibility for any problems that may occur.
If you discover any issues, please create an Issue or suggest a fix via Pull Request. See the "Contributing" section below for details.
Contributions to this project are welcome. Bug reports, feature suggestions, pull requests, or any other form of participation are greatly appreciated.
For details, please refer to CONTRIBUTING.md.
This MCP server provides the following functions:
# Clone the repository (or obtain the project by any method)
git clone <repository URL>
cd mcp-google-tasks
# Install dependencies
npm install
credentials.jsonmcp-google-tasks/
├── src/
├── package.json
├── credentials.json <- place here
└── ...
# Build TypeScript
npm run build
# Run the server
node build/index.js
On first run, a browser window will open asking for Google account authentication. After authentication is complete, a token.json file will be generated, and this token will be used automatically for subsequent runs.
To use this server with MCP-compatible IDEs like Cursor, configure as follows:
~/.cursor)mcp.json file{
"mcpServers": {
"gtasks": {
"command": "node",
"args": [
"/full/path/mcp-google-tasks/build/index.js"
]
}
}
}
Replace /full/path/ with the actual full path to your project.
Example: /home/username/projects/mcp-google-tasks/build/index.js
Lists all task lists.
Parameters: none
Example:
list_tasklists()
=> Task list collection (JSON format)
Lists tasks within a specific task list.
Parameters:
taskListId: Task list ID (obtainable from list_tasklists)Example:
list_tasks(taskListId: "YOUR_TASK_LIST_ID")
=> Tasks in the specified task list (JSON format)
Cre