Skip to content

Integrations

hummin meets the rest of your toolchain without plugins-by-GUI: MCP, LSP, web, and a full automation surface.

MCP client

Model Context Protocol servers configured under mcpServers (stdio JSON-RPC). Their tools appear as model-callable mcp_<server>_<tool> entries.

/mcp       # server status + restart

TypeScript LSP

When typescript-language-server is available, the model gets real language tools instead of grep-shaped guessing:

Tool Purpose
lsp_diagnostics Type errors, live
lsp_definition Jump to definition
lsp_references Find all references
lsp_hover Type info 
/lsp       # server status + restart

Web

  • web_search - DuckDuckGo search
  • web_fetch - fetch with an SSRF guard (internal addresses and metadata endpoints are refused)

Extensions

TypeScript extensions in ~/.hummin/agent/extensions/ autoload at startup with hot reload and a transform cache. This is the mechanism behind the local fleet provider - see Connecting to hummin - and it is the same API available to yours.

Prompt templates, skills, packages

  • Skills follow the Agent Skills standard: /skill:<name>.
  • Prompt templates become first-class slash commands.
  • Packages install from npm or git: hummin package install|remove|update|list.

Automation surface

  • SDK for embedding, RPC mode and JSON event mode for scripts.
  • hooks.json for shell-level lifecycle automation (see Safety).
  • Cron for scheduled wake-ups (see Agent Teamwork).
  • /remote-control - loopback browser view of the session with prompt/abort, for when you want to drive from a phone-shaped window on the same machine.