Enables persistent agent workspaces by storing tasks, files, and activity logs in MongoDB Atlas, featuring user isolation and real-time progress tracking for autonomous agents.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@TTG Scratchpad MCP Serversave my research notes to a file called draft.md"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
TTG Scratchpad MCP Server
Production-ready MCP server for agent workspace/scratchpad functionality with MongoDB persistence and user isolation.
Features
Persistent Workspaces: Tasks and files stored in MongoDB Atlas
User Isolation: Each user has their own isolated workspace (via X-User-ID header)
File Management: Create, read, update, delete files in workspace
Progress Tracking: Real-time progress updates visible in chat widget
Activity Logging: Full audit trail of workspace operations
Bearer Authentication: Secure API access via MCP_API_KEYS
Tools
Workspace Management
scratchpad_start- Start a new task workspacescratchpad_update- Update progress during taskscratchpad_complete- Mark task as completescratchpad_demo- Demo widget with sample data
File Management
scratchpad_write_file- Save file to workspacescratchpad_read_file- Read file from workspacescratchpad_list_files- List all workspace filesscratchpad_delete_file- Delete file from workspace
Local Development
Prerequisites
Python 3.11+
MongoDB Atlas cluster (ttg-workspaces)
Setup
Run Locally
Server runs on http://localhost:8001/mcp
Test Without Database
The server runs in demo/stateless mode if MONGODB_URI is not set. Useful for UI testing.
Deployment (Render)
1. Push to GitHub
2. Configure Render Environment Variables
In Render dashboard, add these environment variables:
Variable | Value | Notes |
|
| Your ttg-workspaces connection string |
|
| Must match LibreChat SCRATCHPAD_MCP_TOKEN |
Do NOT set PORT - Render provides it automatically.
3. Verify Deployment
After deploy, test the /mcp endpoint:
LibreChat Configuration
librechat.yaml
LibreChat .env
Database Schema
Collections
workspaces
files
activity_logs
Security
Bearer token authentication via
MCP_API_KEYSUser isolation via
X-User-IDheader (provided by LibreChat)All database queries scoped by user_id
Input validation on file paths and content
Troubleshooting
"No HTTP request context available"
Tool called outside of request context. Ensure using FastMCP 0.5.0+.
"X-User-ID header required"
LibreChat not sending user ID. Check librechat.yaml headers config.
"MONGODB_URI environment variable required"
Set MONGODB_URI in Render dashboard or local .env.
Connection timeout
Check MongoDB Atlas network access - ensure Render IP is whitelisted or use 0.0.0.0/0 for all access.