get_record — signal bureau MCP Tool Read-only

get_record (get record) 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_record from your client

Claude Code signal bureau get_record run in your project directory
Claude Desktop signal bureau get_record ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor signal bureau get_record ~/.cursor/mcp.json
VS Code signal bureau get_record .vscode/mcp.json
Zed signal bureau get_record ~/.config/zed/settings.json
Windsurf signal bureau get_record ~/.codeium/windsurf/mcp_config.json
Cline signal bureau get_record ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI signal bureau get_record ~/.gemini/settings.json
Grok signal bureau get_record .mcp.json (in your project root)
ChatGPT signal bureau get_record Settings → Connectors → Advanced → Developer mode
Claude.ai signal bureau get_record Settings → Connectors → Add custom connector
LangChain signal bureau get_record pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http signal-bureau https://api.signalbureau.ai/api/mcp

Other tools on this server

start_here
top_accelerating
search_entities
get_entity
get_truth_record
ask
get_answer
get_signals
get_calibration
get_events
get_corroborated
todays_brief
propose_topic
get_quote
create_order
get_order
get_watch_feed
get_desk_feed
get_account
get_feedback_status
send_feedback

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.

signal bureau MCP server