Features · MCP tools
Your tools, inside the conversation.
Devora speaks MCP. Add local stdio servers or remote HTTPS servers and their tools appear in the agent, namespaced per server — with their own permission settings and the same approval flow as built-in actions.
Interface illustration — sample MCP servers.
What it does
01
Local and remote
Stdio servers run on your machine; remote servers connect over HTTPS.
02
Namespaced tools
Each server's tools are grouped under its name, so two servers can expose a search tool without colliding.
03
The same rules
Per-server permissions and per-action approvals apply exactly like built-in tools.
Details
What you can rely on.
The small print, written plainly — including the parts that depend on your account.
- Configure MCP servers in Settings → Tools.
- Permissions are per server; approvals still happen per action.
- Remote servers must use HTTPS.
Availability
MCP support ships with the desktop app. Servers you add yourself are your responsibility.
Keep exploring.
Try Devora.
Install the desktop app, open your project, and start with a question about your own codebase.
Windows 10 & 11 · Local workspace · Reviewable edits