A framework-neutral foundation for building generic DevTools, part of the Vite DevTools monorepo (MIT). Current stable version is 0.1.21, with weekly releases featuring breaking changes and new capabilities. Provides an RPC layer based on birpc + valibot + WebSocket presets, plus six built-in hosts: RPC, docks, views, terminals, logs, commands, and an agent interface for MCP integration. Includes adapters for CLI, build, SPA, Vite, Kit, embedded, and MCP. Key differentiators: designed specifically for developer tooling, first-class MCP support for AI agents, and a modular architecture that decouples UI from logic since v0.1.21. Ships TypeScript types. Requires @modelcontextprotocol/sdk as a peer dependency for MCP features.
npm install devframeNo compatibility data collected yet for this library.
Verified import paths — ran on the pinned version, not inferred.
Defines a minimal devtool with an RPC function and MCP resource, then starts an HTTP server. Demonstrates core setup, RPC registration, and agent integration.
Update any hardcoded mount paths in your integrations from '/.' to '/__'.
Import host modules from dedicated packages (e.g., @devframe/docks) instead of relying on devframe exports.
If you use devframe with a custom HTTPS setup, ensure your config is correctly applied to the embedded client.
Replace all references to ctx.logs with ctx.messages.
Pin your devframe version and avoid relying on undocumented agent features in production.
Use import syntax or dynamic import with await when consuming in CommonJS environments.
Use import syntax if your project is ESM, or use dynamic import: const { defineDevtool } = await import('devframe').Ensure you have installed @modelcontextprotocol/sdk and import from 'devframe/adapters/mcp' (not 'devframe').
Check that you have configured the devtool with agent-native support enabled. Ensure you are using a version >=0.1.16.
Replace ctx.logs with ctx.messages in your code.
Update your URL to use '/__' prefix, e.g., http://localhost:3000/__/devtools/.