Uptake PluMCP 0.3.0 (beta2) with OAuth Client ID Metadata Documents (CIMD) support

[kumarshantanu]

PluMCP 0.3.0 uptake

PluMCP 0.3.0 has full support for the MCP 2025-Nov-25 spec. See the changelog for all features.

To upgrade update deps.edn with the following coordinates:

io.github.plumce/plumcp.core-json-cheshire {:mvn/version "0.3.0-beta2"}
...
cheshire/cheshire {:mvn/version "6.2.0"}

PluMCP 0.3.0 is currently in beta2 - consider testing before switching to the new version.

CIMD Support

The MCP 2025-Nov-25 spec does not promote OAuth Dynamic Client Registration (DCR) as the default/preferred client registration mechanism anymore. It also supports Client ID Metadata Documents (CIMD) as a first class alternative to DCR. With version 0.3.0 uptake ECA may publish CIMD support as follows:

Publish a file client.json (or suitably named, e.g. mcp-client.json) on the ECA website with the following content:

{
  "client_id": "https://<eca-website-host-fixme>.com/client.json",
  "client_name": "ECA PluMCP Client",
  "redirect_uris": [
    "http://localhost:6277/"
  ],
  "grant_types": [
    "authorization_code"
  ],
  "response_types": [
    "code"
  ],
  "token_endpoint_auth_method": "none"
}

The "redirect_uris" entry above should match :auth-options config :redirect-uris, :callback-redirect-uri and :callback-start-server.

Then, in :auth-options map specify the following pointing to this URL.

{
  :client-id "https://.../client.json"
}

Breaking changes

There are no known breaking changes w.r.t. ECA in this uptake.