usesignal_convert_timestamp — useSignal MCP Tool
usesignal_convert_timestamp
(usesignal convert timestamp) is one of 12 tools on the
useSignal
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call usesignal_convert_timestamp from your client
- Claude Code useSignal usesignal_convert_timestamp run in your project directory
- Claude Desktop useSignal usesignal_convert_timestamp ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor useSignal usesignal_convert_timestamp ~/.cursor/mcp.json
- VS Code useSignal usesignal_convert_timestamp .vscode/mcp.json
- Zed useSignal usesignal_convert_timestamp ~/.config/zed/settings.json
- Windsurf useSignal usesignal_convert_timestamp ~/.codeium/windsurf/mcp_config.json
- Cline useSignal usesignal_convert_timestamp ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI useSignal usesignal_convert_timestamp ~/.gemini/settings.json
- Grok useSignal usesignal_convert_timestamp .mcp.json (in your project root)
- ChatGPT useSignal usesignal_convert_timestamp Settings → Connectors → Advanced → Developer mode
- Claude.ai useSignal usesignal_convert_timestamp Settings → Connectors → Add custom connector
- LangChain useSignal usesignal_convert_timestamp pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http usesignal https://www.usesignal.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 3 October 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.