@toolforest/toolforest-plugin

OpenClaw plugin that connects your Toolforest toolkits as native agent tools. Supports tools across Google Workspace, GitHub, prediction markets, health trackers, and more.

Installation

1. Install the plugin

openclaw plugins install @toolforest/toolforest-plugin@latest

2. Set your API key

openclaw config set plugins.entries.toolforest.config.apiKey "tfo_your_key_here"

Get your API key at app.toolforest.io.

3. Make tools available on all tool profiles

existing=$(openclaw config get tools.alsoAllow 2>/dev/null || echo '[]')
openclaw config set tools.alsoAllow "$(node -e "const v=JSON.parse('$existing');
if(!v.includes('toolforest'))v.push('toolforest'); console.log(JSON.stringify(v))")"

Note: tools.alsoAllow ensures Toolforest tools remain available when using non-full tool profiles such as coding, minimal, and messaging. The command above safely appends toolforest to any existing entries — unlike openclaw config set tools.alsoAllow '["toolforest"]' which would replace the entire list and remove any other plugins you have configured.

4. Restart the gateway

openclaw gateway restart

5. Verify

openclaw config get tools.alsoAllow
openclaw plugins inspect toolforest

Or set the TOOLFOREST_API_KEY environment variable as an alternative to step 2.

Options

| Key | Description | Default | |-----|-------------|---------| | apiKey | Toolforest API key (tfo_...) | TOOLFOREST_API_KEY env var | | remoteUrl | Override the MCP endpoint URL | https://mcp.toolforest.io/mcp |

How it works

1. Connects to the Toolforest MCP server using your API key
2. Registers 4 meta-tools (list_toolkits, list_toolkit_tools, list_additional_toolkits, execute_tool) for on-demand toolkit discovery and execution
3. Injects prompt guidance so the agent knows which toolkits are available
4. Refreshes the toolkit list in the background every 5 minutes

If the plugin fails to connect, the agent will surface a helpful error message with setup instructions rather than silently failing.

Features

• Native tool registration — Toolforest tools appear as first-class OpenClaw tools
• Dynamic prompt guidance — agent sees which toolkits are connected, updated every 5 minutes
• Error state guidance — if connection fails, the agent guides the user through setup
• Fallback skill — /toolforest-mcp skill provides curl-based MCP access when native tools are unavailable
• Client-side validation — validates tool arguments locally before sending to the server

Fallback skill

If the native tools aren't working, use the built-in fallback skill:

/toolforest-mcp

This gives the agent curl-based instructions to call the Toolforest MCP server directly.

Requirements

• OpenClaw >= 2026.3.0
• Node.js >= 20
• A Toolforest account with at least one connected toolkit

License

MIT