Skip to main content
MCP servers connect Embedder to tools from other applications or local programs. Run /mcp to browse available connections, add a server, and review its tools.

​
Add a server in chat

  1. Run /mcp and choose a catalog entry or custom server.
  2. Supply the command or URL requested by the server.
  3. Complete its sign-in or credential setup.
  4. Confirm the connection and enable the tools you need.
  5. Ask Embedder to perform a small, read-only check before using write actions.
Review the server and requested access before connecting it.

​
Add a local program

Run from the project directory:
The executable and its dependencies must be available on the machine running Embedder. Use an absolute command path if it is not on PATH.

​
Add a remote server

Replace the URL with your server’s address. Use --transport sse only when the server requires SSE. For a credential supplied through an environment variable:
Set the variable in the environment that starts Embedder. For browser sign-in, connect interactively from /mcp and follow the prompts.

​
Choose a configuration scope

Global configuration is in ~/.embedder/mcp.json; project configuration is in .embedder/mcp.json. A project entry replaces a global entry with the same name. For example:
Use names from the server’s actual tool list. disabledTools hides selected tools. hardwareTools identifies actions that need exclusive access to a live device. You can manage both from /mcp.

​
Coordinate hardware actions

Mark every tool that flashes, resets, captures from, or otherwise controls a live target as a hardware tool. This lets Embedder coordinate it with other sessions. The setting does not verify the behavior of the external program. Use the intended device and review its actions before running a hardware workflow.

​
Disconnect or remove

Use /mcp to disconnect a server or disable individual tools. From the terminal:

​
Troubleshoot

  • Local program cannot start: check the executable path and required dependencies.
  • Remote sign-in does not finish: reconnect from /mcp and complete the browser prompt.
  • A supplied credential is rejected: update the header or environment variable and reconnect.
  • A tool is missing: check the connection and disabled-tool list.
  • A company certificate is rejected: use your organization’s trusted certificate setup; support can help configure NODE_EXTRA_CA_CERTS if required.
See CLI reference for all configuration options.
Last modified on September 12, 2026