Extend your AI coding workflow with MCP, LSP and plugins

Choose the extension that fits the task

1. MCP connects external tool services and adds their discovered tools to a task.
2. LSP connects an installed language server for project code understanding.
3. Skills provide reusable project conventions and task instructions loaded when needed.
4. Hooks participate at defined points in the workflow.
5. Rhai / WASM provide scripted tool composition and signed extension components.

Connect an MCP stdio service

Install the MCP service on the execution computer and confirm its command, arguments and credentials. Configure it through the session plugin settings. This example shows the structure; replace your-mcp-server with the actual installed command.

MCP connects and discovers tools when a task starts. Opening a status page does not start it. Verify with a concrete read task, then inspect the tool activity and background service status.

{
  "id": "project-mcp",
  "kind": "ternilo.mcp.stdio",
  "enabled": true,
  "config": {
    "server_name": "project",
    "command": "your-mcp-server",
    "args": []
  }
}

Session settings, presets and packages have different scopes

1. A session override changes the current session’s plugin settings, not every other session.
2. An Agent preset supplies the baseline for new sessions using it. Applying it to an existing idle session is an explicit action.
3. The extension inventory controls packages installed and allowed on the current target. Installing a package does not automatically mount it in the current session.

Verify tools before adding reusable methods

Start with one MCP tool and an explicit task, check its actual output, then add LSP, Skills or Hooks as needed. An enabled switch does not install missing language servers, commands or credentials.

Plugins remain subject to host permissions, sandbox policy and approvals. Skills are instructions, not extra file or network permissions. Signed components can use only their granted capabilities.