This guide helps you upgrade your plugged.in MCP Proxy from pre-release versions to the stable v1.0.0.
Version 1.0.0 is our first stable release, bringing together all the features developed during the pre-release phase with enhanced security, notifications, and developer tools.
- Notification Support: Real-time activity tracking
- RAG Integration: Document context in AI interactions
- Enhanced Security: Improved validation and sanitization
- Developer Tools: New inspector scripts for testing
- Better Debugging: Structured logging and error messages
Update your MCP server configuration to use v1.0.0:
{
"mcpServers": {
"pluggedin": {
"command": "npx",
"args": ["-y", "@pluggedin/mcp-proxy@1.0.0"],
"env": {
"PLUGGEDIN_API_KEY": "YOUR_API_KEY"
}
}
}
}npx -y @pluggedin/mcp-proxy@1.0.0 --pluggedin-api-key YOUR_API_KEYAfter updating the configuration:
- Claude Desktop: Restart the application
- Cline: Reload the VS Code window
- Cursor: Restart Cursor
- Check that the proxy connects successfully
- Test existing tools and resources
- Verify new features in the plugged.in App:
- Check notification center for MCP activities
- Test RAG queries if you have documents uploaded
Once upgraded, all MCP activities will be logged to the plugged.in App:
- Navigate to the Notifications page in plugged.in App
- See real-time updates for tool calls, resource reads, and prompts
- Configure notification preferences in your profile settings
If you're using the document library feature:
- Upload documents through the plugged.in App
- Enable RAG in the playground settings
- Your MCP interactions will automatically include document context
Test your setup with the new inspector tools:
# Clone the repository
git clone https://github.com/VeriTeknik/pluggedin-mcp.git
cd pluggedin-mcp
# Install dependencies
npm install
# Run the inspector
npm run inspectorNo new environment variables are required. Existing configurations remain valid:
PLUGGEDIN_API_KEY=your_api_key
PLUGGEDIN_API_BASE_URL=https://plugged.in # or your self-hosted URLNew features are automatically enabled. No configuration needed unless you want to customize behavior through the plugged.in App settings.
Solution: Ensure your profile has the notification capability enabled:
- Go to plugged.in App Settings
- Check your profile capabilities
- Enable "Notifications" if not already enabled
Solution: Clear any cached versions:
# Clear npx cache
npx clear-npx-cache
rm -rf ~/.npm/_npx
# Try again with explicit version
npx @pluggedin/mcp-proxy@1.0.0 --pluggedin-api-key YOUR_API_KEYSolution: Ensure you've updated all configuration files:
- Check Claude Desktop config at:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
- Restart the application completely
If you need to rollback to a previous version:
- Update your configuration to use a specific pre-release version:
{
"mcpServers": {
"pluggedin": {
"command": "npx",
"args": ["-y", "@pluggedin/mcp-proxy@0.5.10"],
"env": {
"PLUGGEDIN_API_KEY": "YOUR_API_KEY"
}
}
}
}- Restart your MCP client
Note: You'll lose access to the new features introduced in v1.0.0.
Version 1.0.0 includes performance improvements:
- Faster startup time
- Reduced memory usage
- Better handling of concurrent requests
No action required - these improvements are automatic.
This version includes security enhancements that are transparent to users:
- Improved input validation
- Better error handling
- Enhanced logging for debugging
These changes improve security without affecting normal usage.
Thank you for using plugged.in MCP Proxy!