timezone — Hectares to acres MCP Tool
timezone
(timezone) is one of 31 tools on the
Hectares to acres
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call timezone from your client
- Claude Code Hectares to acres timezone run in your project directory
- Claude Desktop Hectares to acres timezone ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Hectares to acres timezone ~/.cursor/mcp.json
- VS Code Hectares to acres timezone .vscode/mcp.json
- Zed Hectares to acres timezone ~/.config/zed/settings.json
- Windsurf Hectares to acres timezone ~/.codeium/windsurf/mcp_config.json
- Cline Hectares to acres timezone ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Hectares to acres timezone ~/.gemini/settings.json
- Grok Hectares to acres timezone .mcp.json (in your project root)
- ChatGPT Hectares to acres timezone Settings → Connectors → Advanced → Developer mode
- Claude.ai Hectares to acres timezone Settings → Connectors → Add custom connector
- LangChain Hectares to acres timezone pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http hectare-to-acre https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/hectare-to-acre/mcp
Other tools on this server
- hectare-to-acre
- utc-time
- validate-json
- normalize-url
- inspect-robots
- domain-shape
- citation
- compatibility
- status-catalog
- iana-zones
- web-fetch
- fetch-status
- github-repo-shape
- weather-hint
- memory-key-count
- file-path-ok
- browser-url-ok
- think-steps
- search-query-len
- hn-front-count
- lib-docs-hint
- playwright-url-ok
- figma-url-shape
- jira-key-shape
- geo-hint
- calc-eval
- wiki-title-ok
- agent-tool-index
- people-search-index
- agent-ads-index
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.