Implement LTI 1.3 Dynamic Registration to automate tool registration on a new platform without manual administrator data entry
domain: imsglobal.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Receive the openid_configuration and registration_token parameters on the tool's registration initiation URL
Fetch the platform's OpenID Connect Discovery document from the openid_configuration URL
Extract registration_endpoint, jwks_uri, token_endpoint, and authorize_endpoint from the discovery document
POST a JSON client metadata object to the registration_endpoint with the Bearer registration_token, including redirect_uris, initiate_login_uri, jwks_uri, and the https://purl.imsglobal.org/spec/lti-tool-configuration claim
Store the client_id from the registration response along with the platform's deployment_id and all endpoints
Redirect the administrator browser to the platform's configuration completion URL to finalize the registration
Known gotchas
The registration_token is single-use with a short TTL; the entire registration flow must complete before it expires
The lti-tool-configuration claim in the registration request must list the exact set of LTI message types and scopes the tool needs; adding them later requires re-registration on many platforms
Some platforms derive the deployment_id from the registration response, others send it via a post-registration webhook; handle both patterns
Give your agent this knowledge — and 15,800+ more routes
One MCP install gives any agent live access to the full route map across 5,800+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?