Skip to main content

Zed Editor Integration

Learn how to integrate Buildable with the Zed editor through MCP.

Prerequisites​

  • Zed editor installed
  • Active Buildable account
  • Node.js for MCP server

Setup​

Step 1: Configure MCP in Zed​

Add the Buildable MCP server to your Zed configuration file:

{
"assistant": {
"mcp_servers": {
"buildable": {
"command": "npx",
"args": ["@buildable/mcp-server"],
"env": {
"BUILDABLE_API_KEY": "<your_full_api_key_here>",
"BUILDABLE_PROJECT_ID": "<your_project_id>",
"BUILDABLE_AI_ASSISTANT_ID": "<assistant_name>"
}
}
}
}
}

Step 2: Restart Zed​

After configuration, restart Zed to load the MCP integration.

Step 3: Verify Connection​

Open the assistant panel and verify that Buildable tools are available.

Features​

Native MCP Support​

Zed has built-in MCP support, providing seamless integration with Buildable's task system.

Task Management​

  • Access tasks directly from the editor
  • Update task status with natural language commands
  • Get contextual code suggestions based on active tasks

Code Intelligence​

  • AI-powered code completion using project context
  • Automated refactoring suggestions
  • Real-time code analysis

Usage​

Opening Tasks​

Use the command palette (Cmd+Shift+P) and search for "Buildable" to access task-related commands.

Updating Task Status​

Simply describe what you've completed, and the AI will update the appropriate task status.

Getting Code Suggestions​

Ask for help with specific tasks, and the AI will provide contextual code suggestions.

Best Practices​

  1. Keep assistant panel open: This helps maintain context throughout your coding session
  2. Use descriptive comments: Help the AI understand your intent
  3. Regular sync: Periodically sync with Buildable to ensure up-to-date task information

Troubleshooting​

Connection Issues​

  • Verify your API key is correct
  • Check that the MCP server is accessible
  • Ensure Node.js is properly installed

Performance​

  • Restart Zed if the assistant becomes unresponsive
  • Check your network connection
  • Verify the MCP server logs for errors