Toolhouse MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Toolhouse MCP Serverscrape the content of example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Toolhouse MCP Server
This MCP server allows you to connect MCP clients with Toolhouse's tools. Built on top of Toolhouse and Groq's API - for fast inference.
The Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. Whether you’re building an AI-powered IDE, enhancing a chat interface, or creating custom AI workflows, MCP provides a standardized way to connect LLMs with the context they need.
Features
Allows compatible MCP Clients (i.e Claude Desktop App) to access a vast library of tools to enhance their capabilities
Related MCP server: MCP360 Universal Gateway
Configuration
Getting API Keys
Toolhouse API Key:
Sign up at Toolhouse and create an account.
Obtain your API key from the Toolhouse dashboard.
Groq API Key:
Sign up at Groq if you don’t already have an account.
Get your API key from the API console.
Toolhouse Bundle:
Navigate to Toolhouse Bundles and create a bundle with a name i.e.
mcp-toolhouseAdd the tools that you want to use on your client i.e. Scrape the web, Memory, Send Email
Save the bundle
(Optional) Set these environment variables if you prefer not having them in the configuration:
export TOOLHOUSE_API_KEY="your_toolhouse_api_key" export GROQ_API_KEY="your_groq_api_key" export TOOLHOUSE_BUNDLE_NAME="your_bundle_name"
Starting the server
Add this server to your client's configuration.
For example on Claude's desktop app navigate to the folder and manually change the settings file called claude_desktop_config.json
On MacOS:
~/Library/Application\ Support/Claude/claude_desktop_config.jsonOn Windows:
%APPDATA%/Claude/claude_desktop_config.jsonModify the configuration file to look like this:
{
"mcpServers": {
"mcp-server-toolhouse": {
"command": "uv",
"args": [
"--directory",
"/path/to/this/folder/mcp-server-toolhouse",
"run",
"mcp-server-toolhouse"
],
"env": {
"TOOLHOUSE_API_KEY": "your_toolhouse_api_key",
"GROQ_API_KEY": "your_groq_api_key",
"TOOLHOUSE_BUNDLE_NAME": "a_bundle_name"
}
}
}
}Run this project locally
This project is not yet configured for ephemeral environments like uvx. Run the project locally by cloning the repository:
git clone https://github.com/toolhouse-community/mcp-server-toolhouse.gitAdd this tool as an MCP server.
On MacOS:
~/Library/Application\ Support/Claude/claude_desktop_config.jsonOn Windows:
%APPDATA%/Claude/claude_desktop_config.jsonModify the configuration file to include:
"toolhouse": {
"command": "uv",
"args": [
"--directory",
"/path/to/this/repo/",
"run",
"mcp-server-toolhouse"
],
"env": {
"TOOLHOUSE_API_KEY": "your_toolhouse_api_key",
"GROQ_API_KEY": "your_groq_api_key",
"TOOLHOUSE_BUNDLE_NAME": "a_bundle_name"
}
}TODO
Future improvements include:
Adding test coverage for all modules
Extending API support for enhanced tool configurations
Debugging
Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, use the MCP Inspector.
Launch the Inspector via npm:
npx @modelcontextprotocol/inspector uv --directory /path/to/toolhouse_mcp run toolhouse-mcpThe Inspector will display a URL to access debugging tools in your browser.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/prompted365/mcp-server-toolhouse'
If you have feedback or need assistance with the MCP directory API, please join our Discord server