create-arc1-extension

You can build custom tools for an MCP server by developing a plugin that extends its functionality without modifying the core. This involves using scaffolding to generate necessary files, writing TypeScript code, and loading the plugin into the server.

The best way to extend ARC-1 functionality with an OData service integration is to scaffold a new plugin repository. This automates file creation and provides architecture guidance on which SAP API to use, avoiding the need to fork the core.

Yes, you need TypeScript experience and familiarity with the ARC-1 API to develop plugins. The plugin development process requires writing TypeScript code to build, load, and test custom tools within the MCP server environment.

Yes, you can add a separate code tier for your MCP server extension. Guided architecture helps you choose between a code tier vs. manifest tier and whether to build an extension or a separate server based on your integration needs.

Scaffolding automates the creation of a new plugin repository with necessary files and configurations. This sets up the foundational structure required to build, load, and test your custom tool within the ARC-1 MCP instance.