Connect AgentsCopy Anchor Link

Choose the integration mechanism, then the host or framework:

• Plugins package host configuration, tools, hooks, or Skills. Dedicated plugins can join the host lifecycle; the portable Agent Plugin provides MCP configuration and a Skill.
• MCP exposes Agent tools at the Server's /mcp endpoint. MCP alone does not provide automatic prompt capture, recall hooks, or Skill installation.
• Skills provide discoverable workflow instructions. Installing a Skill does not start the Server or grant host tool permissions. Use the portable Agent Plugin in a compatible host, or export a managed Skill.

Agent HostsCopy Anchor Link

The 9 Agent Hosts use official for PowerContext project maintenance and community for community contributions. official does not imply endorsement by a host vendor.

Each integration connects to a separately running Server. Follow its guide in the table for installation, connection settings, authentication, and diagnostics.

For remote endpoints, see Connect to a remote Server: PowerContext clients allow loopback HTTP by default and require explicit consent for non-loopback HTTP. Host-native MCP policies remain separate.

To select multiple hosts interactively, run:

powercontext setup

Use the same ref as the Server. powercontext setup codex dsh installs, configures, and diagnoses both agents. Use powercontext config agent codex dsh to update installed connections without reinstalling or enabling them; consult each Agent guide for native requirements.

Experimental MCP connectionsCopy Anchor Link

Cindy offers scoped Ghost recall tools and optional automatic recall and original-prompt capture, with a separate native MCP connection for the full Server tool catalog. Users do not need DSH. It remains under evaluation and is not counted in the qualified Agent Host list.

Automatic prompt privacyCopy Anchor Link

The following prompt adapters enable capture by default. Existing capture preferences remain effective when updating a plugin; this policy adds credential checks without changing capture defaults.

Before automatic capture, these adapters recognize conventional credential assignments (API/access keys and tokens, client/private keys, secrets, passwords, passphrases, authorization and cookies), Bearer values of at least eight token characters, common provider/GitHub/Slack token shapes, private-key blocks including unfinished blocks, and exact occurrences of the configured Server credential. Recognition is best effort: unknown formats, obfuscation and credentials without recognizable markers can pass. Conservative matching also skips examples such as password=example. Ordinary words such as “token budgets” are not assignments. The shared synthetic corpus is tests/fixtures/automatic_prompt_privacy.json; it defines tested examples, not proof that arbitrary credentials are detected.

Authorization, Proxy-Authorization, Cookie and Set-Cookie assignments consume the complete header value, including schemes, cookie attributes and folded continuation lines, before ordinary assignments are matched. This conservatively removes any other prose on the same header line from the automatic query.

A recognized input is skipped as a whole for capture. The adapter never redacts a Source body and then attaches the original event's identity or receipt to it. Accepted events keep their existing host text normalization and identity semantics; distinct events and retries follow the host's documented contract. Local diagnostics or configured observations report a bounded skip reason (sensitive_content, or Kimi's sensitive) without the rejected text. Pi reports this through its configured diagnostic sink; off disables that output.

Automatic read-only preparation remains independent: recognized fragments are replaced with [REDACTED] before building the bounded query, even when capture is disabled. Preparation may therefore lose some query specificity; a valid historical response can still be delivered. This changes only the automatic query, not stored Source evidence or an explicit tool call. Authentication headers still carry the configured credential to the selected Server as required by that connection.

If prompts must not leave the host, disable automatic capture and the host's automatic preparation hook/extension. Disabling capture alone still allows read-only requests, and detection is not a confidentiality guarantee. Keep secrets out of prompts, configure trusted endpoints and review operational access. This policy does not scan stored Sources, rewrite immutable revisions, prevent prompt injection, or classify all explicit Source writes at the Server.

Python Agent frameworksCopy Anchor Link

All 3 adapters are community. Install them in the application environment; do not use powercontext setup <host>:

Evaluation integrationsCopy Anchor Link

Bub is for evaluation only. It is not part of the Agent Host or Python Agent framework support lists.

Capabilities and availabilityCopy Anchor Link

The capability matrix is generated from integrations/capabilities.toml. The 9 Agent Hosts and Bub are master_only; Pydantic AI is experimental. released means available from a specified release tag, master_only means implemented but unreleased, and experimental carries no stability guarantee. These labels are separate from stewardship and the Minimal / Recommended / Full capability profiles.

Use the same release tag or commit for the Server and integration. Check installation requirements: Windows support is experimental, and does not imply that every host or optional backend supports Windows.