mcp-server-time 0.5.1__tar.gz

mcp_server_time-0.5.1/.gitignore

@@ -0,0 +1,300 @@
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+lerna-debug.log*
+.pnpm-debug.log*
+
+# Diagnostic reports (https://nodejs.org/api/report.html)
+report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+*.lcov
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (https://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+jspm_packages/
+
+# Snowpack dependency directory (https://snowpack.dev/)
+web_modules/
+
+# TypeScript cache
+*.tsbuildinfo
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Optional stylelint cache
+.stylelintcache
+
+# Microbundle cache
+.rpt2_cache/
+.rts2_cache_cjs/
+.rts2_cache_es/
+.rts2_cache_umd/
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variable files
+.env
+.env.development.local
+.env.test.local
+.env.production.local
+.env.local
+
+# parcel-bundler cache (https://parceljs.org/)
+.cache
+.parcel-cache
+
+# Next.js build output
+.next
+out
+
+# Nuxt.js build / generate output
+.nuxt
+dist
+
+# Gatsby files
+.cache/
+# Comment in the public line in if your project uses Gatsby and not Next.js
+# https://nextjs.org/blog/next-9-1#public-directory-support
+# public
+
+# vuepress build output
+.vuepress/dist
+
+# vuepress v2.x temp and cache directory
+.temp
+.cache
+
+# Docusaurus cache and generated files
+.docusaurus
+
+# Serverless directories
+.serverless/
+
+# FuseBox cache
+.fusebox/
+
+# DynamoDB Local files
+.dynamodb/
+
+# TernJS port file
+.tern-port
+
+# Stores VSCode versions used for testing VSCode extensions
+.vscode-test
+
+# yarn v2
+.yarn/cache
+.yarn/unplugged
+.yarn/build-state.yml
+.yarn/install-state.gz
+.pnp.*
+
+build/
+
+gcp-oauth.keys.json
+.*-server-credentials.json
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+.DS_Store
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/

mcp_server_time-0.5.1/.python-version

@@ -0,0 +1 @@
+3.10

mcp_server_time-0.5.1/PKG-INFO

@@ -0,0 +1,211 @@
+Metadata-Version: 2.3
+Name: mcp-server-time
+Version: 0.5.1
+Summary: A Model Context Protocol server providing tools for time queries and timezone conversions for LLMs
+Author-email: Mariusz 'maledorak' Korzekwa <mariusz@korzekwa.dev>
+License: MIT
+Keywords: llm,mcp,time,timezone
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Requires-Python: >=3.10
+Requires-Dist: mcp>=1.0.0
+Requires-Dist: pydantic>=2.0.0
+Requires-Dist: tzdata>=2024.2
+Description-Content-Type: text/markdown
+
+# Time MCP Server
+
+A Model Context Protocol server that provides time and timezone conversion capabilities. This server enables LLMs to get current time information and perform timezone conversions using IANA timezone names, with automatic system timezone detection.
+
+### Available Tools
+
+- `get_current_time` - Get current time in a specific timezone or system timezone.
+  - Required arguments:
+    - `timezone` (string): IANA timezone name (e.g., 'America/New_York', 'Europe/London')
+
+- `convert_time` - Convert time between timezones.
+  - Required arguments:
+    - `source_timezone` (string): Source IANA timezone name
+    - `time` (string): Time in 24-hour format (HH:MM)
+    - `target_timezone` (string): Target IANA timezone name
+
+## Installation
+
+### Using uv (recommended)
+
+When using [`uv`](https://docs.astral.sh/uv/) no specific installation is needed. We will
+use [`uvx`](https://docs.astral.sh/uv/guides/tools/) to directly run *mcp-server-time*.
+
+### Using PIP
+
+Alternatively you can install `mcp-server-time` via pip:
+
+```bash
+pip install mcp-server-time
+```
+
+After installation, you can run it as a script using:
+
+```bash
+python -m mcp_server_time
+```
+
+## Configuration
+
+### Configure for Claude.app
+
+Add to your Claude settings:
+
+<details>
+<summary>Using uvx</summary>
+
+```json
+"mcpServers": {
+  "time": {
+    "command": "uvx",
+    "args": ["mcp-server-time"]
+  }
+}
+```
+</details>
+
+<details>
+<summary>Using pip installation</summary>
+
+```json
+"mcpServers": {
+  "time": {
+    "command": "python",
+    "args": ["-m", "mcp_server_time"]
+  }
+}
+```
+</details>
+
+### Configure for Zed
+
+Add to your Zed settings.json:
+
+<details>
+<summary>Using uvx</summary>
+
+```json
+"context_servers": [
+  "mcp-server-time": {
+    "command": "uvx",
+    "args": ["mcp-server-time"]
+  }
+],
+```
+</details>
+
+<details>
+<summary>Using pip installation</summary>
+
+```json
+"context_servers": {
+  "mcp-server-time": {
+    "command": "python",
+    "args": ["-m", "mcp_server_time"]
+  }
+},
+```
+</details>
+
+### Customization - System Timezone
+
+By default, the server automatically detects your system's timezone. You can override this by adding the argument `--local-timezone` to the `args` list in the configuration.
+
+Example:
+```json
+{
+  "command": "python",
+  "args": ["-m", "mcp_server_time", "--local-timezone=America/New_York"]
+}
+```
+
+## Example Interactions
+
+1. Get current time:
+```json
+{
+  "name": "get_current_time",
+  "arguments": {
+    "timezone": "Europe/Warsaw"
+  }
+}
+```
+Response:
+```json
+{
+  "timezone": "Europe/Warsaw",
+  "datetime": "2024-01-01T13:00:00+01:00",
+  "is_dst": false
+}
+```
+
+2. Convert time between timezones:
+```json
+{
+  "name": "convert_time",
+  "arguments": {
+    "source_timezone": "America/New_York",
+    "time": "16:30",
+    "target_timezone": "Asia/Tokyo"
+  }
+}
+```
+Response:
+```json
+{
+  "source": {
+    "timezone": "America/New_York",
+    "datetime": "2024-01-01T12:30:00-05:00",
+    "is_dst": false
+  },
+  "target": {
+    "timezone": "Asia/Tokyo",
+    "datetime": "2024-01-01T12:30:00+09:00",
+    "is_dst": false
+  },
+  "time_difference": "+13.0h",
+}
+```
+
+## Debugging
+
+You can use the MCP inspector to debug the server. For uvx installations:
+
+```bash
+npx @modelcontextprotocol/inspector uvx mcp-server-time
+```
+
+Or if you've installed the package in a specific directory or are developing on it:
+
+```bash
+cd path/to/servers/src/time
+npx @modelcontextprotocol/inspector uv run mcp-server-time
+```
+
+## Examples of Questions for Claude
+
+1. "What time is it now?" (will use system timezone)
+2. "What time is it in Tokyo?"
+3. "When it's 4 PM in New York, what time is it in London?"
+4. "Convert 9:30 AM Tokyo time to New York time"
+
+## Contributing
+
+We encourage contributions to help expand and improve mcp-server-time. Whether you want to add new time-related tools, enhance existing functionality, or improve documentation, your input is valuable.
+
+For examples of other MCP servers and implementation patterns, see:
+https://github.com/modelcontextprotocol/servers
+
+Pull requests are welcome! Feel free to contribute new ideas, bug fixes, or enhancements to make mcp-server-time even more powerful and useful.
+
+## License
+
+mcp-server-time is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

mcp_server_time-0.5.1/README.md

@@ -0,0 +1,193 @@
+# Time MCP Server
+
+A Model Context Protocol server that provides time and timezone conversion capabilities. This server enables LLMs to get current time information and perform timezone conversions using IANA timezone names, with automatic system timezone detection.
+
+### Available Tools
+
+- `get_current_time` - Get current time in a specific timezone or system timezone.
+  - Required arguments:
+    - `timezone` (string): IANA timezone name (e.g., 'America/New_York', 'Europe/London')
+
+- `convert_time` - Convert time between timezones.
+  - Required arguments:
+    - `source_timezone` (string): Source IANA timezone name
+    - `time` (string): Time in 24-hour format (HH:MM)
+    - `target_timezone` (string): Target IANA timezone name
+
+## Installation
+
+### Using uv (recommended)
+
+When using [`uv`](https://docs.astral.sh/uv/) no specific installation is needed. We will
+use [`uvx`](https://docs.astral.sh/uv/guides/tools/) to directly run *mcp-server-time*.
+
+### Using PIP
+
+Alternatively you can install `mcp-server-time` via pip:
+
+```bash
+pip install mcp-server-time
+```
+
+After installation, you can run it as a script using:
+
+```bash
+python -m mcp_server_time
+```
+
+## Configuration
+
+### Configure for Claude.app
+
+Add to your Claude settings:
+
+<details>
+<summary>Using uvx</summary>
+
+```json
+"mcpServers": {
+  "time": {
+    "command": "uvx",
+    "args": ["mcp-server-time"]
+  }
+}
+```
+</details>
+
+<details>
+<summary>Using pip installation</summary>
+
+```json
+"mcpServers": {
+  "time": {
+    "command": "python",
+    "args": ["-m", "mcp_server_time"]
+  }
+}
+```
+</details>
+
+### Configure for Zed
+
+Add to your Zed settings.json:
+
+<details>
+<summary>Using uvx</summary>
+
+```json
+"context_servers": [
+  "mcp-server-time": {
+    "command": "uvx",
+    "args": ["mcp-server-time"]
+  }
+],
+```
+</details>
+
+<details>
+<summary>Using pip installation</summary>
+
+```json
+"context_servers": {
+  "mcp-server-time": {
+    "command": "python",
+    "args": ["-m", "mcp_server_time"]
+  }
+},
+```
+</details>
+
+### Customization - System Timezone
+
+By default, the server automatically detects your system's timezone. You can override this by adding the argument `--local-timezone` to the `args` list in the configuration.
+
+Example:
+```json
+{
+  "command": "python",
+  "args": ["-m", "mcp_server_time", "--local-timezone=America/New_York"]
+}
+```
+
+## Example Interactions
+
+1. Get current time:
+```json
+{
+  "name": "get_current_time",
+  "arguments": {
+    "timezone": "Europe/Warsaw"
+  }
+}
+```
+Response:
+```json
+{
+  "timezone": "Europe/Warsaw",
+  "datetime": "2024-01-01T13:00:00+01:00",
+  "is_dst": false
+}
+```
+
+2. Convert time between timezones:
+```json
+{
+  "name": "convert_time",
+  "arguments": {
+    "source_timezone": "America/New_York",
+    "time": "16:30",
+    "target_timezone": "Asia/Tokyo"
+  }
+}
+```
+Response:
+```json
+{
+  "source": {
+    "timezone": "America/New_York",
+    "datetime": "2024-01-01T12:30:00-05:00",
+    "is_dst": false
+  },
+  "target": {
+    "timezone": "Asia/Tokyo",
+    "datetime": "2024-01-01T12:30:00+09:00",
+    "is_dst": false
+  },
+  "time_difference": "+13.0h",
+}
+```
+
+## Debugging
+
+You can use the MCP inspector to debug the server. For uvx installations:
+
+```bash
+npx @modelcontextprotocol/inspector uvx mcp-server-time
+```
+
+Or if you've installed the package in a specific directory or are developing on it:
+
+```bash
+cd path/to/servers/src/time
+npx @modelcontextprotocol/inspector uv run mcp-server-time
+```
+
+## Examples of Questions for Claude
+
+1. "What time is it now?" (will use system timezone)
+2. "What time is it in Tokyo?"
+3. "When it's 4 PM in New York, what time is it in London?"
+4. "Convert 9:30 AM Tokyo time to New York time"
+
+## Contributing
+
+We encourage contributions to help expand and improve mcp-server-time. Whether you want to add new time-related tools, enhance existing functionality, or improve documentation, your input is valuable.
+
+For examples of other MCP servers and implementation patterns, see:
+https://github.com/modelcontextprotocol/servers
+
+Pull requests are welcome! Feel free to contribute new ideas, bug fixes, or enhancements to make mcp-server-time even more powerful and useful.
+
+## License
+
+mcp-server-time is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.