Add official MCP server
This commit is contained in:
@@ -118,6 +118,27 @@ See [`docs/desktop-automation.md`](./docs/desktop-automation.md).
|
||||
On desktop, KeePassGO now listens on a Unix socket by default under the user runtime directory.
|
||||
Set `KEEPASSGO_GRPC_ADDR` or `-grpc-addr` to override it, for example `tcp://127.0.0.1:47777`.
|
||||
|
||||
## MCP Server
|
||||
|
||||
KeePassGO includes a stdio Model Context Protocol server for agent and assistant integrations.
|
||||
It connects to the same local authenticated gRPC API used by browser and desktop automation, so
|
||||
existing token policy and approval prompts remain in force.
|
||||
|
||||
Build it with:
|
||||
|
||||
```bash
|
||||
make mcp-server
|
||||
```
|
||||
|
||||
Configure your MCP client to run `keepassgo-mcp-server` and provide an API token through
|
||||
`KEEPASSGO_MCP_TOKEN`. The server also accepts `KEEPASSGO_BEARER_TOKEN` for compatibility with
|
||||
existing local gRPC tooling. Set `KEEPASSGO_GRPC_ADDR` or pass `-grpc-addr` when KeePassGO is not
|
||||
listening on the default local socket.
|
||||
|
||||
The MCP server exposes tools for session status, metadata-only entry search, browser-login matching,
|
||||
and explicit credential retrieval. Metadata tools do not return passwords, notes, or custom field
|
||||
values; credential retrieval uses KeePassGO's credential access policy.
|
||||
|
||||
## Browser Extension
|
||||
|
||||
Firefox and Chromium browser integration is available through the local gRPC API plus a native messaging bridge.
|
||||
|
||||
Reference in New Issue
Block a user