Person
automatizatodo
GitHub@automatizatodolast push
Capabilities
Provides
Agent access to your codeCAPAgent access to your codeLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from [MCP servers](capability:mcp-servers), which is a protocol adapter on your own running service, and from [agent guidance](capability:agent-guidance), which is knowledge handed over as files rather than read from the thing itself.
Entries
Group by
EntrySignals
Maintains
capforgecapforgeAn MCP server that scaffolds CAP and CDS for a coding agent and then holds it to cds compile — the agent does not stop until the generated code builds clean.independent, cap
MCP server scaffolding CAP and CDS checked by cds compile
Details
History
- capforgeMCP is how this is delivered, not what it answers — artifact_type carries the transport. It helps an agent work on real code rather than exposing a running service to one, which is a different capability.
- capforgeTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- capforgePlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- First entry seenDiscovered via npm registry, The discovery pass.
For your agent
- Ref
actor:automatizatodo- JSON
- /actors/automatizatodo.json
- MCP
- Connecting an agent