Agent-readable docs index: /llms.txt. Full docs in one file: /llms-full.txt. Download /docs.zip to grep all markdown files locally.

Security and confirmations

StackYapper applies workspace boundaries, encrypted credential storage, authorization policy, operation risk metadata, and audit logging around every connector.

Risk-aware execution

Read operations can execute through the read-only tool path. Operations that create, change, or delete provider data require the broader execution path and can require operation-bound confirmation.
The confirmation applies to the exact proposed operation. It is not a standing approval for unrelated future changes.

Audit history

StackYapper records the calling client, workspace, user or credential identity, selected tool, and execution result so administrators can review activity.

Credential handling

  • Provider secrets are encrypted at rest.
  • Interactive clients should use OAuth.
  • API keys are shown once and should be stored in a secret manager.
  • Removing a client or credential revokes its future access.
Open the portal
Review apps, users, MCP clients, and audit activity for your workspace.
Powered byHolocron