Elemental

What is Elemental?

Elemental provides an interface to bring tools provided by Model Context Protocol (MCP) servers into a unified toolbox for use by an agent. It allows MCP tools to be registered and called alongside native tools.

How to use Elemental?

Define MCP servers in the .env file using the mcpServers variable as a JSON string with server name, command, args, and env. Register MCP tools by name using the pattern MCP|server_name|tool_name or use MCP|server_name|* to include all tools from a server. Tools are then available in the toolbox for agent use.

Key features of Elemental

• Integrates MCP server tools with native tools in a single toolbox.
• MCP tools require naming convention MCP|server_name|tool_name.
• Supports registering all tools from a server with a wildcard (*).
• Tools are described and called using the same mechanism as native tools.
• MCP server definitions are stored in a .env file as a JSON string.

Use cases of Elemental

—

FAQ from Elemental

How do I define MCP servers in Elemental?

Define them in the .env file with the mcpServers variable as a JSON string, e.g., mcpServers='{"Github": {"command": "npx", "args": ["-y","@modelcontextprotocol/server-github"], "env": {"GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"}}}'.

How do I register MCP tools?

Register them by name using the pattern MCP|server_name|tool_name (e.g., MCP|Github|list_issues) via box.register_tool_by_name().

Can I use all tools from an MCP server at once?

Yes, use MCP|server_name|* to include all tools provided by that server.

Can MCP tools be used with any language model?

Yes, tools are included in the description and called using the same mechanism as native tools and may be used with any language model.

What naming convention must MCP tools follow?

The name must be MCP|server_name|tool_name, where MCP indicates it comes from an MCP server, server_name matches the key in mcpServers, and tool_name is the individual tool name.