Dust Postman Railway MCP Server

Dust MCP Server with advanced agent conversation features

Local serverstdioTypeScript

What is the Dust Postman Railway MCP server?

Most developer tooling work still happens through a UI a human drives. Dust Postman Railway MCP server moves it into the conversation instead. Dust MCP Server with advanced agent conversation features.

The short version

🚀 A TypeScript-based MCP (Model Context Protocol) Server with advanced agent conversation features.

  • ✅ TypeScript-powered MCP server
  • 🏗️ Modern ES2022+ JavaScript features
  • 🔍 Built-in API documentation
  • 🧪 Comprehensive test suite with Jest
  • 🛠️ Developer-friendly tooling
  • 🔄 Hot-reloading development server

The tools it exposes

The server publishes 14 tools. What each one is for:

  • list_workspace_vaults — List all workspace vaults
  • list_assistants — List available assistants
  • list_data_source_views — List data source views
  • get_conversation_events — Get conversation events
  • get_data_sources — Get available data sources
  • search_assistants_by_name — Search for assistants by name
  • get_conversation — Get conversation details
  • retrieve_document — Retrieve a document
  • get_app_run — Get application run details
  • get_events_for_message — Get events for a specific message
  • upsert_document — Create or update a document
  • get_documents — Get multiple documents

Getting it running

Installation goes through your MCP client rather than a global install: point it at COPY on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What it needs from you

Configuration is passed through the environment: DEFAULT_WORKSPACE_ID, WORKSPACE_DEFAULT_API_KEY, DUST_API_KEY, DUST_WORKSPACE_ID, DUST_AGENT_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Ensure you have curl installed. For testing with netcat (nc), install it using: - macOS: brew install netcat - Ubuntu/Debian: sudo apt-get install netcat

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Dust Postman Railway's toolset — list_workspace_vaults, list_assistants, list_data_source_views and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ma3u; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Dust Postman Railway's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Dust Postman Railway.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
list_workspace_vaultsList all workspace vaults
list_assistantsList available assistants
list_data_source_viewsList data source views
get_conversation_eventsGet conversation events
get_data_sourcesGet available data sources
search_assistants_by_nameSearch for assistants by name
get_conversationGet conversation details
retrieve_documentRetrieve a document
get_app_runGet application run details
get_events_for_messageGet events for a specific message
upsert_documentCreate or update a document
get_documentsGet multiple documents
create_conversationStart a new conversation
create_messageSend a message

How to install the Dust Postman Railway MCP server

{
  "mcpServers": {
    "dust-mcp-server-postman-railway": {
      "command": "npx",
      "args": ["-y", "COPY"],
      "env": {
        "DEFAULT_WORKSPACE_ID": "your-value",
        "WORKSPACE_DEFAULT_API_KEY": "your-value",
        "DUST_API_KEY": "your-value",
        "DUST_WORKSPACE_ID": "your-value",
        "DUST_AGENT_ID": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

Ensure you have curl installed. For testing with netcat (nc), install it using: - macOS: brew install netcat - Ubuntu/Debian: sudo apt-get install netcat

VariableDescriptionRequired
DEFAULT_WORKSPACE_IDConfiguration value read at startup.Optional
WORKSPACE_DEFAULT_API_KEYCredential the server authenticates with.Yes
DUST_API_KEYCredential the server authenticates with.Yes
DUST_WORKSPACE_IDConfiguration value read at startup.Optional
DUST_AGENT_IDConfiguration value read at startup.Optional

Example prompts to try

  • Use Dust Postman Railway to list workspace vaults.
  • Use Dust Postman Railway to list assistants.
  • Use Dust Postman Railway to list data source views.

Frequently asked questions

It connects Dust Postman Railway to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (list_workspace_vaults, list_assistants, list_data_source_views, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Dust Postman Railway directly.