Haruno Knowledge base

Custom MCP servers

Add a server of your own by its web address to give Haruno extra tools. It is in the advanced view only, and scheduled tasks never use these servers.

  • Mac appAvailableAdvanced view only. Scheduled tasks never use these servers.
  • Windows appAvailableAdvanced view only. Works in the sandbox. Not used by scheduled tasks or hooks.

A custom MCP server is a service you or your company runs that offers Haruno extra tools. You add it by its web address. Haruno then lists the tools the server offers, and you choose which ones Haruno may use.

Where it is

The Custom MCP servers section is at the bottom of the Connectors window. It shows in the advanced view only. To see it, turn on Advanced view in Settings ▸ General. See Normal view and advanced view.

The section says: Connect the agent to your own MCP servers, by URL.

Add a server

  1. Click Add server

    A window opens with a Connection section.

  2. Fill in the connection

    Give the server a Name and its Server URL. A name is 1 to 64 letters, numbers, hyphens or single underscores. The window tells you if a name is reserved or already used. Under Authentication, choose None, Header or OAuth.

  3. Add the sign in details

    Header asks for a Header name and a Secret. OAuth asks for optional details: Client ID (optional), Client secret (optional), Callback port (optional) and Scopes (space-separated, optional).

  4. Click Connect

    Haruno contacts the server. With OAuth, the window says Complete sign-in in your browser…. When it works, a Tools list appears. If the server offers none, the window says so.

  5. Choose a setting for each tool

    Each tool has On, Confirm or Off. On lets Haruno use it. Confirm makes Haruno ask first. Off keeps Haruno from using it.

  6. Click Save

    The server joins the list.

If Connect fails, the window says why. For example, the server could not be reached, its certificate could not be verified, or the sign in was declined or timed out.

A server on your own Mac cannot be reached

Haruno works in an isolated space. A server at localhost is on your Mac, outside that space, so Haruno cannot reach it. The window warns you. Use a host name or a network address instead. Any port works. Haruno lets its isolated space reach the address you give.

Use and change a server

Each server has a row with its name and either the number of tools on, such as 3/5 tools, or its web address. A switch turns it on or off. The ⋯ menu has Edit… and Remove.

  • Edit… opens the same window. Reconnect refreshes the tool list from the live server.
  • Remove asks first. Haruno then stops using the server.

A row can show a warning when the saved secret is a problem: Credential missing — edit the server to re-enter it., Unlock your keychain to use this server. or Credential rejected — edit the server to enter a new one.

Scheduled tasks never use them

A scheduled task is never given a custom server. This holds for a task you allowed to send on its own, and for Try it…. Haruno cannot tell which tools of someone else's server reach other people, so it cannot hold them for your approval the way it holds an email. Use these servers in a chat, where you see each step.

A chat that belongs to a project does not use them either. See The Connectors window.

Who has it

The advanced view only. The normal view hides the section.

What to tell a customer

This is for people who run their own tools, usually with help from their IT team. They need the server's web address and, if it asks for one, a header secret or an OAuth sign in. Most customers never need it.

Last updated · PR #2944 · View this version on GitHub

History (1 version)
  1. Internal knowledge base for staff: site, reader keys, assistant, 197 pages and the PR rule (#2944)
    What changed
    @@ -0,0 +1,71 @@
    +---
    +title: Custom MCP servers
    +summary: Add a server of your own by its web address to give Haruno extra tools. It is in the advanced view only, and scheduled tasks never use these servers.
    +feature: custom-mcp-servers
    +covers:
    +  - apple/Sources/ConnectorsFeature/AddMCPServerSheet.swift
    +  - apple/Sources/ConnectorsFeature/AddMCPServerValidation.swift
    +  - apple/Sources/ConnectorsFeature/CustomMCPService.swift
    +  - apple/Sources/EngineSupport/CustomMCPMaterializer.swift
    +  - apple/Sources/EngineSupport/CustomMCPServer.swift
    +---
    +
    +A custom MCP server is a service you or your company runs that offers Haruno extra tools. You add it by its web address. Haruno then lists the tools the server offers, and you choose which ones Haruno may use.
    +
    +## Where it is
    +
    +The <Ui>Custom MCP servers</Ui> section is at the bottom of the [Connectors window](/macos/connectors/connectors-window/). It shows in the advanced view only. To see it, turn on <Ui>Advanced view</Ui> in <Ui>Settings ▸ General</Ui>. See [Normal view and advanced view](/macos/app/normal-and-advanced-view/).
    +
    +The section says: <Ui>Connect the agent to your own MCP servers, by URL.</Ui>
    +
    +## Add a server
    +
    +<Steps>
    +<Step title="Click Add server">
    +A window opens with a <Ui>Connection</Ui> section.
    +</Step>
    +<Step title="Fill in the connection">
    +Give the server a <Ui>Name</Ui> and its <Ui>Server URL</Ui>. A name is 1 to 64 letters, numbers, hyphens or single underscores. The window tells you if a name is reserved or already used. Under <Ui>Authentication</Ui>, choose <Ui>None</Ui>, <Ui>Header</Ui> or <Ui>OAuth</Ui>.
    +</Step>
    +<Step title="Add the sign in details">
    +<Ui>Header</Ui> asks for a <Ui>Header name</Ui> and a <Ui>Secret</Ui>. <Ui>OAuth</Ui> asks for optional details: <Ui>Client ID (optional)</Ui>, <Ui>Client secret (optional)</Ui>, <Ui>Callback port (optional)</Ui> and <Ui>Scopes (space-separated, optional)</Ui>.
    +</Step>
    +<Step title="Click Connect">
    +Haruno contacts the server. With OAuth, the window says <Ui>Complete sign-in in your browser…</Ui>. When it works, a <Ui>Tools</Ui> list appears. If the server offers none, the window says so.
    +</Step>
    +<Step title="Choose a setting for each tool">
    +Each tool has <Ui>On</Ui>, <Ui>Confirm</Ui> or <Ui>Off</Ui>. <Ui>On</Ui> lets Haruno use it. <Ui>Confirm</Ui> makes Haruno ask first. <Ui>Off</Ui> keeps Haruno from using it.
    +</Step>
    +<Step title="Click Save">
    +The server joins the list.
    +</Step>
    +</Steps>
    +
    +If Connect fails, the window says why. For example, the server could not be reached, its certificate could not be verified, or the sign in was declined or timed out.
    +
    +<Callout variant="info" title="A server on your own Mac cannot be reached">
    +Haruno works in an isolated space. A server at localhost is on your Mac, outside that space, so Haruno cannot reach it. The window warns you. Use a host name or a network address instead. Any port works. Haruno lets its isolated space reach the address you give.
    +</Callout>
    +
    +## Use and change a server
    +
    +Each server has a row with its name and either the number of tools on, such as 3/5 tools, or its web address. A switch turns it on or off. The ⋯ menu has <Ui>Edit…</Ui> and <Ui>Remove</Ui>.
    +
    +- <Ui>Edit…</Ui> opens the same window. <Ui>Reconnect</Ui> refreshes the tool list from the live server.
    +- <Ui>Remove</Ui> asks first. Haruno then stops using the server.
    +
    +A row can show a warning when the saved secret is a problem: <Ui>Credential missing — edit the server to re-enter it.</Ui>, <Ui>Unlock your keychain to use this server.</Ui> or <Ui>Credential rejected — edit the server to enter a new one.</Ui>
    +
    +## Scheduled tasks never use them
    +
    +A scheduled task is never given a custom server. This holds for a task you allowed to send on its own, and for <Ui>Try it…</Ui>. Haruno cannot tell which tools of someone else's server reach other people, so it cannot hold them for your approval the way it holds an email. Use these servers in a chat, where you see each step.
    +
    +A chat that belongs to a project does not use them either. See [The Connectors window](/macos/connectors/connectors-window/).
    +
    +## Who has it
    +
    +The advanced view only. The normal view hides the section.
    +
    +## What to tell a customer
    +
    +This is for people who run their own tools, usually with help from their IT team. They need the server's web address and, if it asks for one, a header secret or an OAuth sign in. Most customers never need it.