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.

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:
ItemMeaning
ToolsActions an agent can call
ResourcesReadable external data
Resource templatesParameterized resources
PromptsReusable prompt templates

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

Disable MCP servers or tools until you understand what they expose. After they are trusted, decide whether they should be implicit. An implicit MCP tool can be picked up automatically when Pioneer decides it is relevant. A not implicit MCP tool stays available, but agents should use it only when you explicitly ask for that MCP capability. Use implicit mode for trusted read-heavy tools that are useful across many threads. Keep write-capable, sensitive, expensive, noisy, or production-facing MCP tools 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 requested?

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

Add or refresh the required secret or token, then restart the server.
Some catalog items may have failed. Review diagnostics and restart after fixing dependencies.
Confirm the MCP server is installed for the same gateway and that policy allows it in the current workspace.
Check server logs, gateway connectivity, credentials, input schema, and external service status.