MCP Servers
Model Context Protocol (MCP) is Anthropic's open standard for letting AI models call external tools via a uniform interface. Jorv Builder ships with a built-in MCP client — register an MCP server and Orbit gains its tools as if they were native.
What Jorv Builder does with MCP
- Connects to MCP servers via stdio transport (subprocess) or HTTP
- Discovers available tools at connection time
- Exposes those tools to Orbit alongside the built-in toolset
- Surfaces failures inline in the cockpit (red icon on the MCP HUD slot)
Setup
- Pick an MCP server. Examples:
@modelcontextprotocol/server-filesystem— file ops@modelcontextprotocol/server-github— GitHub API@modelcontextprotocol/server-postgres— Postgres queries
- Settings → MCP Servers → Add server.
- Enter the command (e.g.
npx -y @modelcontextprotocol/server-postgres postgresql://localhost/mydb). - Save. Jorv Builder connects, discovers tools, and they're immediately available to Orbit.
Security notes
MCP servers run as subprocesses with the same permissions as Jorv Builder. Only register servers you trust. Be especially careful with servers that accept connection strings or credentials in their command line.