MCP Catalog

The MCP catalog shows what a connected MCP server exposes to Pioneer. Use the catalog before allowing agents to use a server.

​

Catalog items

An MCP server can expose:

​

What to inspect

For each server, review:

• display name
• transport type
• runtime status
• health diagnostics
• enabled/disabled state
• implicit/not implicit state
• tool count
• resource count
• prompts
• policy state
• recent audit activity

​

Enable, Disable, Or Change Implicit Mode

Keep MCP servers explicit-only until you understand what they expose. After they are trusted, decide whether they should be implicit. An implicit MCP server can have its tools picked up automatically when Pioneer decides they are relevant. A not implicit MCP server stays available, but agents should use its tools only when you select that server or one of its tools from the composer, or when you explicitly ask for that MCP capability. Use implicit mode for trusted read-heavy servers that are useful across many threads. Keep write-capable, sensitive, expensive, noisy, or production-facing MCP servers not implicit.

​

Tool review checklist

Before enabling an MCP server in real workflows, ask:

• What can each tool read?
• What can each tool write?
• Does it call external services?
• Does it need secrets?
• Does it modify production systems?
• Does it have rate limits?
• Does it return sensitive data?
• Should it be implicit, or only used when explicitly selected?

​

Server lifecycle

From the desktop app you can manage server lifecycle actions such as:

• start
• stop
• restart
• update policy
• uninstall
• inspect details

Available actions may depend on transport and server state.

​

Troubleshooting