ncode

Desktop docs MCP servers

ncode Desktop Customize

MCP servers

MCP servers give agents new tools: a database browser, an issue tracker, a design tool, a company API. ncode connects to them and offers their tools to every agent in scope, next to the built-in ones.

MCP servers#

MCP (Model Context Protocol) servers add their tools to the agents. ncode supports two transports:

TransportWhat you give it
stdio (a local process)a command, its arguments, and environment variables (KEY=VALUE)
http (streamable HTTP)a URL and request headers (Name: value)

A server is either global (every project) or scoped to one project. It can be switched off without deleting it, and each of its tools has its own switch: a tool you turn off is not offered to any agent. The environment variables and headers you enter are stored like your other keys.

A tool the server marks as read-only is treated like a read and never asks. Every other MCP tool is treated like a shell command: blocked in Read-only, asked about in Auto, allowed in Full access.

Adding a server#

  1. Open Settings → MCP servers and click Add MCP server.
  2. Fill in:
    • Name, for example filesystem.
    • Transport: stdio (local process) or http (streamable).
    • For stdio: Command (for example npx), Arguments (one line, shell-quoted) and Environment (KEY=VALUE per line).
    • For http: URL and Headers (Name: value per line), for example Authorization: Bearer ….
    • Scope: Global, or one of your projects.
  3. Save. ncode starts or connects to the server and lists its tools.

Example: a stdio server that exposes one folder.

FieldValue
Namefilesystem
Transportstdio (local process)
Commandnpx
Arguments-y @modelcontextprotocol/server-filesystem /path/to/notes

Managing servers#

Each server's card shows its status (ready, connecting, stopped, or the error it reported) and has:

  • a switch to turn the whole server on or off;
  • Reconnect, after you fix a problem or change the server;
  • Edit and delete (its tools disappear from every agent in scope);
  • the tool list: open it and click a tool to switch it off or on. A tool that is off is never offered to an agent;
  • Recent output: what the server itself reported (for a local server, also what it printed as errors), to see why it does not start.

Keys and safety#

  • The environment variables and headers you enter often contain tokens. They are stored in the local database with your other keys; see Data and privacy.
  • A stdio server is a program running on your Mac with your permissions. Add only servers you trust.
  • Tools a server does not mark as read-only need approval like shell commands, unless the project is in Full access.