Back to Paperclip

Connections Glossary

doc/connections/GLOSSARY.md

2026.720.03.5 KB
Original Source

Connections Glossary

Audience: engineers, designers, and agents writing integration code, plans, or product copy on the Apps v2 substrate.

Source: the accepted vocabulary table from the PAP-13211 plan. Treat these definitions as product law when translating old Connections v1, plugin, skill, MCP, and gateway language onto Apps v2.

Canonical Vocabulary

TermDefinitionIt is NOT
AppCatalog entry for an external or first-party system: metadata, supported transports, auth modes, and action catalog. The unit of the store.A running thing; a plugin.
ConnectionA configured, credentialed instance of an app for this company, possibly per-user account. Carries status and health.A plugin install; an MCP server config file.
Action / ToolOne invokable capability of a connection, risk-classified and quarantined when new or changed.A free-form shell command or permission grant.
ProfileCurated allowlist of actions bound to a scope such as company, project, agent, routine, or issue.A permission system of its own.
RuleAllow, ask-first, or block per action. Ask-first lands in the Review queue.A profile or catalog entry.
GatewayNamed inbound MCP endpoint exposing curated connections/tools to external clients under a scoped bearer token. Reuses profiles and rules.A new permission model.
PluginCode extension package: workers, UI, migrations. May declare apps/providers and provision skills. Packaging, not governance.An integration per se.
SkillInstructions an agent follows. May use connections; must not own tokens.A token store.
MCPA wire protocol; one transport apps may support.A product category.
BrokerThe run-time service that turns a stored credential plus a grant into a short-lived, downscoped, attributed token.A vault or a permission model.

Product Copy Defaults

Use these words in prosumer surfaces:

  • app
  • connect
  • connection
  • allowed
  • ask-first
  • review

Keep protocol and implementation terms behind Developer or Advanced surfaces:

  • MCP
  • stdio
  • gateway
  • plugin
  • manifest
  • DCR
  • PKCE
  • schema hash
  • bearer token
  • secret ref

Apps v2 Object Mapping

Vocabulary termApps v2 object or surface
Apptool_applications, provider gallery cards, app detail metadata.
Connectiontool_connections, connection detail status/health, setup/configure flows.
Action / ToolCatalog entries discovered from MCP/OpenAPI/vendor wrappers.
ProfileAccess profiles and bindings.
RulePolicy rules such as allow, ask-first, block, rate limit, and trust rules.
GatewayInbound MCP gateway sessions and scoped client tokens.
PluginExtension packaging that may declare apps but does not bypass governance.
SkillAgent instruction package that calls governed connections through Paperclip.
MCPTransport option for apps and gateways.
BrokerCredential resolver/token broker path over company_secrets.

Translation Rules

  • MCP is a transport, not the information architecture.
  • A plugin may bundle an app, but governance always flows through the connection, profile, rule, broker, and audit model.
  • A skill may use Slack, Google Drive, Ramp, or another vendor, but the durable credential belongs in company_secrets and is reached through a connection.
  • Inbound clients use scoped Paperclip auth; outbound vendor calls use the Apps v2 connection governance stack.