get_signals — signal bureau MCP Tool Read-only
get_signals
(get signals) is one of 22 tools on the
signal bureau
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_signals from your client
- Claude Code signal bureau get_signals run in your project directory
- Claude Desktop signal bureau get_signals ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor signal bureau get_signals ~/.cursor/mcp.json
- VS Code signal bureau get_signals .vscode/mcp.json
- Zed signal bureau get_signals ~/.config/zed/settings.json
- Windsurf signal bureau get_signals ~/.codeium/windsurf/mcp_config.json
- Cline signal bureau get_signals ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI signal bureau get_signals ~/.gemini/settings.json
- Grok signal bureau get_signals .mcp.json (in your project root)
- ChatGPT signal bureau get_signals Settings → Connectors → Advanced → Developer mode
- Claude.ai signal bureau get_signals Settings → Connectors → Add custom connector
- LangChain signal bureau get_signals pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http signal-bureau https://api.signalbureau.ai/api/mcpOther tools on this server
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.