Skip to main content

Create & Manage ToolSets

This guide covers how to create, configure, and manage ToolSets in the Nexla Platform. ToolSets are the unit of deployment for MCP servers -- once you have assembled the right set of tools, you can deploy the ToolSet as an MCP server that AI agents connect to.

Creating a ToolSet​

There are two ways to create a ToolSet: from existing tools in the Tools Registry, or directly from Nexsets.

From Existing Tools​

Use this approach when you have already created tools and want to bundle them into a deployable collection.

  1. Navigate to the AI tab and open the ToolSets page.
  2. Click Create ToolSet.
  3. Enter a name for the ToolSet. Choose a name that reflects its purpose or domain (e.g., "Sales Data Tools", "Inventory Lookup Agent").
  4. Optionally, add a description to help collaborators understand what the ToolSet is for.
  5. Select one or more tools from the Tools Registry to include in the ToolSet.
  6. Click Save to create the ToolSet.

The ToolSet is created with an active status and appears in the ToolSets listing.

This is the fastest path from data to a working MCP server. When you create a ToolSet from Nexsets, Nexla automatically generates tools from the selected Nexsets, bundles them into a new ToolSet, and creates an MCP server export -- all in one step.

  1. From the AI tab, open the Nexsets browser.
  2. Select one or more Nexsets that you want to expose as AI tools.
  3. Click Create ToolSet from Selected.
  4. Enter a name and optional description for the ToolSet.
  5. Nexla generates tools from the selected Nexsets, creates the ToolSet, and provisions an MCP server export automatically.

You can also create a ToolSet from Nexsets programmatically using the API: POST /v1/toolsets:from_nexsets.

tip

Creating from Nexsets is the fastest way to go from data to a working MCP server. It generates tools, bundles them into a ToolSet, and creates an MCP server export automatically. Use this approach when you want to get up and running quickly.

Viewing ToolSets​

The ToolSets page displays all of your ToolSets as cards. Each card shows:

  • Name and description
  • Tool count -- the number of tools included
  • Export count -- the number of MCP server exports
  • Status -- active or paused
  • Creation date

Use the search bar to find ToolSets by name, or apply filters to narrow the list by status or tags.

Managing Tools in a ToolSet​

You can add or remove tools from a ToolSet at any time.

  1. Click on a ToolSet to open the ToolSet detail drawer.
  2. Navigate to the Tools tab.
  3. Click Manage Tools to open the Tools Manager.
  4. Add tools by selecting from the Tools Registry, or remove tools by deselecting them.
  5. Save your changes.

The ToolSet's manifest is updated automatically to reflect the new tool list.

note

When you add or remove tools from a ToolSet, any active MCP server exports will reflect the changes. Connected AI agents will see the updated tool list on their next request.

Cloning a ToolSet​

Cloning creates a copy of an existing ToolSet with a new name, a new MCP server key, and a new export. All tools from the original ToolSet are copied to the clone.

To clone a ToolSet, open the ToolSet detail and select the Clone action.

Cloning is useful for:

  • Environment-specific variants -- Clone a production ToolSet to create a staging version for testing changes before they go live.
  • Testing changes safely -- Experiment with tool additions or removals on a clone without affecting the original.
  • Sharing templates across teams -- Create a base ToolSet and clone it for different teams, letting each team customize their copy.

Activating and Pausing​

You can toggle a ToolSet between active and paused status at any time.

  • Active -- The ToolSet is fully operational. MCP server exports accept new connections and serve tool requests.
  • Paused -- The ToolSet is temporarily disabled. Existing MCP server connections remain active, but new connections are blocked.

To change the status, open the ToolSet detail and toggle the status control. Pausing is useful during maintenance, incident response, or when you need to temporarily restrict access without deleting the ToolSet.

Deleting a ToolSet​

Deleting a ToolSet performs a soft delete. The ToolSet is removed from the active listing and all associated MCP server exports are deactivated.

warning

Deleting a ToolSet will deactivate all its MCP server exports. Any AI agents connected to those servers will lose access to the tools. Make sure no critical workflows depend on the ToolSet before deleting it.

Next Steps​