Todo Assistant with AI and Google Calendar Integration

Created By
mertadalia year ago
AI-powered todo assistant with Google Calendar integration using OpenAI's API and Model Context Protocol (MCP) support for natural language task management.
Overview

What is OpenAI Todo Assistant Server?

OpenAI Todo Assistant Server is a simple Express server that utilizes OpenAI's Assistant API to manage a todo list effectively.

How to use OpenAI Todo Assistant Server?

To use the server, clone the repository, install the dependencies, set up your OpenAI API key in a .env file, build the TypeScript code, and start the server. The server will be accessible at http://localhost:3000.

Key features of OpenAI Todo Assistant Server?

  • Integration with OpenAI's Assistant API for intelligent task management.
  • API endpoints for creating threads, sending messages, and retrieving chat history.
  • Easy setup and deployment using TypeScript and Express.

Use cases of OpenAI Todo Assistant Server?

  1. Managing personal todo lists with AI assistance.
  2. Creating collaborative task management systems.
  3. Integrating with other applications for enhanced productivity.

FAQ from OpenAI Todo Assistant Server?

  • How do I set up the server?

Clone the repository, install dependencies, set up your OpenAI API key, build the code, and start the server.

  • What API endpoints are available?

The server provides endpoints for creating threads, sending messages, and retrieving chat history.

  • Is there any cost associated with using the OpenAI API?

Yes, usage of the OpenAI API may incur costs based on the API's pricing model.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mertadali
Star
0
Language
TypeScript
License
MIT license
Tags

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