> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.moveworks.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.moveworks.com/_mcp/server.

# ToolSmith

ToolSmith is an assistant for creating, editing, and debugging plugins. You describe the workflow you want, the systems it touches, and who will use it. ToolSmith proposes a plan, and once you approve it, it builds the plugin.

ToolSmith is available to Moveworks customers in early access. To register interest, use the [ToolSmith page on the AI Agent Marketplace](https://marketplace.moveworks.com/toolsmith).

# How a build works

1. **Describe the plugin.** Say what it should do, which systems are involved, and who will use it. For example: "Retrieve my team's open Linear issues and rank them by priority."
2. **Review the proposed steps.** ToolSmith lays out the connections, actions, and steps it intends to create. You can adjust the plan before anything is built.
3. **Approve and connect your systems.** ToolSmith starts the work after approval. If a connection needs credentials, it asks you for them before continuing.
4. **Test and roll out.** The result is a normal Agent Studio plugin. Test it with your own data, set access control, and publish it the same way you would a hand-built plugin.

# What ToolSmith uses

* **The [Action Catalog](/agent-studio/toolsmith/action-catalog).** A library of third-party API operations and their documentation. When your plugin needs an HTTP action against a covered system, ToolSmith already has the endpoint, parameters, and schemas, so it skips the research step and gets the request shape right the first time.
* **Your connectors.** Every action ToolSmith builds is attached to a connector you configure. See [Connectors](/agent-studio/connectors).
* **Execution logs.** When you ask ToolSmith to fix a plugin, it reads the plugin's execution logs to find what went wrong and proposes edits.

# Editing and debugging existing plugins

ToolSmith is not only for new plugins. Describe the change you need, or explain what is going wrong, and ToolSmith proposes edits to the existing plugin. You review and approve edits the same way you approve a new build.

# Relationship to Agent Architect

[Agent Architect](/agent-studio/toolsmith/agent-architect) is the read-and-advise copilot inside the Agent Studio editor: it explains and suggests, and you author the changes. ToolSmith builds and edits plugins on your behalf after you approve a plan. Both are available; use Agent Architect for guidance while you hand-build, and ToolSmith when you want the build done for you.

# FAQ

## Do I still need to configure connectors and access control?

Yes. ToolSmith builds the plugin; you own the connection credentials, permissions, and testing, exactly as with a hand-built plugin.

## Which systems can ToolSmith build actions for?

Any system with an API. Systems in the [Action Catalog](/agent-studio/toolsmith/action-catalog) are faster and more reliable because ToolSmith already has their documentation. Check coverage on the AI Agent Marketplace Explore page with the **ToolSmith** filter.

## Where do I use ToolSmith?

In Agent Studio, for customers with early access. Register interest on the [Marketplace ToolSmith page](https://marketplace.moveworks.com/toolsmith).