Desktop appDesktop apptypeAn application you run locally with a desktop user interface. It may be distributed as an installer or built from source; it is the workspace itself, rather than a library, command-line tool or hosted utility.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

Werkbank

A local desktop workspace for AI conversations, attached files and generated HTML Spaces, run by a goose agent and offering a catalog of SAP MCP connectors and ABAP, CAP and UI5 skills.

Werkbank keeps conversations, attached files and generated HTML Spaces in a local workspace, using a project-local goose agent through the Agent Client Protocol. Its catalog includes ARC-1 for ABAP development and mcp-sap-docs, alongside ABAP, CAP and UI5 skills. Connectors are selected per conversation, and installation links stop at an in-app review before configuration is applied. The documented setup runs from source on macOS with Node.js 22.12 or newer and an OpenRouter API key; a signed, notarized installer is not included.

Facts

Last pushLicenceApache-2.0

Where it sits

Provides
Agent guidanceABAPCAPUI5Agent guidancecapabilityPackaged knowledge you hand a coding agent so it gets a framework right unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from [agent access to your code](capability:agent-code-access), where the agent reads the real project instead of being handed a file about it.
Requires
goosegooseoutside the atlasthe project-local agent process reached through the Agent Client ProtocolNode.jsNode.jsoutside the atlasthe source-based macOS setup, which requires version 22.12 or newerOpenRouterOpenRouteroutside the atlasmodel access in the documented setup, which asks for an API key and a compatible GOOSE_MODEL

Who is behind it

Marian ZeisMarian ZeisPersonMaintains this
In the atlas: maintains 35, contributes to 86, wrote 25
@marianfoo
maintainer

What it declares

Every artifact

Type
Desktop app
Origin
Independently maintained
Runtime
Node.js

As a desktop app

Runs on
macOS
Distributed through
does not say

Connections4

README

quoted from marianfoo/werkbank under Apache-2.0, read
marianfoo/werkbank/README.mdOn GitHub

Werkbank

Werkbank is a local desktop workbench for AI-assisted conversations, file context, persistent Spaces, MCP connectors, and reusable agent skills. The renderer talks to a project-local Goose process through the Agent Client Protocol; connector configuration and generated work stay in the local project workspace.

What works

  • Streaming conversations with stop, permission, and mode controls
  • Multiple active and archived conversations stored locally
  • Word, PowerPoint, text, CSV, JSON, and image attachments
  • Persistent, sandboxed HTML Spaces generated from grounded data
  • Session-scoped MCP connector selection and guarded .mcpb imports
  • Connector configuration with secret-shaped values stored through Electron safe storage
  • Skill install deep links with an explicit in-app confirmation step
  • Light, dark, and system appearance settings

Local development

Werkbank currently targets macOS for source-based development. Node.js 22.12 or newer is required.

npm install
cp .env.example .env
# Add OPENROUTER_API_KEY and choose a compatible GOOSE_MODEL in .env
npm run dev

The app uses the repository-local goose-home/ and workspace/ directories. Runtime credentials, selected attachments, generated Spaces, and outputs are ignored by Git. Only the files under workspace/demo-files/ are synthetic fixtures intended for tests.

Using the app store

The current release runs from source, so start Werkbank before using an install button:

  1. Complete the local setup above and keep npm run dev running with the Werkbank window open.
  2. Open the Werkbank app store in your browser.
  3. Choose an MCP server or skill and select Add to Werkbank or Add skill.
  4. On the install page, select Open Werkbank and allow the browser to open the werkbank:// link.
  5. Review the source and requested configuration inside Werkbank, provide any required credentials, and confirm the installation.

Installed items appear under Connectors & Skills in the app, where connectors can be configured, restarted, or removed. If an install page does not return to the app, confirm that the Werkbank window is still running, reload the install page, and select Open Werkbank again.

Verification

npm run check

This runs the TypeScript check, Node test suite, and production renderer build.

Connectors and skills

Use Connectors & Skills inside the app to import an MCP bundle, configure an installed connector, restart the local agent, or remove a connector or skill. Browser handoffs use the werkbank:// protocol and always stop at an in-app review dialog.

Add SAP Notes MCP to Werkbank

Connector maintainers can use the same button in their own README. Replace the encoded bundle URL and title in the link target; the hosted page validates the HTTPS source and opens Werkbank's guarded in-app confirmation. See site/README.md for the copyable Markdown.

Publication status

The source, static website, and guarded install handoffs are release-prepared. A signed, notarized desktop installer is not included yet; follow the order in site/README.md before publishing the website or advertising binary downloads.

License

Apache License 2.0

Apache-2.0, read
Agent guidance
  1. abap2UI5 for VS CodeVS Code extension to preview, activate and lint abap2UI5 apps
  2. sap-basis-opsRunbook skills for Basis operations at the OS and database layer
  3. abap-offstack-aunitAgent skill for off-stack ABAP Unit tests and an abaplint gate
  4. ARC-1 SkillsTwenty-two agent skills shipped with arc-1
  5. sapskillsAgent skills for Clean ABAP, ADT in VS Code and guardrails
  6. SuperClaude for SAPClaude Code plugin with an ABAP MCP server and write guards
  7. claude-abap-devFive ABAP workflows for Claude Code on existing MCP servers
  8. DanKromp/skillOverflowCollection of 41 agent skills, 37 for SAP development tasks
  9. sap-ai-dev-toolkitMCP proxy pinning an agent's ABAP tools to one SAP system
  10. sapcli Claude Code PluginAgents and skills that drive sapcli instead of ADT
  11. sap-odata-explorerRust CLI and desktop app for exploring SAP OData services
  12. abap-skillsSeventeen agent skills for ABAP development
  13. ABAP remote filesystemVS Code extension editing ABAP systems over ADT as a filesystem
  14. claude-abap-skillsClaude Code plugins with Clean ABAP rules and templates
  15. SAP Power for KiroSAP skills for the Kiro IDE
  16. SAP Developers MCPHosted MCP server of developers.sap.com tutorials and missions
  17. secondsky/sap-skillsForty SAP development plugins for coding agents
  18. claude-sap-kitClaude Code plugin adding Custom_* tools to arc-1
  19. rap-skillsRAP skills delivered branch-per-target for each deployment
  20. KlystronMCP server in ABAP inside the application server, with agent skills

Details

Sources3
Added by handdiscovered herechecked
github.com/marianfoo/werkbanktree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesnode
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainumbrella, ai-and-agents
History in the atlas3
  1. What Werkbank adds for ABAP, CAP and UI5 is its catalog of development skills; the workspace itself is not specific to any of those stacks. Agent workspaces is narrowed back to BTP.
  2. The project homepage describes "A small, curated shelf of MCP servers and SAP development skills." Its own catalog spans ABAP (ARC-1 and ABAP Cloud), CAP (CAP Upgrade), and UI5 skills; the workspace is not specific to one stack. This intake follows the maintainer’s explicit request after the September source sweep passed it over for lacking a workspace capability; that concern now exists as Agent workspaces. The served views describe which users the project-owned install catalog addresses. Werkbank provides the workspace; each selected connector or skill supplies the stack-specific behavior. No SAP implementation capability is attributed to Werkbank itself.
  3. First seen.
For your agent
Ref
artifact:marianfoo-werkbank
JSON
/artifacts/marianfoo-werkbank.json
MCP
Connecting an agent