Add a custom tool or MCP server

Before you begin

You need a business workspace and owner or dashboard editor access. For authenticated HTTP tools, prepare a credential profile. For MCP, have the server's HTTPS URL.

Install a recipe

1. Open Tools and choose Add tools.
2. Search for the service and select its connector pack.
3. Review the tools and required credential keys.
4. Choose Add tools to install the pack.
5. Create its first credential profile when prompted.

A recipe supplies ready-made requests. Bind the profile wherever the connector runs. When an installed pack offers an update, review the changes and choose Update connector.

Build an HTTP tool

1. Choose Bring your own in the catalog and select Build tools by hand.
2. Name the integration group and create its first tool.
3. Describe the action and when the AI should use it.
4. Set the HTTP method and HTTPS endpoint.
5. Choose the authentication method and a saved credential key.
6. Use Insert to add agent-provided values to the URL, headers or request body.
7. Define each input's name, type, description and allowed values where needed.
8. Review the request and its suggested approval level.
9. Choose Create tool.

The request template combines arguments supplied by the agent with credentials from the bound profile. Botchi injects credential values during execution; the model does not receive them.

To start from a specification, choose Import an OpenAPI file instead. Import OpenAPI 3.x or Swagger 2.0 JSON/YAML, then review the HTTPS server, credential keys, endpoints, inputs and read/write risks. Parsing happens locally in your browser; creating the connector and selected tools is atomic.

Make an argument optional

1. Clear Required for the input, or ask the dashboard Assistant to set required to false.
2. Place its placeholder as the whole value where omission should remove that value.
3. Test both supplied and omitted arguments.

For an omitted input named limit, a complete placeholder such as {{args.limit}} removes the query parameter, header, JSON object property, or entire body. Paths, composite values and array elements still require a value. Botchi inserts no defaults. Optional booleans in the tester offer Not sent, true and false.

Do not name an input executionTargetId: Botchi reserves it for identity selection and refuses new saves. Rename it in older tools before adding credential profiles. An older tool using it works only while its connector has no profile; adding one makes it unavailable to agents until renamed.

Connect an MCP server

1. Open Add tools and search for the provider, or paste its HTTPS server URL.
2. Select the server.
3. Follow the detected setup: no authentication, provider sign-in, or API key.
4. Complete provider sign-in in the popup when OAuth is required.
5. Review the discovered tools on the connector page.

Botchi stores and refreshes OAuth tokens. Server tools can be used by agents, workflow tool steps and the dashboard Assistant.

Search the public MCP directory opens unverified servers separately. Check the displayed operator domain. Domain ownership proves who runs a server; it does not establish tool quality or safety. Providers that restrict OAuth to approved AI clients can be marked unavailable.

MCP tools start with a recommendation to ask for approval, regardless of the server's risk claims. Review agent tool policy before allowing automatic execution.

Supply your own OAuth app

If automatic app registration is refused:

1. Create an OAuth app in the provider's developer console.
2. Open Pre-registered app (advanced) in the MCP server's settings.
3. Copy Botchi's callback URI into the provider app.
4. Enter the client ID, client secret if required, and scopes.
5. Use the required-scopes control to select the scopes the server requests.
6. Save the new client ID to start sign-in.

Add other published scopes only when needed. If sign-in fails, correct the reported redirect URI, scope or app-approval problem before retrying.

Resolve sync problems

1. Open the MCP connector flagged in Needs attention.
2. Inspect Tools for excluded tools and their reasons when the server is partially synced.
3. Choose Re-sync after correcting the server or connection.

Loaded tools keep working during partial sync; a workflow using an excluded tool fails with its reason. Enabled catalogs older than one hour refresh before use. Failed refreshes retain the last successful catalog and retry after a cooldown.

An incompatible-schema error triggers a refresh and requests a new run; Botchi does not repeat the operation automatically. Removed tools fail explicitly. Their names are never reassigned, and existing references work again if the same tool returns.

Related

• Manage credential profiles
• Grant tools and set approvals
• Use tools in workflows
• Connect an AI client to Botchi