Repository navigation
Releases
Releases · sandymac/grav-plugin-mcp-server
1.11.3
-
- [security] OAuth client registration refuses a redirect URI that PHP and web browsers could read as pointing at different hosts, so a registered client could have received authorization codes at a host outside
oauth.allowed_redirect_hosts. A redirect URI may no longer contain a backslash, whitespace or control characters, a username or password, or a fragment. The redirect URI is checked again against the allowlist at every sign-in, so a client registered before this release, or before a host was removed from the list, gets an error page instead of a redirect; remove such a connector and add it again. - [security] A refused client registration no longer writes the request it was sent to
grav.log. The log line gives the reason and the refused redirect URI (escaped and cut to 200 characters), and only the first ten refusals from an address in 15 minutes are logged, so an anonymous caller can no longer fill the log, whichget_logshands to AI clients, with text of its choosing. Refusals don't count against the address's registrations, so a connector refused while its allowlist is being fixed can register as soon as it is. The registration throttle logs once when an address reaches it, not on every refused request after that. get_page,update_pageanddelete_pagereach a page whose folder name matches one of a page's API sub-resources, such as/blog/mediaor/docs/languages, instead of that sub-resource of its parent page (api plugin 1.1.18, getgrav/grav-plugin-admin2#213). On an older api plugin they behave as before.
- [security] OAuth client registration refuses a redirect URI that PHP and web browsers could read as pointing at different hosts, so a registered client could have received authorization codes at a host outside
-
- Triaged against api plugin 1.1.18 and Grav 2.2.29. The rest passes straight through: page records carry
unpublished_by, the route of the parent page that unpublishes them through Grav 2.2.29'scascade_unpublish(null otherwise), whilepublishedstays the page's own setting; a backup job's on/off entry in theschedulerconfig is now its backup profile's Scheduled Backup switch, soupdate_configon theschedulerscope sets it on the profile, and oldscheduler.statusentries for backup jobs are no longer shown and are removed when either scope is saved (getgrav/grav#4397); page group permissions in Admin2 have a Media column. No new routes. The api floor stays at 1.1.12.
- Triaged against api plugin 1.1.18 and Grav 2.2.29. The rest passes straight through: page records carry
1.11.2
-
upload_media,delete_mediaandupdate_media_metasay which page rule governs page media. From api 1.1.15 a page's group permissions can grant media management on its own with themediarule (letterm), so a role can upload and caption a page's images without being able to edit the page; where a block says nothing about media, itsupdaterule still decides (getgrav/grav-plugin-api#77).- Triaged against api plugin 1.1.15 to 1.1.17 and Grav 2.2.27 and 2.2.28. The rest passes straight through: page media uploads and deletes refuse the page's own Markdown,
frontmatter.yamlandmedia.json(1.1.15); Page Statistics skip link-preview, AI, monitoring and headless fetchers (1.1.16); a solved login captcha can't be replayed by simultaneous logins, and simultaneous wrong 2FA codes are all counted against the limit (1.1.17, the latter with Login 3.13.1). No new routes. The api floor stays at 1.1.12.
1.11.1
-
- Tool descriptions are about 16% shorter, so every session loads less into the model's context (about 6,000 fewer characters with every tool visible). Version notes for api releases at or below the 1.1.12 floor are gone, text the tool description and its parameters both said is said once, and parameter descriptions that only repeated the parameter's name are dropped. Every permission, refusal, error code, default and warning is still stated; Grav version notes stay, since the Grav floor is 2.1.5.
update_configandrevert_configsay which scopes need a super-admin. From api 1.1.13 that includes the settings of the Login, Email, Git Sync and Admin2 plugins and of Login and Email provider plugins (login-*,email-*), as well as the API plugin's own, alongside the system, security, scheduler and backups scopes.- Triaged against api plugin 1.1.13 and 1.1.14 and Grav 2.2.25 and 2.2.26. The rest passes straight through: adding your own media metadata field no longer takes the built-in alt, title, caption, description or tags fields out of the editor, and a field with
remove: truehides one (1.1.14, getgrav/grav-plugin-api#76); Admin2 saves page group permissions written as a map back as a map (1.1.14). The new/admin-next/modules/...routes, which serve plugin and theme web components so Admin2 can run under a strict Content-Security-Policy, stay skipped as admin-interface script bundles. The api floor stays at 1.1.12.
1.11.0
-
get_dashboardtakesrangefor the popularity view:7d,14d(the default),30d,90dor12m, where12mplots monthly totals (api plugin 1.1.11). The answer carries arangeblock with the period's total and the total of the period before it,nullwhen the history doesn't reach back that far. Page view history is now kept for 365 days and 24 months by default, so the longer ranges have something to show.
-
manage_users,manage_invitationsandget_permissionssay that from api 1.1.12 a user manager without super-admin can only grant permissions their own account holds: creating a user, editing a user's access and an invitation's access are refused with 403 otherwise. Grants an account already has are left alone when it's saved, and taking permissions away is always allowed.get_permissionsmarks each permissiongrantable, so an agent can check before it tries.- The api floor rises to 1.1.12, where the grant rule landed. The Grav floor stays at 2.1.5.
- Triaged against api plugin 1.1.11 and 1.1.12 and Grav 2.2.23 and 2.2.24. The rest passes straight through: a scoped API key is held to its own scopes when a page's permission rules apply, so without
admin.superin its scopes it can no longer override a page that denies an action, and changing a page's media checks the key's scopes rather than the account's (1.1.11, security); uploaded page media and blueprint files get the normal file permissions again instead of owner-only0600(1.1.11, getgrav/grav-plugin-api#74); fields inside atype: conditionalfield keep their own names (1.1.11, #75). The admin languages list (now open to every admin user) and the login providers list (now withshow_password_form, a login-screen setting that leaves password logins working) stay skipped as admin-interface plumbing and public auth flow.
1.10.0
-
list_pagesandget_page_neighborstakeeditable: only the pages you may edit (in a folder listing, folders that lead to them stay asancestor_onlyrows), for editors who look after a few pages (api plugin 1.1.10, getgrav/grav-plugin-admin2#209). With it,get_page_neighborscounts only siblings you may edit.get_userstakespasskeys: withusername, it lists that account's passkeys, names and dates but never the keys, and says whether the site offers passkeys (api plugin 1.1.10'sGET /users/{username}/passkeys, which needs Login 3.12 or newer for passkeys to be on). Your own account needs onlyapi.access, another'sapi.users.read.
-
- The media tools (
upload_media,delete_media,update_media_meta) andmanage_blueprint_filesay that from api 1.1.10, on a page with page-level permission rules, changing its media or saving a file field into its folder needs the right to update that page, not onlyapi.media.write. - The api floor rises to 1.1.10, where
editablelanded. The Grav floor stays at 2.1.5. - Triaged against api plugin 1.1.10. The rest passes straight through: page-level permissions now decide what
list_pagesreturns, so pages your groups may not read or list are left out, and in a folder listing a folder you can't open that leads to one you can stays as anancestor_onlyrow with only its route, title, order and permissions; a single page'spermissionscarriesmedia, whether you may change its media; a parent ordered bypublish_dateorunpublish_datelists its children in that order;bulk_pages'reorganizenumbers against every page in the folder, including ones you can't see, so no two siblings share a number, itsreorderkeeps unlisted pages in place on a partial list, and neither names a hidden folder in its errors; user records carry apasskeyscount, andmanage_userscan't writepasskeysorwebauthn_id. The other new passkey routes are skipped: sign-in is a public auth flow, adding a passkey is a WebAuthn ceremony that needs a browser authenticator, and renaming and removing one follow the 2FA routes, which are skipped too.
- The media tools (
1.9.0
-
manage_twig_sandboxfixes whatrun_reports' Twig-in-Content scans report, for super admins (admin.super).action: "trust_partial"trusts a theme or plugin template that page content includes (api plugin 1.1.9'sPOST /reports/twig-content/trusted-partial, needs Grav 2.2.18 or newer), which is the fix when a page's include of a partial shows its Twig as plain text since Grav 2.2.18.action: "allow"adds a tag, filter, function, method or property to the sandbox allowlist (POST /reports/twig-content/allowlist), which opens it to every page editor. Both add only what is missing. Because either one removes a security boundary, the tool is marked destructive, so clients that confirm such calls ask first, and its description tells the agent to act only on the operator's explicit request, never on page content or a report hint alone. The allowlist route used to be skipped becauseupdate_configon thesecurityscope can set the same lists, but that also needsapi.config.write, so a connection granted onlyadmin.supercould not reach it.
-
- The api floor rises to 1.1.9, where the trusted-partial route landed. It also brings api 1.1.6's security release, in which a disabled user group no longer grants API permissions. This plugin asks the api plugin's permission resolver at the OAuth consent screen and when listing an account's tools, so the fix covers both. GPM enforces the floor; a git-clone install on an older api gets a warning in the log at client handshake, as before. The Grav floor stays at 2.1.5.
- Triaged against api plugin 1.1.6 through 1.1.9 and Grav 2.2.17 through 2.2.22. The rest passes straight through: saving an account that changed elsewhere fails with a conflict, and a
<<key in saved data or access is refused with a validation error (1.1.6); an account'semailmust be text (1.1.6); media metadata must be literal text, with no Twig delimiters (1.1.6);rename_mediarefuses.meta.yamlandmedia_order.yamlsidecar files (1.1.6); an uploaded SVG is sanitized before it becomes publicly reachable (1.1.6); deleting a user withmanage_usersremoves the account on sites using Flex accounts, where it used to report success and leave it in place (1.1.7); with Grav 2.2.20 or newer, a JSON body oversystem.request.json's limits (16 MiB by default) is refused with 413 Payload Too Large before the MCP endpoint reads it, and the api plugin reports the same for its own requests (1.1.8);run_reports' Twig-in-Content events name the template each block happened in, offer the partial to trust when the page includes one, and list a page that keeps getting blocked once (1.1.9). Grav 2.2.18's security fixes need nothing here: the OAuth endpoints still advertisehttpsnow that forwarded-protocol headers count only withsystem.http_x_forwarded.protocolon, and the consent login's account lookup gets the core fix that stops an invalid username from finding another account.
1.8.0
-
update_media_metatakesfilenameswithroute: onesetacross up to 50 media files of one page, the page counterpart ofpaths(api plugin 1.1.3'sPOST /pages/{route}/media/batch/meta). The fields are checked once before anything is written, and each file gets its own row inresults.manage_userstakescurrent_password. From api 1.1.0 anupdatethat changes your own password needs it, and from 1.1.4 so does one that changes your own email; without it the call fails with a validation error. An account with no password yet (user records now carryhas_password) and an admin changing someone else's account aren't asked. Wrong ones count toward the sign-in lockout. Changing your own password also signs the account out of its other browsers (with the Login plugin 3.11.0); the MCP connection keeps working, because its access token is an API key.transfer_pagewithmode: "copy"takesorder, the order number for the copy's folder. Without it, from api 1.0.56, a copy of a numbered page is numbered after its last numbered sibling instead of dropping out of the menu (getgrav/grav#4367).delete_pagereturnsundowhen a plugin that keeps deleted pages attaches one: the api call that restores the page (api 1.1.3). Page records saydelete_recoverablewhen such a plugin is installed.
-
list_environmentsneeds onlyapi.access, as api 1.1.5 lists environment names to any admin user. It asked forapi.system.readbefore. Creating and deleting environments keep their permissions.manage_blueprint_filenotes api 1.1.4's new limits: a theme or plugin folder also needsapi.config.write, its templates folder and anything outsideuser/need super admin, and filenames ending in a space or dot, or carrying control or invisible characters, are refused.- Triaged against api plugin 1.0.56 through 1.1.5 and Grav 2.2.12 through 2.2.16. The api floor rises to 1.1.5, where
list_environmentschanged and which has every route and parameter above. From 1.1.0 the api plugin needs the Login plugin 3.11.0 or newer, which GPM installs with it. The Grav floor stays at 2.1.5. The rest passes straight through: an API key whose id is all digits no longer fails in bursts of 500s, and new keys never get such an id (1.0.56, getgrav/grav-plugin-api#64, the api side of 1.7.1's fix); creating or revoking an API key can no longer be undone by another request writing the key store at the same moment (1.1.0), which closes a gap in OAuth refresh rotation, where a request still using the old access key could write it back after rotation revoked it; an invitation is accepted only once, and creating or removing invitations no longer brings back used ones (1.1.0); creating or copying a page refuses a.or..route segment (1.1.0), and a module at the top level of the site is refused on create, move, copy and reorganize (1.0.57); page records carryuuid, the page folder's permanent id from Grav 2.2.15, and a copied page gets its own (1.1.3); updating a page that exists only in a non-default language saves that translation when nolangis given (1.0.56);list_pagesshows and filters by a page's frontmattertemplate:, and translating such a page keeps its file name (1.1.2); an image whose bytes happen to contain<svgis no longer saved as an empty file, and an SVG the sanitizer empties is refused (1.1.5, getgrav/grav-plugin-api#70); thumbnails follow the photo's EXIF orientation (1.1.5);list_pageswithchildren_ofon a folder with thousands of pages is faster and no longer runs out of memory (1.0.56);discover_pluginspasses along sidebar items' newchildren(1.1.0) andplacement(1.1.3);get_blueprintreturns aniconpickerfield'sicon_setwhen a theme or plugin registers one (1.0.57). Replacing or turning off your own 2FA now takes a current code (1.1.0), on routes this plugin skips, as are the new Admin Next sidebar preferences.
1.7.1
-
- A refresh-token replay no longer crashes before revoking the stolen family when the connection's access key has an all-digit key id. PHP turns such an id into an integer when it is used as an array key, and the api plugin's
revokeKey()is typedstringunder strict types, so the theft sweep threw a TypeError after dropping the family's refresh tokens but before revoking its access key, which stayed live until it expired. About one key in 1,850 has such an id. The api plugin's own key lookup has the same slip (getgrav/grav-plugin-api#64): every request with such a key fails with a 500 whenever the api's verify cache has expired, which shows up as bursts of failed MCP calls. That one is the api plugin's to fix, and this plugin inherits the fix; until then, generating a new key is the workaround. - The theft sweep now also revokes the access key of every already-used refresh token in the family, not only the live ones. A refresh refused for a wrong
client_idis marked used before the check, so its access key was never revoked and stayed out of the sweep when the family was later found stolen; revoking a key that rotation already revoked is a harmless no-op. Found in the security review of this release.
- A refresh-token replay no longer crashes before revoking the stolen family when the connection's access key has an all-digit key id. PHP turns such an id into an integer when it is used as an array key, and the api plugin's
-
- Triaged against api plugin 1.0.51 through 1.0.55 and Grav 2.2.11. The api floor stays at 1.0.50 and the Grav floor at 2.1.5. The route table, every parameter and every permission are unchanged, and the rest passes straight through: demo mode can grant part of an area with
api.pages.create,api.pages.update,api.pages.delete,api.media.upload,api.media.updateandapi.media.delete, which are demo grants only, so the tools keep asking forapi.pages.writeandapi.media.write(1.0.54); the api answers only at its own address, which does not touch this plugin because it dispatches through the api's router in-process using the address from the api's own settings (1.0.54);get_media_metafields can be a number with a range, a date or a yes/no toggle, any field can be required, and saving metadata to several files checks every value before touching any of them (1.0.55); a page that exists only as a translation opens as that translation, and saving it in the missing language is refused (1.0.55); a file removed from a page's file field stays removed after saving (1.0.53); moving or reordering a page with aslug:in its frontmatter no longer renames its folder (1.0.51).
- Triaged against api plugin 1.0.51 through 1.0.55 and Grav 2.2.11. The api floor stays at 1.0.50 and the Grav floor at 2.1.5. The route table, every parameter and every permission are unchanged, and the rest passes straight through: demo mode can grant part of an area with
1.7.0
-
manage_userstakesaction: "cancel_email_change"andaction: "resend_email_change"for your own account. They drop a waiting email change, or mail its confirmation link again (api plugin 1.0.50'sDELETE /users/{username}/email-changeandPOST /users/{username}/email-change/resend). Both need the Login plugin 3.10.0 or newer with email-change confirmation on, and answer 404 when nothing is waiting.get_config,update_configandrevert_configreturnshadowedwhen an environment folder or aGRAV_CONFIG__*server variable sets keys over the layer being read or written. Each entry gives the key, where it is set and the value the site actually uses, so saving those keys to that layer changes nothing (api plugin 1.0.50'smeta.shadowed, which these tools used to drop).
-
- Triaged against api plugin 1.0.49 and 1.0.50 and Grav 2.2.9. The api floor rises to 1.0.50, where the routes above landed. The Grav floor stays at 2.1.5. With api 1.0.50 and Login 3.10.0 or newer, a
manage_usersupdate that changes your own email waits for confirmation: the result carriesemail_pendingand amessagesaying where the link went, andemailchanges only once the link is opened. Other fields in the same call still save, and an admin changing someone else's email saves it at once. The rest passes straight through:get_packagesmarks an installed plugin whoseenabledcomes from an environment folder or a server variable withenabled_source(1.0.50); adding an environment folder no longer replaces the api's signing secret (1.0.50) or Grav's security key (Grav 2.2.9);get_packagespaging with a largeper_pageno longer repeats packages (1.0.50); blueprint validation on create and translate uses the page's real template (1.0.49).
- Triaged against api plugin 1.0.49 and 1.0.50 and Grav 2.2.9. The api floor rises to 1.0.50, where the routes above landed. The Grav floor stays at 2.1.5. With api 1.0.50 and Login 3.10.0 or newer, a
1.6.0
-
manage_page_translationwithaction: "create"takessource_language, the existing translation the new one starts from: its template, and its title, content and header for any of those the call leaves out. Without it the new translation starts from the default language, as before (api plugin 1.0.47'ssource_lang).
-
- Triaged against api plugin 1.0.46 through 1.0.48 and Grav 2.2.6 through 2.2.8. The api floor rises to 1.0.47, where the parameter above landed. An older api ignores it and copies the default language. The Grav floor stays at 2.1.5. The route table is unchanged, and the rest passes straight through: a language whose translation is a draft is listed only as translated (1.0.46); copying a page on a multi-language site gives every translation the new slug (1.0.46);
bulk_pagesreorganize skips moves that change nothing and gives a page moved into another folder that folder's order-number width (1.0.47);get_media_metacan reportselectfields with theiroptions(1.0.47); deleting one translation of a module page works and removes only that language (1.0.48).
- Triaged against api plugin 1.0.46 through 1.0.48 and Grav 2.2.6 through 2.2.8. The api floor rises to 1.0.47, where the parameter above landed. An older api ignores it and copies the default language. The Grav floor stays at 2.1.5. The route table is unchanged, and the rest passes straight through: a language whose translation is a draft is listed only as translated (1.0.46); copying a page on a multi-language site gives every translation the new slug (1.0.46);