Person
Henry Brink
Capabilities
Contributes to
Metadata publishingCAPMetadata publishingDescribing a service to something other than a human — service metadata for clients, and machine-readable descriptions for registries and discovery.Serve your application over MCPCAPServe your application over MCPExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through [service integration](capability:service-integration), connecting its exposed contract with [agent access to your systems](capability:agent-systems-access). Development assistance belongs to [agent access to your code](capability:agent-code-access).
Entries
Group by
EntrySignals
Contributes to
@cap-js/mcp@cap-js/mcpA CAP plugin that serves an @mcp-annotated service over MCP with three generated tools, describe, query and call_action, and writes its endpoint into the local agent's configuration in development.sap official, cap
SAP prohibits gateway/proxy use for SAP Application APIs; the Atlas applies that prohibition to CAP wrappers around those APIs. Data changes require application-defined unbound actions, and the adapter supplies no rate limiting, agent-action audit logging, approval workflows or policy enforcement. In beta, with nine releases in the six weeks after the first, so pin it.
Exposes CAP services as MCP servers for AI agents
@cap-js/ord@cap-js/ordGenerates Open Resource Discovery documents from a CAP model.sap official, cap
Generates Open Resource Discovery documents from a CAP model
Details
For your agent
- Ref
actor:henrybrink- JSON
- /actors/henrybrink.json
- MCP
- Connecting an agent