Zed
Connect the native support of the Zed editor to the platform with a comprehensive OAuth token, including multi-medium setting and troubleshooting guide.
Zed is a fast, collaborative code editor with native support forMCP.
Prerequisites
Section entitled ‘Prerequisites’- Zed editor installed
- Scoped the platform OAuth token (see Authentication)
- Your platform court URL
Endpoint
Section entitled “Endpoint”Choose the end point for your platform environment:
| Environment | MCP URL |
|---|---|
| the platform US | https://us.probo.com/api/mcp/v1 |
| the platform EU | https://eu.probo.com/api/mcp/v1 |
| Custom | https://your-probo-instance.com/api/mcp/v1 |
The ___ZBT_I18N_RUNTIME_BLOCK_171__ segment is required.
Configuration
Section entitled “Configuration”1. Open Zed Settings
Section entitled “1. Open Zed Settings”Open the Zed settings by pressing ___ZBT_I18N_RUNTIME_BLOCK_174__ (Mac) or ___ZBT_I18N_RUNTIME_BLOCK_175__ (Linux/Windows) or by Zed → Settings.
2. Edit Configuration
Section entitled “2. Edit Configuration”Add the MCPServer platform to your settings:
{ "context_servers": { "probo": { "settings": { "url": "https://your-probo-instance.com/api/mcp/v1", "headers": { "Authorization": "Bearer your_api_token_here" } } } }}3. Replace Placeholders
Section entitled “Replace Placeholders”Update these values:
your-probo-instance.com→ URL of your platform instanceyour_api_token_here→ Your OAuth token on the platform
4. Restart Zed
Section entitled “Restart Zed”Open Zed again to load the configuration.
Once configured, you can use the platform tools through Zed’s artificial intelligence assistant:
Example queries:
"List all high-priority risks in my organization""Add a new third party called CloudBackup Inc""Show me all open nonconformities"The assistant will automatically use the tools of the appropriate MCP platform to fulfill your requests.
Environment Variables
Section entitled ‘Environment Variables’For security, use an environmental variable for your OAuth token:
{ "context_servers": { "probo": { "settings": { "url": "https://your-probo-instance.com/api/mcp/v1", "headers": { "Authorization": "Bearer ${PROBO_API_TOKEN}" } } } }}Setting the environment variable before launching Zed:
export PROBO_API_TOKEN="your_api_token_here"zedMultiple Environments
Section entitled “Multiple Environments”Differently configure the platform instances for development and production:
{ "context_servers": { "probo-dev": { "settings": { "url": "http://localhost:8080/api/mcp/v1", "headers": { "Authorization": "Bearer ${PROBO_DEV_TOKEN}" } } }, "probo-prod": { "settings": { "url": "https://probo.company.com/api/mcp/v1", "headers": { "Authorization": "Bearer ${PROBO_PROD_TOKEN}" } } } }}Troubleshooting
Section “Troubleshooting”Authentication Errors
Section “Authentication Errors”Problem: 401 Unauthorized errors
Solutions:
- Create an OAuth replacement token in the platform
- Check if the token is correctly formatted as
Bearer your_token - Check for additional spaces or newlines in the token
- Ensure the token hasn’t been revoked
Connection Issues
Section entitled “Connection Issues”Problem: Can't connect to the platform server
Solutions:
- Check if the URL of the platform’s court is correct
- Check network connectivity
- Make sure that HTTPS is used for production courts
- Verify firewall rules allow outbound connections
Best Practices
Section “Best Practices”- Use environment variables for OAuth tokens
- Create separate tokens for each environment
- Rotate tokens every 90 days
- Use HTTPS for production connections
- Monitor token usage in the platform settings
Features
Section entitled “Features”Zed with the platformMCPofer:
- Fast, responsive AI assistance
- Real-time compliance context during coding
- Collaborative editing with compliance awareness
- Native MCP integration without plugins
- Low-latency tool execution