Quickstart Guide
This guide will get you from zero to executing your first LLM tool in minutes.Prerequisites
Before you begin, ensure you have:Maven 3.8+
Included via
mvnw wrapper — no separate installation neededOptional: GraalVM 21 for native compilation (sub-second startup). Not required for getting started.
Installation
Start HandsAI
Run the service using the Maven wrapper:The service will start on
http://localhost:8080. You’ll see:Register Your First API Tool
Let’s register a real weather API so your LLM can check the weather anywhere in the world.Get a WeatherAPI Key
- Sign up at weatherapi.com (free tier available)
- Copy your API key from the dashboard
Set Up HandsAI Bridge for MCP
To connect HandsAI to your LLM client (Claude Desktop, Antigravity, VS Code, etc.), you need the HandsAI Bridge.Execute Your First Tool
Now test the integration end-to-end.- Via LLM Client
- Via Direct API Call
Ask your LLM:
“What’s the weather in Buenos Aires?”The LLM will:
- Discover the
Get Current Weathertool via MCP - Call the tool with
{"q": "Buenos Aires"} - HandsAI executes the API call to WeatherAPI
- Return the JSON response to the LLM
- The LLM formats the weather data in natural language
“The current weather in Buenos Aires is 15°C (59°F) with partly cloudy skies. Wind is 10 km/h from the east.”
Next Steps
Import More APIs
Check out the pre-built use cases:
- Email sending (Resend)
- Social media posting (Ayrshare)
- AI search (Tavily)
- GitHub automation
docs/casos-de-uso/NUEVOS_HITOS.jsonExplore the Architecture
Learn how HandsAI’s caching, authentication, and execution flow works under the hood.
API Reference
Complete documentation of all admin and MCP endpoints.
Native Compilation
Compile to native executable for < 1.5s startup:
Troubleshooting
Tool not appearing in MCP client
Tool not appearing in MCP client
- Verify the tool is registered:
curl http://localhost:8080/mcp/tools/list - Check that HandsAI is running on port 8080
- Ensure the bridge configuration uses the correct absolute path
- Restart your MCP client after configuration changes
API authentication errors
API authentication errors
- Check that your API key is correct
- Verify
apiKeyLocationmatches the API’s requirements (HEADER, QUERY_PARAMETER, or IN_BODY) - For OAuth2, ensure
isDynamicAuthis enabled with correct token endpoint
Port 8080 already in use
Port 8080 already in use
Change the port in Update the bridge config.json to point to the new port.
application.properties: