Beyond Cursor, Copilot, and the big names, there’s a whole ecosystem of AI editors and app builders worth knowing about. Some are genuinely useful for specific workflows, and the “vibe coding” app builders have matured from novelty to practical tools. Here’s a practical guide to the ones that matter.
AI Editors Worth Trying
Zed AI
Zed is a high-performance editor written in Rust with native AI integration. Why consider it:
- Speed — significantly faster than VS Code/Cursor for large projects. File opening, search, and navigation are near-instant.
- Collaborative editing — real-time multiplayer editing built into the core, similar to Google Docs for code.
- AI integrated, not bolted on — AI features are part of the editor’s architecture, not an extension.
Getting started:
- Download from zed.dev (Mac and Linux; Windows in development)
- Configure your AI provider in Settings (supports Anthropic, OpenAI, Ollama)
- Use
Cmd+Enterfor inline AI assistance - Use the AI panel for chat-style interactions
Best for: developers who prioritize editor performance and work on large codebases where VS Code feels sluggish.
JetBrains AI Assistant
If you’re a JetBrains user (IntelliJ, PyCharm, WebStorm, GoLand), the AI Assistant keeps you in your existing workflow:
- Settings → Plugins → Install “AI Assistant”
- Sign in with your JetBrains account
- AI features appear in: code completion, context actions, chat panel, commit messages
Key features: AI-powered refactoring suggestions, test generation from context menus, and documentation generation. The advantage is deep integration with JetBrains’ already-excellent code analysis — AI suggestions are informed by the IDE’s understanding of types, dependencies, and project structure.
Continue (Open Source)
Continue is an open-source AI coding assistant that works as a VS Code and JetBrains extension:
- Install from the marketplace
- Configure your models (any provider — Claude, GPT, Gemini, local models)
- Full customization through
config.json
Why Continue matters: complete control over which models you use, how context is built, and what instructions the AI follows. If you want Copilot-style features but with your choice of model and no vendor lock-in, Continue is the answer.
{
"models": [
{
"title": "Claude Sonnet",
"provider": "anthropic",
"model": "claude-sonnet-4-20250514",
"apiKey": "YOUR_KEY"
}
],
"tabAutocompleteModel": {
"title": "Ollama",
"provider": "ollama",
"model": "starcoder2:3b"
}
}
App Builders: Practical Evaluation
The “vibe coding” tools have moved beyond demos. Here’s what actually works for production use.
v0 by Vercel
What it does: Generates React/Next.js UI from natural language prompts.
Setup: Go to v0.dev, sign in with your Vercel account.
What it’s good for:
- Frontend prototyping — describe a UI and get a working component in seconds
- Design-to-code — paste a screenshot or wireframe and get React code
- Component libraries — “create a data table with sorting, filtering, and pagination”
Practical workflow:
- Generate the component in v0
- Copy the code to your local project
- Integrate with your data layer and state management
- Customize styling to match your design system
Where it falls short: Complex state management, multi-page flows, and backend integration still require manual work. v0 is a starting point, not a complete solution.
Bolt by StackBlitz
What it does: Generates full-stack applications in the browser.
Setup: Go to bolt.new, start a conversation.
What it’s good for:
- Full-stack prototyping — “build a task management app with auth and a database”
- Quick demos and MVPs
- Learning — see how a complete app is structured
Key feature: Bolt runs entirely in the browser using WebContainers. No local setup needed. You can see the running application alongside the code.
Practical tip: Use Bolt to generate the scaffold, then git clone the result and continue development in your regular editor. Bolt’s in-browser editor isn’t where you want to do serious development.
Lovable
What it does: Generates production-quality web applications from descriptions.
Setup: lovable.dev, sign up and start describing.
Strengths: Lovable focuses on design quality — the generated UIs tend to look more polished than other app builders. It also handles deployment, giving you a live URL.
Best for: MVPs that need to look professional quickly. Landing pages, internal tools, and prototypes for stakeholder feedback.
Replit Agent
What it does: Builds and deploys applications from descriptions within Replit’s cloud IDE.
Setup: Sign up at replit.com, create a new project using Agent.
Unique advantage: Integrated hosting, database (Replit DB), and deployment. Your app is live the moment it’s built. No DevOps required.
Best for: Quick prototypes, hackathon projects, learning projects, and small tools that need to be deployed immediately.
MCP: The Integration Layer You Should Know About
Model Context Protocol (MCP) is becoming the standard for connecting AI tools to external services. Understanding it opens up custom workflows that none of the pre-built tools offer.
What MCP does: It defines a standard way for AI tools (Claude Code, Cursor, Windsurf) to talk to external services — databases, APIs, issue trackers, documentation systems.
Example: Building a custom MCP server
A simple MCP server that gives your AI tool access to your PostgreSQL database:
import { Server } from "@modelcontextprotocol/sdk/server/index.js";
const server = new Server({
name: "postgres-mcp",
version: "1.0.0",
});
server.setRequestHandler("tools/list", async () => ({
tools: [{
name: "query_database",
description: "Run a read-only SQL query",
inputSchema: {
type: "object",
properties: {
query: { type: "string", description: "SQL SELECT query" }
}
}
}]
}));
Now Claude Code or Cursor can query your database directly, making suggestions based on your actual schema and data.
Pre-built MCP servers worth knowing:
- GitHub MCP — lets AI tools interact with issues, PRs, and repo data
- Filesystem MCP — broader file access beyond the working directory
- Brave Search MCP — web search from within AI coding tools
- Database MCPs — PostgreSQL, SQLite, MongoDB connectors
The MCP ecosystem is growing rapidly. Check github.com/modelcontextprotocol/servers for the current directory.
Choosing the Right Tool for the Right Job
The landscape is wide, but the decision is often simpler than it looks:
- Need a quick UI? → v0
- Need a full prototype fast? → Bolt or Lovable
- Need a deployed MVP? → Replit Agent
- Need editor performance? → Zed
- Need model freedom in your IDE? → Continue
- Need AI in JetBrains? → AI Assistant
- Need custom AI integrations? → Build with MCP
What tools from this ecosystem are you using? Discovered something great that isn’t listed here? Share it. ![]()