MCP Server Setup Instructions

Name: MCP Server Setup Instructions
Author: amirdhs

@amirdhs

Repository

About MCP Server Setup Instructions

No overview available yet

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-server-amirdhs": {
      "command": "python",
      "args": [
        "mcp_server.py"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Server Setup Instructions?

MCP Server Setup Instructions is a Telegram AI agent server that integrates Gmail, Google Calendar, and Google Tasks using the Ionos AI model. It allows users to manage Google services through natural language commands sent via Telegram.

How to use MCP Server Setup Instructions?

Install dependencies with pip install -r requirements.txt, then set up Google Cloud OAuth2 credentials, a Telegram bot token, and an Ionos AI API key. Copy .env.example to .env, fill in the values, and run python mcp_server.py to authenticate with Google. Use Telegram to send messages or commands to the bot, which triggers the available tools.

Key features of MCP Server Setup Instructions

Send messages via Telegram
Search Gmail messages
Create Google Calendar events
Create Google Tasks
Chat with Ionos AI model

Use cases of MCP Server Setup Instructions

Search Gmail for emails from a specific sender
Create a calendar meeting with custom details
Add a task with a due date
Ask the AI assistant conversational questions
Manage Google services hands‑free via Telegram

FAQ from MCP Server Setup Instructions

What dependencies are required?

Python 3.8+, a Google Cloud project with Gmail, Calendar, and Tasks APIs enabled, a Telegram bot token from BotFather, and an Ionos AI API key.

How are credentials stored and secured?

Google OAuth2 credentials are stored in credentials.json and the authentication token in token.pickle. Both files are sensitive and should not be committed to version control. The .env file holding keys must also be kept secure.