More
Connectors (MCP): other services' tools in the chat
A connector lets the chat model use another service's tools: look up issues, read a calendar, search a company's files. A connector is an MCP server (Model Context Protocol, the open standard many AI apps use). Connectors are in the desktop app; the web version doesn't have them yet.
Two kinds
- A service on the internet: an https address, often with a key.
- A program on this PC: GlirOS starts it as you, without admin rights, and stops it when GlirOS stops.
Adding one
Settings > Connectors > add: give it a name, the address (or the program and its arguments) and the key if it needs one. Each connector gets a card with its status, its tools (each can be switched off), Connect again, Change the key and Delete.
Where they work
Projects are the hub: a connector lists the projects whose chats use it. One marked Personal is used in ordinary chats. A project chat uses only its project's connectors. Each message offers only the tools that fit it, fewer for a small model (6 at once) than for a mid-size one (12) or a cloud or big model (30); when you switch to a smaller model, a note says how many tools are paused.
Asked first
- A call that only reads runs without asking.
- Any other call shows what it does, the service and where it goes, with Allow once or Always allow. (In Settings > Connectors the same choice is each tool's Allow without asking switch.)
- A call that deletes or can't be undone is asked every time, with no Always.
- Once a message has read text from outside (a web page, a file, a connector's answer), every call that changes something is asked again, so text from outside can't steer it.
- A plan whose steps will change something stops before its first step with one card that lists them.
- Every call leaves a line in the chat's activity log: "Sent to …".
Where they don't work
Offline and incognito chats use no connectors, and while Settings > Security blocks all traffic a service can't be reached. Connectors can't be added or changed through remote access.
Keys
A key is typed once in Settings and kept in Windows Credential Manager. It is never shown again and never given to the model.
Signing in
Some services want you to sign in on their own page instead of a key. The card then says "Sign in to <service> to use it." Sign in… says what happens, then opens the service's page in your browser; when you've signed in there, the card shows the tools. GlirOS never sees your password: the access the service gives is kept in Windows Credential Manager, renewed by itself, and never given to the model. If the service wants more access for a tool, or the access ran out, the card asks you to sign in again. Sign out (or Delete) gives the access back to the service and forgets it. A few services want a client ID you register with them yourself: Enter client ID… keeps it, and the card shows the address to register as the callback. Signing in works only on this PC, not through remote access.
Not yet
Connectors in the web version, and MCP's resources and prompts.
This guide is the same text GlirOS itself uses to answer questions about GlirOS.