Custom Extensions Overview
Custom extensions allow you to add specialized capabilities to ZeroTwo beyond the built-in tools. Create custom integrations, connect proprietary systems, or leverage Model Context Protocol (MCP) servers for advanced functionality.What Are Custom Extensions?
Custom extensions are tools that extend ZeroTwo’s capabilities:MCP Servers
Custom Tools
API Integrations
Internal Systems
Model Context Protocol (MCP)
MCP is an open protocol that standardizes how AI systems connect to data sources and tools.What is MCP?
Model Context Protocol provides:- Standardized communication between AI and external systems
- Reusable server implementations
- Secure, controlled access to resources
- Community-driven ecosystem of integrations
MCP Architecture
- Client: ZeroTwo (requests resources/tools)
- Server: MCP server (provides capabilities)
- Resources: Data, files, system access
Built-in MCP Servers
ZeroTwo includes pre-configured MCP servers:- GitHub
- Linear
- Notion
- Supabase
- Read repository contents
- Browse file structures
- View commits and history
- Read issues and pull requests
- Search code across repos
Adding Custom MCP Servers
Connect your own MCP servers to ZeroTwo.Using Public MCP Servers
Find MCP server
- MCP Server Registry
- Community implementations
- Official vendor servers
Get server details
- Server URL or command
- Authentication method
- Required permissions
Add to ZeroTwo
Configure server
- Name: Friendly name for the server
- URL: Server endpoint
- Authentication: Choose auth method
- API Key: If required
- Select which resources the server can access
- Choose allowed operations
- Set usage limits
Test connection
Use in conversations
Self-Hosted MCP Servers
Run MCP servers on your own infrastructure:- Local Development
- Cloud Deployment
- Docker Container
Install server
Start server
Expose with ngrok
Add to ZeroTwo
Creating Custom MCP Servers
Build your own MCP server from scratch.Set up project
Create server
Add resources
Implement authentication
Deploy and connect
Custom API Tools
Create custom tools that call your APIs.Simple API Tool
Define API endpoint
Add in ZeroTwo
Configure tool
- Name:
get_inventory - Description: “Check inventory levels for products”
- API Endpoint: Your API URL
- Method: POST
- Authentication: Bearer token / API key
Test tool
Use in conversation
get_inventory tool → Returns inventory infoAdvanced Tool Configuration
Request customization
Request customization
Response processing
Response processing
Rate limiting
Rate limiting
- Requests per minute
- Requests per hour
- Burst allowance
- Cooldown period
Caching
Caching
- TTL (time to live)
- Cache key strategy
- Invalidation rules
Database Connections (Enterprise)
Connect directly to databases.- SQL Databases
- NoSQL Databases
- Data Warehouses
- PostgreSQL
- MySQL
- SQL Server
- Oracle
- SQLite
- Read-only by default
- Query allowlist
- Row limits
- Timeout controls
Extension Marketplace
Browse and install community extensions.Finding Extensions
Extension sources:- ZeroTwo Extension Marketplace (built-in)
- GitHub MCP Server Registry
- NPM packages
- Community forums
- 📊 Data & Analytics
- 🔧 Development Tools
- 🤝 CRM & Sales
- 📝 Productivity
- 🎨 Creative Tools
- 🔐 Security & Compliance
Installing from Marketplace
Browse marketplace
Search or browse
- Category
- Popularity
- Recently added
- Search term
View details
- Description and capabilities
- Required permissions
- Reviews and ratings
- Installation instructions
- Pricing (if applicable)
Install
Configure
Activate
Managing Extensions
Keep your extensions organized and secure.Extension Settings
For each extension:- ✅ Enable/disable
- ⚙️ Configuration
- 🔐 Permissions
- 📊 Usage statistics
- 🔄 Update status
- 🗑️ Uninstall
Permissions Management
Review permissions
Review permissions
- Conversation history
- File uploads
- API credentials
- Project data
- Personal information
- 👀 Read-only
- ✏️ Read-write
- 🔐 Sensitive data access
- 🌐 Network access
Revoke permissions
Revoke permissions
- Open extension settings
- Click Permissions
- Toggle off unwanted permissions
- Extension functionality may be limited
Audit log
Audit log
- API calls made
- Data accessed
- Errors encountered
- Performance metrics
Updating Extensions
Auto-updates (default):- Extensions update automatically
- Security patches applied immediately
- Breaking changes delayed with notice
- Settings > Extensions
- See “Update Available” badge
- Review changelog
- Click Update
Best Practices
Security first
Security first
- Use read-only database connections
- Implement proper authentication
- Review extension permissions regularly
- Use environment variables for secrets
- Audit extension activity logs
- Keep extensions updated
- Grant unnecessary permissions
- Hard-code API keys
- Skip security reviews
- Trust unverified extensions
- Expose production databases without limits
Test thoroughly
Test thoroughly
- Test in development environment
- Verify error handling
- Check rate limits
- Validate data transformations
- Test authentication failures
- Monitor performance
Monitor usage
Monitor usage
- API call counts
- Response times
- Error rates
- Cost (if applicable)
- User feedback
Document integrations
Document integrations
- Purpose of each extension
- Required setup steps
- Known limitations
- Troubleshooting guide
- Contact for issues
Troubleshooting
Extension not working
Extension not working
- Authentication failed
- Verify API keys are correct
- Check token hasn’t expired
- Ensure proper permissions
- Connection timeout
- Check server URL
- Verify network access
- Look for firewall blocks
- Invalid response
- Check API endpoint is correct
- Verify response format matches config
- Look at error logs
- Test extension with simple request
- Check extension activity log
- Verify API directly (Postman/curl)
- Contact extension developer
Permission denied
Permission denied
- Check extension has required permissions
- Verify your account has necessary role
- Review organization policies
- Check if extension is approved
MCP server connection failed
MCP server connection failed
- Verify server is running
- Check URL/endpoint is correct
- Test authentication credentials
- Look for SSL/TLS issues
- Check server logs

