Skip to main content
Smithers ships first-party event sources for GitHub, Linear, and Telegram (@smthrs/integrations) that turn provider webhooks into durable workflow signals. For other services (Notion, Slack, etc.), your app owns the integration: pick tools on an SDK agent, skills/plugins/MCP on a CLI agent, or an external CLI run inside a task. If the service already exposes an MCP server and you’re using an SDK agent, MCP Toolset turns that server into AI SDK tools.

Pattern 1: Pass tools to an SDK agent

Use this when the agent needs judgment but the external calls should stay explicit and reviewable.

Pattern 2: Pass a skill / plugin / MCP config to a CLI agent

Use this when your CLI agent already supports external integrations and Smithers should only orchestrate the task.

Pattern 3: Run an external CLI in a task

Use this when the step is deterministic and you do not need the model involved.

Choosing between them

See also

React hook patterns: /recipes#custom-hooks-over-ctx. Agent-class details: SDK agents, MCP Toolset, CLI agents. To wire Smithers into your coding agent so it can drive workflows, see Agent Support.