Expose AgentKit over MCP

Create an AgentKit MCP config, mint a per-run session token, and make 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 reuse one static mcp_server_url. Mint a session token per identifier and per run with create_session_token.

Gotchas

• 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 list_mcp_connected_accounts auth links, not integrate-agentkit app-code execute_tool calls.
• create_session_token is remint. Call it again before the next run. Do not reuse a token from a previous session.
• New environments ship one connection: GitHub, Connection Name github-connect. Every other connector, Gmail and Google Calendar included, needs its own connection in AgentKit → Connections. Record each name exactly.
• Default language is Python. If the repo is Node, follow references/node.md: the Node SDK has the same API on scalekit.actions.mcp (createConfig, listConnectedAccounts, createSessionToken).
• Confirm every tool name on the connector's page in https://docs.scalekit.com/agentkit/connectors.md, or with discover-connectors, before you put it in a config. Do not copy connector pages into the repo.