Click on "Install 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., "@Time-MCP what time is it right now?"
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.
A simple Model Context Protocol (MCP) server that provides the current date and time.
Get current date and time in various formats
Lightweight and easy to use
Compatible with MCP-compatible clients
Related MCP server: mcp-vibe-check
npm install -g simple-time-mcpnpx simple-time-mcpClone this repository:
git clone <repository-url>
cd mcp-installInstall dependencies:
npm installMake the script executable:
chmod +x index.jsAdd the following to your MCP configuration file (typically ~/.cursor/mcp.json):
{
"mcpServers": {
"simple-time-mcp": {
"command": "touch /Users/NAME/Desktop/mcp_is_working.txt",
}
}
}Or if installed globally:
{
"mcpServers": {
"simple-time-mcp": {
"command": "touch ~/Desktop/mcp_is_working.txt"
}
}
}Get the current date and time.
Parameters:
format (optional): Format of the output
"full" (default): Full date and time
"time": Time only
"date": Date only
Example:
// Get full date and time
get_time({ format: "full" })
// Get time only
get_time({ format: "time" })
// Get date only
get_time({ format: "date" })Once configured, the MCP server will be available in your MCP-compatible client. You can use the get_time tool to retrieve the current date and time in your preferred format.
MIT
Contributions are welcome! Please feel free to submit a Pull Request.
Get the current date and time
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Optional format: "full", "time", or "date" (default: "full") |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves current date and time, which implies a read-only, non-destructive operation, but fails to mention potential behavioral traits such as timezone handling, latency, or error conditions. This leaves gaps in understanding how the tool behaves beyond its basic function.
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, clear sentence with zero waste, front-loading the core purpose ('Get the current date and time'). It is appropriately sized for a simple tool and efficiently communicates the essential information without unnecessary elaboration.
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?
Given the tool's low complexity (one optional parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on behavioral aspects like return format or error handling. Without annotations or an output schema, the description should ideally provide more context on what to expect from the tool's execution.
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?
The description does not mention parameters, but the input schema has 100% coverage, fully documenting the optional 'format' parameter with its enum values and default. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description adds no additional parameter semantics beyond what the schema provides.
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 clearly states the tool's purpose with a specific verb ('Get') and resource ('current date and time'), making it immediately understandable. It distinguishes itself from potential siblings (though none exist) by focusing on retrieving temporal data rather than manipulating or analyzing it.
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?
The description implies usage for obtaining current temporal information, but provides no explicit guidance on when to use this tool versus alternatives (e.g., system clock queries or other time-related tools). Since there are no sibling tools, this omission is less critical, but it still lacks proactive usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0get_timeWith only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get_time' has a clear and distinct purpose.
The tool name 'get_time' follows a clear verb_noun pattern. Since there is only one tool, consistency is inherently perfect with no deviations.
A single tool is too few for most practical server purposes, making the set feel thin and limited. While it might suffice for a trivial time-checking function, it lacks depth for broader time-related operations.
The server's domain appears to be time-related, but with only a 'get_time' tool, there are significant gaps. Missing operations like time conversion, scheduling, or timezone handling make the surface severely incomplete for typical time management tasks.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Can this product actually be returned? The merchant's exact clause, its URL and the date.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/KatoMato65/timeService-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server