Skip to content About The people and vision powering Probo Blog The latest news from Probo Stories Hear from our customers Docs Documentation for Probo GitHub Explore our open-source compliance tools

Zed

Zed is a fast, collaborative code editor with native MCP support.

  • Zed editor installed
  • Probo API token (see Authentication)
  • Your Probo instance URL

Open Zed settings by pressing Cmd+, (Mac) or Ctrl+, (Linux/Windows), or go to Zed → Settings.

Add the Probo MCP Server to your settings:

{
"context_servers": {
"probo": {
"settings": {
"url": "https://your-probo-instance.com/api/mcp/v1",
"headers": {
"Authorization": "Bearer your_api_token_here"
}
}
}
}
}

Update these values:

  • your-probo-instance.com → Your Probo instance URL
  • your_api_token_here → Your API token from Probo

Restart Zed to load the configuration.

Once configured, you can use Probo tools through Zed’s AI assistant:

Example queries:

"List all high-priority risks in my organization"
"Add a new vendor called CloudBackup Inc"
"Show me all open nonconformities"

The assistant will automatically use the appropriate Probo MCP tools to fulfill your requests.

For security, use environment variables for your API token:

{
"context_servers": {
"probo": {
"settings": {
"url": "https://your-probo-instance.com/api/mcp/v1",
"headers": {
"Authorization": "Bearer ${PROBO_API_TOKEN}"
}
}
}
}
}

Set the environment variable before launching Zed:

Terminal window
export PROBO_API_TOKEN="your_api_token_here"
zed

Configure different Probo 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}"
}
}
}
}
}

Problem: Probo tools aren’t available in the AI assistant

Solutions:

  1. Verify the configuration syntax is correct
  2. Restart Zed completely
  3. Check Zed logs for connection errors
  4. Test the URL and token with curl:
    Terminal window
    curl -H "Authorization: Bearer YOUR_TOKEN" \
    https://your-probo-instance.com/api/mcp/v1/health

Problem: 401 Unauthorized errors

Solutions:

  1. Regenerate your API token in Probo
  2. Verify the token is correctly formatted as Bearer your_token
  3. Check for extra spaces or newlines in the token
  4. Ensure the token hasn’t been revoked

Problem: Cannot connect to Probo server

Solutions:

  1. Verify your Probo instance URL is correct
  2. Check network connectivity
  3. Ensure HTTPS is used for production instances
  4. Verify firewall rules allow outbound connections
  • Use environment variables for API tokens
  • Create separate tokens for each environment
  • Rotate tokens every 90 days
  • Use HTTPS for production connections
  • Monitor token usage in Probo settings

Zed with Probo MCP provides:

  • Fast, responsive AI assistance
  • Real-time compliance context during coding
  • Collaborative editing with compliance awareness
  • Native MCP integration without plugins
  • Low-latency tool execution