Connected services

Many apps and services offer an MCP server: a set of tools an assistant can use, like searching a calendar, creating an issue or turning on the lights. Connect one and nolune’s agent can use its tools in chats, automations and subagents, on every model.

Connecting a server

Admins connect servers on the Connected services page, in the menu under their name: Connect a server, give it a name, and what its instructions say:

• A command that starts it on this computer, like npx -y @modelcontextprotocol/server-filesystem ~/Documents or uvx mcp-server-time, with the environment variables it needs (NAME=value, a line each).
• An address, often ending in /mcp, with the headers it needs, like Authorization: Bearer …. Choose SSE for older servers.

nolune connects to it right away and says how many tools it has, or why it couldn’t connect. It keeps a server it couldn’t reach, so you can install what it needs and press Check.

The same from a terminal:

nolune mcp add time -- uvx mcp-server-time
nolune mcp add github https://api.githubcopilot.com/mcp/ --header 'Authorization: Bearer ghp_…'
nolune mcp add-json files '{"command": "npx", "args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/anna/Documents"]}'
nolune mcp list
nolune mcp rm github

add-json takes a server as MCP clients’ settings write it, so the snippet from a server’s README can be pasted, "mcpServers" and all.

Signing in

Many services at an address ask you to sign in instead of giving a key, like Notion’s, Linear’s or Sentry’s. Connect it with just its address: nolune says it needs someone to sign in, and its row gets Sign in. That opens the service’s sign-in page, and once you’ve signed in and allowed nolune, it comes back to Connected services with the server’s tools. Sign out forgets the sign-in.

• The account you sign in with is the server’s, for every profile that has it. To connect someone’s own account, sign in with theirs and keep the server to their profile.
• nolune registers itself with the service, so there’s nothing to set up. A few services want you to register an app with them first: give its client ID and secret under Sign-in app.
• The sign-in comes back to the address you have nolune open at. Services accept http://localhost and https addresses; at another http:// address, sign in from the computer nolune runs on, or turn on remote access.
• nolune keeps the sign-in fresh by itself. When the service ends it (a password changed, access taken back), the agent hears that someone has to sign in again, and so does the page.

From a terminal, nolune mcp login <name> prints the page to open, which comes back to nolune’s web address, and nolune mcp logout <name> signs out:

nolune mcp add notion https://mcp.notion.com/mcp
nolune mcp login notion

Who gets it

Every profile gets a server unless you choose some under Profiles (--profile <slug> in the CLI). A server that reaches someone’s own account, like their email, belongs in their profile.

What it’s for is a few words that tell the agent when to use it. Left empty, nolune uses what the server says about itself.

How the agent uses it

Each chat gets the tools of its profile’s servers next to nolune’s own, named mcp__<server>__<tool>, and its instructions say what each server is for. The agent calls them like any tool, on every model, the plans included, and pictures a tool returns are shown to it.

A chat keeps the tools it has, so its prompt cache stays warm: a server you connect, change or disconnect reaches new chats. A chat already going shows a line above its composer saying what changed, with Reload tools (also in the chat’s menu): press it, and the chat gets the servers’ tools and the profile’s skills as they are now. Its next reply reads the whole chat again, so it costs more than usual on a long chat. The agent can also reach a server’s tools from a command, in scripts and automations:

nolune mcp tools github
nolune mcp call github search_issues '{"query": "repo:anna/garden is:open"}'

Every server’s tool definitions go with every request of the chats that have them, so a server with many tools makes each reply cost more. Connect the ones the family uses, and keep personal ones to their own profile. A chat gets at most 120 tools from servers.

Auto mode checks every call to a server’s tool: looking things up goes ahead, while creating, changing, deleting or sending something in someone’s account needs someone in the chat to have asked for it. In the chat, a call shows as what it does, like “Search issues (github)”.

Good to know

• A server that runs on this computer runs as your account, like the agent’s commands, and finds programs (npx, uvx, docker) where they do. Connect only servers you trust.
• nolune keeps each server running while it’s used, and stops it after 10 minutes without a call or when the gateway stops.
• Servers, with their keys, are kept in ~/.nolune/config.json, and their sign-ins in ~/.nolune/mcp-auth.json, both readable by your account only. The page and nolune mcp list show the keys’ names, never the keys, and never the sign-ins’ tokens.