MCP Greeting Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Greeting ServerGreet me in Portuguese"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
🌍 MCP Greeting Server
A Model Context Protocol (MCP) server that provides intelligent, time-aware greetings in multiple languages and timezones.
✨ Features
🕐 Time-aware greetings - Automatically says good morning, afternoon, or evening based on current time
🌍 Multi-language support - English, Portuguese, Spanish, and French
🌎 Timezone flexibility - Works with any timezone (defaults to Brazil/São Paulo)
👤 Personalization - Optional name parameter for personalized greetings
🎯 MCP Compatible - Ready to use with Claude and other MCP clients
Related MCP server: Time MCP Server
🚀 Quick Start
Prerequisites
Node.js 18+
npm or yarn
Installation
# Clone the repository
git clone https://github.com/gustavorobertux/mcp-greeting-server.git
cd mcp-greeting-server
# Install dependencies
npm install
# Start the server
npm start🔧 Claude Configuration
Method 1: Claude Desktop App
Install Claude Desktop from Claude.ai
Locate the configuration file:
# Windows %APPDATA%\Claude\claude_desktop_config.json # macOS ~/Library/Application Support/Claude/claude_desktop_config.json # Linux ~/.config/Claude/claude_desktop_config.jsonAdd the MCP server configuration:
{ "mcpServers": { "greeting": { "command": "node", "args": ["/full/path/to/mcp-greeting-server/index.js"] } } }Restart Claude Desktop and you'll see the greeting tool available!
Method 2: Claude Web/API with MCP Client
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";
// Connect to the greeting server
const transport = new StdioClientTransport({
command: "node",
args: ["/path/to/mcp-greeting-server/index.js"]
});
const client = new Client({
name: "greeting-client",
version: "1.0.0"
}, {
capabilities: {}
});
await client.connect(transport);
// Use the greeting tool
const result = await client.request({
method: "tools/call",
params: {
name: "greet",
arguments: {
name: "Alice",
language: "en"
}
}
});
console.log(result.content[0].text);Method 3: NPX (Quick Test)
# Run directly with npx (after publishing to npm)
npx mcp-greeting-server
# Or clone and run locally
git clone https://github.com/gustavorobertux/mcp-greeting-server.git
cd mcp-greeting-server
npm install
npm startTroubleshooting
Issue: Claude Desktop doesn't show the greeting tool
✅ Check file path is absolute
✅ Verify Node.js is in PATH
✅ Restart Claude Desktop completely
✅ Check Claude Desktop logs for errors
Issue: Permission denied
# Make the script executable (Linux/macOS)
chmod +x index.js
# Or run with node explicitly
"command": "node"Issue: Module not found
# Install dependencies in the project folder
cd /path/to/mcp-greeting-server
npm installMCP Configuration
Add to your MCP client configuration:
{
"mcpServers": {
"greeting": {
"command": "node",
"args": ["/absolute/path/to/mcp-greeting-server/index.js"]
}
}
}🧪 Testing with Claude
Once configured, you can test in Claude:
Hey Claude, can you greet me?Claude will use the greet tool and respond with a time-appropriate greeting!
Hey Claude, greet me in Portuguese with my name "João"Claude will call: greet({ name: "João", language: "pt" })
📖 Usage
With Claude
Once configured with Claude, simply ask for greetings naturally:
User: "Hey Claude, can you greet me?"
Claude: Uses greet() → "🌅 Good morning! friend! 🤝 It's 09:30 now. Hope you're having a great time!"
User: "Greet me in Portuguese as João"
Claude: Uses greet({name: "João", language: "pt"}) → "☀️ Boa tarde! João! 🤝 São 14:30 agora. Espero que esteja tendo um ótimo momento!"Direct API Usage
Basic Greeting
// Simple greeting (uses defaults: English, current timezone)
greet()
// Output: "🌅 Good morning! friend! 🤝\n\nIt's 09:30 now. Hope you're having a great time!"Personalized Greeting
// With name
greet({ name: "Alice" })
// Output: "☀️ Good afternoon! Alice! 🤝\n\nIt's 14:30 now. Hope you're having a great time!"Multi-language Support
// Portuguese
greet({ name: "João", language: "pt" })
// Output: "🌅 Bom dia! João! 🤝\n\nSão 09:30 agora. Espero que esteja tendo um ótimo momento!"
// Spanish
greet({ name: "María", language: "es" })
// Output: "🌙 ¡Buenas noches! María! 🤝\n\nSon las 21:30 ahora. ¡Espero que estés teniendo un gran momento!"
// French
greet({ name: "Pierre", language: "fr" })
// Output: "☀️ Bon après-midi! Pierre! 🤝\n\nIl est 15:30 maintenant. J'espère que vous passez un bon moment!"Different Timezones
// New York time
greet({ timezone: "America/New_York" })
// London time
greet({ timezone: "Europe/London" })
// Tokyo time
greet({ timezone: "Asia/Tokyo" })⚙️ API Reference
Tool: greet
Description: Returns an appropriate greeting based on the current time
Parameters:
Parameter | Type | Required | Default | Description |
| string | No | - | Person's name for personalization |
| string | No |
| Timezone for the greeting |
| string | No |
| Language code ( |
Example Response:
{
"content": [
{
"type": "text",
"text": "🌅 Good morning! Alice! 🤝\n\nIt's 09:30 now. Hope you're having a great time!"
}
]
}🌐 Supported Languages
Language | Code | Example |
English |
| "Good morning! friend!" |
Portuguese |
| "Bom dia! amigo!" |
Spanish |
| "¡Buenos días! amigo!" |
French |
| "Bonjour! ami!" |
🕐 Time Periods
Time Range | Greeting Type | Emoji |
05:00 - 11:59 | Morning | 🌅 |
12:00 - 17:59 | Afternoon | ☀️ |
18:00 - 04:59 | Evening/Night | 🌙 |
🛠️ Development
Project Structure
mcp-greeting-server/
├── index.js # Main server file
├── package.json # Dependencies and scripts
├── README.md # This file
└── .gitignore # Git ignore rulesRunning in Development
# Install dependencies
npm install
# Start the server
node index.js
# Or with npm script
npm startTesting
# Test the greeting function
npm test🤝 Contributing
Fork the repository
Create a feature branch (
git checkout -b feature/amazing-feature)Commit your changes (
git commit -m 'Add amazing feature')Push to the branch (
git push origin feature/amazing-feature)Open a Pull Request
Adding New Languages
To add support for a new language:
Add the language to the
greetingsobject inhandleGreetmethodInclude translations for:
morning,afternoon,evening,friend,timeText,hopeTextUpdate the README.md supported languages table
Add the language code to the schema enum
📝 License
This project is licensed under the MIT License - see the LICENSE file for details.
🙏 Acknowledgments
Built with Model Context Protocol SDK
Inspired by the need for international, time-aware greetings
Perfect for Claude integrations and other MCP clients
📞 Support
🐛 Issues: GitHub Issues
💬 Discussions: GitHub Discussions
📧 Email: gustavorobertux@gmail.com
Made with ❤️ for the MCP community
Available Tools
1 toolgreetA
Returns an appropriate greeting based on the current time (good morning, good afternoon, or good evening)
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Person's name to personalize the greeting (optional) | |
| language | No | Language for the greeting (en, pt, es, fr) | en |
| timezone | No | Timezone for the greeting (defaults to America/Sao_Paulo) | America/Sao_Paulo |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly communicates that the tool computes a greeting from the time of day and returns it, with no indication of side effects. It could still mention the role of the timezone parameter more explicitly, but the current time-based behavior is well disclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence that immediately states the action, output, and deciding factor. The parenthetical examples add clarity without unnecessary words, making it highly efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple, all parameters are optional and well-documented in the schema, and the description captures the main behavior. The only notable gap is that no output schema is present and the description does not explicitly state the return type, though the examples strongly imply a plain string greeting.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the input schema already documents all three parameters: name, language enum, and timezone default. The description adds value for the time-based behavior but does not add per-parameter meaning beyond the schema, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Returns'), a clear resource ('an appropriate greeting'), and the core mechanism ('based on the current time'). It also gives concrete examples of the output ('good morning, good afternoon, or good evening'), making the tool's purpose unambiguous even without sibling comparisons.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit when-to-use or when-not-to-use guidance, and no sibling tools exist to distinguish against. The use case is implied by the behavior description, but the tool does not actively instruct the agent on when it should be chosen.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- First observed
greet
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion or overlap. The single 'greet' tool is unambiguous in its purpose.
The tool name 'greet' is a clear, concise verb that directly matches the server's purpose. With only one tool, naming consistency is inherently maintained.
The server's scope is limited to providing time-based greetings, and a single tool fully fulfills that purpose. The count is appropriate for the narrow, well-defined domain.
The tool covers the full range of greeting categories (morning, afternoon, evening) and requires no additional operations. The surface is completely sufficient for its stated purpose.
Maintenance
Related MCP Connectors
Create personalized greetings by name in the tone you choose. Get quick suggestions for friendly i…
Greet people by name with friendly, customizable messages. Toggle Pirate Mode to speak like a swas…
Send friendly, personalized greetings by name. Switch to a playful pirate voice for themed salutat…
Send friendly, personalized greetings on demand. Generate quick salutations with a simple prompt.…
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides time and timezone functionality for LLMs, enabling them to get current time information across different timezones and convert times between zones.2MIT
- AlicenseCqualityDmaintenanceProvides current time and date information with timezone support and multiple formatting options. Enables AI assistants to answer time-related queries in different timezones with detailed temporal information.26 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to greet users in 7 different languages including English, Spanish, French, German, Japanese, Chinese, and Korean. A lightweight multilingual greeting tool for the Model Context Protocol.MIT
- FlicenseBqualityDmaintenanceProvides various utilities including timezone-aware time queries, basic calculator operations, multilingual greetings, code review prompts, and AI image generation through Hugging Face API.5-