Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getpioneer.dev/llms.txt

Use this file to discover all available pages before exploring further.

Add MCP servers from the desktop app while connected to the gateway that should own the integration. Pioneer connects to servers that implement Model Context Protocol. Those servers can expose tools, resources, prompts, and workflows to the gateway. Before you add one, decide where it belongs. A work MCP server should usually live on the work gateway. A personal helper should live on the home or local gateway. An unfamiliar server should be tested in a sandbox first.

​
Install From The Desktop App

In the desktop app, connect to the gateway where the MCP server should run. Click the MCP icon in the bottom bar, click Install, paste the MCP JSON config into the config field, and submit it. Pioneer reads the JSON, validates each server under mcpServers, stores secret values in the gateway keystore, stores redacted server entries in gateway.db, and starts or connects to enabled servers.

​
Stdio Servers

Use stdio when Pioneer should launch the MCP server as a local child process. For stdio, the command in the JSON must already be available on the gateway host. For a remote gateway, install that command on the remote machine, not on your laptop. Paste a config with a top-level mcpServers object: 
{
  "mcpServers": {
    "resend": {
      "command": "npx",
      "args": ["-y", "resend-mcp"],
      "env": {
        "RESEND_API_KEY": "re_xxxxxxxxx"
      }
    }
  }
}
The server name, such as resend, must use letters, numbers, _, or -. Use command for the executable, args for command arguments, and env for environment variables passed to that server. You can also set cwd when the command must start from a specific directory.

​
HTTP Servers

Use HTTP when the MCP server is already running as a service. Start the service outside Pioneer, confirm the gateway can reach its URL, then install it from the MCP screen with a JSON config like this: 
{
  "mcpServers": {
    "resend": {
      "url": "https://example.com/mcp",
      "headers": {
        "Authorization": "Bearer re_xxxxxxxxx"
      }
    }
  }
}
Use url for the MCP HTTP endpoint and headers for authentication or routing headers. The URL must use http or https. If the gateway is remote, test connectivity from the remote host.

​
Common Config Fields

Every server config lives under mcpServers and uses the object key as the server name.
FieldUse
commandStdio server executable. Mutually exclusive with url.
argsOptional stdio command arguments.
cwdOptional working directory for a stdio server.
envOptional environment variables for a stdio server.
urlHTTP MCP endpoint. Mutually exclusive with command.
headersOptional HTTP headers for an HTTP server.
enabledEnables the server when true.
disabledDisables the server when true. Do not set both enabled and disabled.
allow_implicit_invocationAllows agents to consider the server automatically when true; keep it false for explicit-only use.
requiredMarks the server as required for the configured scope.
startup_timeout_secOptional startup timeout.
tool_timeout_secOptional timeout for MCP tool calls.

​
Secrets

Do not paste MCP secrets into chat prompts. Put API keys, tokens, and other credentials in the MCP JSON env or headers fields, or in the gateway environment when your server reads credentials from there. Pioneer stores secret values from env, headers, tokens, and authorization fields in keystore.db through the gateway secret store. Diagnostics, source references, and list/detail responses use redacted data and secret refs instead of raw values. When you update or uninstall an MCP server, Pioneer removes stale keystore refs after the database change succeeds. If you need to inspect or clean orphaned MCP secret refs explicitly, use pioneer secrets status and pioneer secrets garbage-collection.

​
Health And First Test

After saving a server, Pioneer should discover its tools, resources, templates, and prompts. If it fails, the most common causes are a missing command, invalid environment variable, auth failure, unreachable HTTP endpoint, or a server that starts but advertises no tools. Review the discovered tools before enabling them. Keep new MCP tools not implicit until you understand what they can read, write, or call. Use a read-only first prompt: 
List the MCP tools available in this workspace and explain what each one can do. Do not call them yet.
Then call one low-risk tool and inspect the timeline.