Daemon Status
Models Enabled
Providers
Tools
No providers configured. Click "Add Provider" to get started.
No models enabled. Add a provider and select models.
| Composite ID | Provider | Engine | Params | Capabilities | |
|---|---|---|---|---|---|
| Tools Vision |
Enable some models first, then start chatting!
Select a model and start chatting!
MCP servers provide tools to the LLM. They are unrelated to Providers/Models (which are LLM inference backends) —
MCP servers register tools the LLM can call, independent of which model answers.
Tools invoked via Abbenay's /mcp endpoint use the same approval policy as chat.
Dynamic stdio registration requires an allowlisted binary and your approval before any process is spawned.
Pending stdio MCP process spawns
A caller wants Abbenay to start an MCP server process. Approve only if you trust this command.
Recent stdio spawn denials
Pending MCP client connections
An external MCP client is trying to connect to Abbenay. Approve only if you trust this client.
Active MCP client sessions
Remembered MCP clients
These client names skip connection consent for this daemon lifetime. Forget to require approval again.
Pending MCP tool approvals
An MCP client called a tool that requires your consent. Approve or deny to unblock the request.
No MCP servers configured.
Click "Add MCP Server" above, or add an entry directly under mcp_servers: in ~/.config/abbenay/config.yaml.
| Name | Transport | Status | Tools | Enabled | Actions |
|---|---|---|---|---|---|
Policies are named behavioral bundles (sampling, output, reliability) assigned to models. Built-in policies are read-only. Duplicate one to create a custom variant.
No policies loaded.
Tools are functions the LLM can call during a chat — e.g. reading a file, running a search, or querying an API. They are registered by MCP servers (see the MCP Servers tab) or by editors like VS Code that connect to Abbenay. Each tool's approval policy below controls whether it runs automatically, asks you first, or is disabled.
tools registered (filtered by )
No tools registered yet
Tools show up here once something registers them with Abbenay. You have two options:
- Add an MCP server in the MCP Servers tab (each server exposes its own tools), or
- Connect an editor like VS Code to Abbenay, which registers its built-in tools automatically.
| Name | Source | Description | Policy |
|---|---|---|---|