Manual setup required. The maintainer's config contains paths only you know - edit the placeholders below before adding it to Claude Code.
1
Prepare the server locally
Run this once before adding it to Claude Code.
git clone https://github.com/ma3u/dust-mcp-server-postman-railway.git
cd dust-mcp-server-postman-railway
npm install2
Register it in Claude Code
claude mcp add -e "WORKSPACE_DEFAULT_API_KEY=${WORKSPACE_DEFAULT_API_KEY}" dust-mcp-server -- node /path/to/dust-mcp-server/dist/index.jsReplace any placeholder paths in the command with the real path on your machine.
Required:
WORKSPACE_DEFAULT_API_KEY+ 4 optional3
Make your agent remember this setup
dust-mcp-server's config, env vars, and the gotchas you hit — recalled in every future Claude Code, Cursor, and Codex session.
npx conare@latestFree · one command · indexes the sessions already on disk. Set up in the browser instead →
What it does
- TypeScript-powered MCP server implementation
- Advanced agent conversation and session management
- Hot-reloading development server
- Comprehensive test suite with Jest
- Environment-based configuration
Environment Variables
PORTPort for the server to run onNODE_ENVEnvironment mode (e.g., development)DEFAULT_WORKSPACE_IDThe ID of the default Dust workspaceWORKSPACE_DEFAULT_API_KEYrequiredAPI key for the Dust workspaceWORKSPACE_DEFAULT_NAMEName of the default workspaceTry it
→Start a new conversation session with my default Dust workspace.
→Send a message to the current active conversation session.
→Check the status of my current Dust session.
→End the current conversation session.
Original README from ma3u/dust-mcp-server-postman-railway
Dust MCP Server
🚀 A TypeScript-based MCP (Model Context Protocol) Server with advanced agent conversation features.
GitHub Repository: dust-mcp-server-postman-railway
User Manual
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
- 📦 Module aliases for clean imports
- 🔒 Environment-based configuration
- 🧩 Extensible architecture
🚀 Getting Started
⚙️ Prerequisites
Before you begin, ensure you have the following installed:
- Node.js (v18+ required, v20+ recommended)
- npm (included with Node.js)
- TypeScript (included as a dev dependency)
- Git (for version control)
🛠️ Installation
Clone the repository
git clone https://github.com/ma3u/dust-mcp-server-postman-railway.git cd dust-mcp-server-postman-railwayInstall dependencies
npm installSet up environment variables
Create a
.envfile in the root directory with the following variables:PORT=3000 NODE_ENV=development DEFAULT_WORKSPACE_ID=default WORKSPACE_DEFAULT_API_KEY=your_api_key_here WORKSPACE_DEFAULT_NAME=Default Workspace
🏗️ Development
Start the development server
npm run devThis will start the server with hot-reloading enabled.
Build for production
npm run build npm startRun tests
npm test # Run all tests npm run test:watch # Run tests in watch mode npm run test:coverage # Generate test coverage reportLinting and Formatting
npm run lint # Check for linting errors npm run lint:fix # Automatically fix linting issues npm run format # Format code using Prettier
Developer Manual
Architecture
[Architecture overview]
Agent Conversation Flow
The following diagram illustrates the conversation flow between MCP Client, MCP Server, and Dust with session management:
sequenceDiagram
participant User
participant MCPClient as MCP Client
participant MCPServer as MCP Server
participant SessionMgr as Session Manager
participant ConvMgr as Conversation Manager
participant Dust as Dust Service
%% Session Initialization
User->>MCPClient: Start New Session
MCPClient->>MCPServer: POST /api/sessions
MCPServer->>SessionMgr: createSession()
SessionMgr-->>MCPServer: {sessionId, status: 'active'}
MCPServer->>ConvMgr: new Conversation(sessionId)
ConvMgr-->>MCPServer: {conversationId, state: 'initializing'}
MCPServer-->>MCPClient: {sessionId, conversationId, status: 'active'}
MCPClient-->>User: Session Ready
%% Message Flow
loop While Session Active
User->>MCPClient: Send Message
MCPClient->>MCPServer: POST /api/conversations/{conversationId}/messages
MCPServer->>ConvMgr: processMessage(message)
alt Has Files
ConvMgr->>FileUploadHandler: handleUpload(files)
FileUploadHandler-->>ConvMgr: {fileIds, paths}
end
ConvMgr->>Dust: forwardMessage(conversationId, message, files)
Dust-->>ConvMgr: {response, metadata}
ConvMgr->>ConversationHistory: addMessage(message, response)
MCPServer-->>MCPClient: {response, state, metadata}
MCPClient-->>User: Display Response
%% Timeout Handling
alt Idle Timeout Reached
ConvMgr->>ConvMgr: handleIdleTimeout()
ConvMgr->>SessionMgr: updateSession(sessionId, {state: 'idle'})
SessionMgr-->>ConvMgr: {status: 'updated'}
ConvMgr-->>MCPServer: {event: 'stateChange', state: 'idle'}
MCPServer-->>MCPClient: {event: 'sessionIdle'}
end
end
%% Session Termination
User->>MCPClient: End Session
MCPClient->>MCPServer: DELETE /api/sessions/{sessionId}
MCPServer->>SessionMgr: deleteSession(sessionId)
SessionMgr->>ConvMgr: destroy()
ConvMgr->>ConversationHistory: clear()
ConvMgr-->>SessionMgr: {status: 'destroyed'}
SessionMgr-->>MCPServer: {status: 'deleted'}
MCPServer-->>MCPClient: {status: 'session_ended'}
MC