[ralf401]

Restructure of system/api.rst to mirror the tabbed settings page of 7.3 (api restructure is part of the same feature branch): H2 Token access with H3 Token Access, H3 Password Access and H3 MCP Server, H2 OAuth. The old H2 Authentication Methods is folded into the intro as a general overview that names the three methods without claiming to mirror the page structure. Claims and their anchors, all from the feature branch
origin/private/dk/issue/6519/mcp-server-agents-work-on-zammad-tickets-from-their-own-ai-client of zammad/zammad (7.3):

• Setting api_mcp_access, area API::Base, default off: db/seeds/settings.rb (title 'MCP server'), db/migrate/20261103120000_add_mcp_server.rb
• Request refused while off, whatever the token: mcp_controller.rb (authenticate_with_personal_access_token!, switched-off message before the token check)
• Personal access tokens are the only authentication, Token Access dependency: mcp_controller.rb delegates to application_controller/authenticates.rb#authentication_check_api_token, which refuses when api_token_access is off
• The client does what the token and its owner may: Service::AI::Tool::Runtime :Router.offered? narrows by token (lib/user_info.rb#with_token) and all 26 MCP tools carry permission 'ticket.agent'
• The page shows /mcp and the Claude Code example: app/views/api /access.jst.eco (new file on the feature branch)
• FQDN, alternative FQDN and loopback hosts, browser origins from other origins refused: app/services/service/mcp_server/addresses.rb
• Approval with text and recipients shown, form elicitation of MCP revision 2026-07-28, nothing sent without or with an unshown form: app/services/service/mcp_server/confirmation.rb (NOT_CONFIRMED, form capability check), call_tool.rb (elicitation/create, spec suggestion for every result of 2026-07-28), create_article/preparation.rb (confirmation preview and required: outbound || !internal)

Heading name "MCP Server" and no "Tab" in headings per review in zammad-admin-documentation#1372. make gettext ran with the conda env, the committed locale/admin-docs.pot is its output.

The tool table lists what the client gets, with the anchors of every row:

• The 26 rows are the 26 tool classes in app/services/service/ai/tool/*.rb, each declaring offered_in :mcp and permission 'ticket.agent'; the Router discovers them without a registry (runtime/router.rb) and sorts by tool_name, which is the alphabetical order of the table
• read/write per row is the tool's effect line in its own class (9 write: add _internal_note, create_article, create_ticket, link_knowledge_base_answer, link_tickets, save_shared_draft, send_shared_draft, set_ticket_tags, update_ticket; 17 read)
• Each row's description is a summary of that class's own description string (written for the model), reduced to what an admin deciding on the toggle and the token needs
• The three knowledge base tools appear only with an active knowledge base: get_knowledge_base_answer.rb:32, link_knowledge_base_answer.rb:43 and search_knowledge_base.rb:126 return ::KnowledgeBase.active.exists? (app/models/knowledge_base.rb:90)

Table shape follows manage/roles/permissions.rst (list-table, header row, widths). Cell prose is a paragraph, not a "|" line block, so each description is one msgid instead of one per wrapped line.

[github-actions]

Artifacts

Produced during runtime

📦 html-e9172db

[dominikklein]

Reviewed at 0b621aa7 against Zammad develop 298de2efad. The setup, permission model and 26-tool table match the implementation. I would clarify two points before publishing:

1. Approval is not guaranteed by the client. In system/api.rst around line 139, explicitly tell users to keep approval enabled for Zammad's write tools. When a client cannot show Zammad's confirmation form, the server proceeds without that extra confirmation; the client's settings may also allow tool calls without a prompt. This instruction is already part of Document the MCP server: enabling it and connecting an AI client #1372.
2. Make attachment limits visible. In the read_attachment table row, mention that it reads supported text formats up to 10 MB. Unsupported or larger files return a download link for the user. A short note that outgoing attachments are unsupported would also help set expectations.

The client setup example, compatibility wording and channel-specific HTML limits belong in the linked user guide; I am recording those on zammad/zammad-user-documentation#671 and the website MR so the three versions stay consistent.

The documentation build passes. This was a source/content review; rendered layout and a real client connection were not tested.