dbt-mcp workflow question: versioning and state management

Has anyone integrated dbt-mcp into a CI/CD pipeline where you need to handle multiple dbt project versions? We're trying to version our dbt models but getting confused about how the MCP server maintains state between runs. Do you just spin up fresh instances, or is there a way to persist manifest caching to speed things up? Would appreciate any real-world setup tips.