Person
Maher Darweesh
GitHub@Maherd18last push
Capabilities
Provides
Agent access to your codeABAPAgent 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.Tool governanceABAPTool governanceControlling what an agent may call, with which authorisations, and leaving an audit trail of what it did. The authorisation question that MCP exposure raises but does not answer.
Entries
Group by
EntrySignals
Maintains
Maherd18/sap-mcp-serverMaherd18/sap-mcp-serverAn MCP server for ABAP development over the ADT resources: eight tools, each checked against a JSON policy file before the call reaches the system, with activation and transport release held for a person to approve.independent, abap
Development and sandbox systems only: the README warns against pointing it at production. Transport release is never executed, since the tool exists to show the policy stopping it, and separation of duties is checked against the `identity.approvers` list in the policy file rather than against SAP authorisations, so it holds as far as that file does and no further. The write path has been tested with ABAP classes and other object types may need adjustments, there is deliberately no tool that creates or deletes an object, and one server instance serves one SAP system.
Policy-checked MCP server for ABAP development over ADT
Details
History
- Maherd18/sap-mcp-serverHanded over as a URL. Behind the ABAP door because the objects it reads and changes are ABAP ones in a system reached over ADT. Two edges: [agent access to your code](capability:agent-code-access) for the eight tools over ADT, with `create_objects` entered as false because the README states that choice rather than leaving it out, and [tool governance](capability:tool-governance) for the policy file, the allow-lists, the read-only switch, the approval and separation-of-duties rules, the dry-run mode and the audit log, which the README's own opening makes the point of the server. [MCP servers](capability:mcp-servers) was considered and left off: that capability is a protocol adapter on a running application service, and this one helps somebody write code, which its own description sends here. No flavor is stated, since the README names no ABAP release or cloud edition; `tool_count` is left out because the README names no number, and the eight in the prose is a count of its own Tools table. The second [tool governance](capability:tool-governance) provider on the ABAP door, where the reading was community-only with one; the coverage note is left to revisit by hand.
- First entry seenDiscovered via Added by hand.
For your agent
- Ref
actor:maherd18- JSON
- /actors/maherd18.json
- MCP
- Connecting an agent