Expose AgentKit over MCP

Create an AgentKit MCP config, a per-user instance URL, and one Streamable HTTP client call. Then stop.

Guardrails

MUST use Streamable HTTP. stdio and SSE are not supported.
MUST pass the exact dashboard Connection Name (connection_name). Never invent a slug. Never use a connector field for that value.
MUST give each user their own instance URL. Do not share one URL across users.

Read SDK credentials from SCALEKIT_ENVIRONMENT_URL, SCALEKIT_CLIENT_ID, and SCALEKIT_CLIENT_SECRET. Some samples use SCALEKIT_ENV_URL; use SCALEKIT_ENVIRONMENT_URL here. Do not prepend https:// if the value already has a scheme.
A connection is dashboard connector config. A connected account is one user authorized on that connection. This skill authorizes through the MCP instance auth link, not integrate-agentkit app-code token calls.
Gmail can use Connection Name gmail when the dashboard has no Gmail row. Every other connector must already have a dashboard connection. Record that name exactly.
Default language is Python. The Node SDK has no MCP config API. Stay on Python.
Look up tool names with discover-connectors. Do not copy connector pages into the repo.