The APIs: REST, GraphQL and custom endpoints
Every Core dna site answers three kinds of API request under /cdna-api: REST for everything, GraphQL for reads that span several entity types, and web events for endpoints you define yourself as jobs. Which fits which task, one worked request for each, and what is true of all three. Jobs were called hooks until the module was renamed Orchestration; the API's routes still use the old name.
Every Core dna site runs an MCP server, which lets an AI assistant in your editor read and change the site's records and configuration as you. For any developer or editor who works with an assistant.
One page: what the server is and what its tools cover, a configuration to copy with the development site shared and production kept to each person's own settings, whom the connection acts as, and how to use it to learn an inherited site's content model before you open its templates.
It is a tool for people at work on a site, not a surface for integrations; those use the REST API with the credentials in Credentials and access.