# Dynamic client registration, defined with a sourced example

GLOSSARY, read 10 Nov 2026

**The short answer.** A step where an MCP client registers itself with an authorization server automatically, so nobody has to create a client ID by hand. Servers that skip it make each team supply a client ID and secret. Per Alation's README, its remote MCP server does not support dynamic client registration, so clients must supply a client_id and client_secret.

## Definition

A step where an MCP client registers itself with an authorization server automatically, so nobody has to create a client ID by hand. Servers that skip it make each team supply a client ID and secret.

## Example from a real server

**Example.** Per Alation's README, its remote MCP server does not support dynamic client registration, so clients must supply a client_id and client_secret.

## Related terms

- [Genie space](/glossary/genie-space/): A Databricks workspace for asking questions of chosen tables in natural language, set up with curated instructions.
- [human confirmation](/glossary/human-confirmation/): A step where a person approves a tool call before it runs.
- [Discovery API](/glossary/discovery-api/): The dbt platform API that returns metadata about a project's models, sources, exposures, tests and runs.

## Where to read more

- [The directory](/)
- [All glossary terms](/glossary/)

## Sources

- github.com/Alation/alation-ai-agent-sdk/blob/main/README.md: https://github.com/Alation/alation-ai-agent-sdk/blob/main/README.md (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datamcpservers.com/glossary/dynamic-client-registration/
