Skip to main content
Use the desktop MCP setup assistant when adding a server.
1
Open MCP settings
2
Go to Settings → MCP.
3
Run the setup assistant
4
Click Run setup assistant.
5
Choose the transport:
6
  • stdio — ntrp launches a local command, such as npx or a local binary
  • HTTP — ntrp connects to a remote or local HTTP/SSE MCP endpoint
    • 7
    Fill the fields or import JSON
    8
    The assistant can parse common MCP JSON shapes, including:
    9
    {
  "mcpServers": {
    "example": {
      "transport": "stdio",
      "command": "npx",
      "args": ["-y", "@example/mcp-server"],
      "env": { "EXAMPLE_API_KEY": "..." }
    }
  }
}
    10
    It also accepts direct server objects with name and transport.
    11
    Save and reload
    12
    After saving, ntrp reloads MCP providers and shows their tools in the provider list.

    ​
    Transport fields

    TransportRequired fieldsOptional fields
    stdiocommandargs, env, cwd
    httpurlheaders, auth-related fields supported by the server

    ​
    Deferred tools

    MCP tools are deferred by server group. For example, a server named obsidian is loaded by the agent with: 
    load_tools(group="mcp:obsidian")

    ​
    Troubleshooting

    • Command not found — use an absolute command path or install the package/binary first.
    • Missing env var — add required KEY=value entries in the server config.
    • HTTP auth failure — check headers/tokens and whether the server expects OAuth.
    • No tools appear — verify the server starts successfully and then reload MCP/settings.