The agent reads documentation, classifies the integration, writes SDK code, configures providers and policies, and guides the user through browser-based OAuth consent to enable the new connection.
The user provides a natural language description of the desired integration (e.g., connecting Slack). The agent uses the Alter Docs MCP server to fetch relevant setup guides and classification logic. It then walks through the steps: creating the app, minting a scoped key, configuring the provider, wiring the SDK into the codebase, and setting runtime policies (such as human-in-the-loop approvals). The agent identifies when browser-based steps are required and hands control back to the user, while the actual account modifications are performed by the alter CLI running in the user's shell.
- Category: Software development
- Effect: Changes data in your accounts
- MCP servers: Alter Docs MCP (https://koskamo.com/explore/alter-docs-mcp)
- Source: Alter Docs MCP Server | Alter (https://docs.alterauth.com/mcp)
- Source quote: "The agent calls get_started , classifies the use case, and walks the flow — creating the app, minting a scoped key, configuring the provider, wiring the SDK, setting the runtime policy ... and confirming a real call produced audit events."
- Playbook page: https://koskamo.com/explore/use-cases/set-up-alter-integration-for-a-specific-use-case
Prompt: Set up Alter so a user can connect their Slack workspace and my app bot can post in a channel they approve.