DRM3 Rails · for anyone who holds data
Run a desk with an agent.
Everything the console does, the API does too. An agent with an admin key can point a desk at its data, build the signals, invite readers and send the digest.
Get a key
Open your desk and mint an admin key under Desk settings. The key is shown once, and it works on its own desk. No desk yet? Contact us.
Connect over MCP
Point any MCP client at the door and pass the key. In Claude Code:
claude mcp add --transport http signaldesk https://signaldesk.drm3.network/mcp \ --header "Authorization: Bearer YOUR_ADMIN_KEY"
The descriptor is at /.well-known/mcp.json. Every tool is also a JSON
route, called with the same key in an Authorization: Bearer header.
What an agent can do
- set_signal_desk and get_signal_desk point a desk at its data and read the setup back.
- build_signals reads the data and files one signal per source row. signal_build_status shows each build.
- invite_reader, remove_reader and signal_access manage who can read the desk.
- ask_desk answers a question from the desk's own record. summarize_signal sums up one signal, with citations.
- brief_watchlist and send_digest tell readers what is new.
The rules the API keeps
- A private desk answers a request with no key with a refusal, never with data.
- A key reads and writes its own desk.
- A customer's records never leave the desk they belong to.
A guided build
The Signal Desk skill walks an agent from a fresh key to a running desk.
Have a dataset in mind?
Tell us what you hold and who should read it, and we will show you what the desk would look like.