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
Configuration
Setup Environment Variables
-
Toolhouse API Key: You need a Toolhouse API Key to access the Toolhouse platform.
- Sign up at Toolhouse and create an account, it's FREE to get started.
- Obtain your API key from the Toolhouse dashboard.
-
Toolhouse Bundle: You need to create a bundle, essentially a group of tools you can assemble from the ones available on the Toolhouse platform.
- Navigate to Toolhouse Bundles and create a bundle with any name i.e.
mcp-toolhouse - Add the tools that you want to use on your client i.e. Scrape the web, Memory, Send Email
- Ensure your bundle looks good (it auto saves)
- Navigate to Toolhouse Bundles and create a bundle with any name i.e.
-
(Optional) Set these environment variables if you prefer not having them in the configuration:
export TOOLHOUSE_API_KEY="your_toolhouse_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.json
On Windows:
%APPDATA%/Claude/claude_desktop_config.json
Modify the configuration file to look like this:
With UVX
{
"mcpServers": {
"mcp-server-toolhouse": {
"command": "uvx",
"args": ["mcp-server-toolhouse"],
"env": {
"TOOLHOUSE_API_KEY": "your_toolhouse_api_key",
"TOOLHOUSE_BUNDLE_NAME": "a_bundle_name"
}
}
}
}
With UV
{
"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",
"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.git
Add this tool as an MCP server.
On MacOS:
~/Library/Application\ Support/Claude/claude_desktop_config.json
On Windows:
%APPDATA%/Claude/claude_desktop_config.json
Modify 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",
"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-mcp
The Inspector will display a URL to access debugging tools in your browser.
Metadata
Release files for mcp-server-toolhouse 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mcp_server_toolhouse-0.2.0.tar.gz | 57.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_server_toolhouse-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 63.2 kB
Release files / mcp_server_toolhouse-0.2.0.tar.gz
| Download URL | mcp_server_toolhouse-0.2.0.tar.gz |
|---|---|
| Size | 57.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a116cab198c68b0c46a30dbc4cafd356942d7b7480a63f2f60cd41312bb5373e
|
|
BLAKE2b-256 checksum How to use checksums |
8a431771d18b06242b628b05d94dabffe5d00a842b9a10165a679f2e50ec6ea4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.11
|
Release files / mcp_server_toolhouse-0.2.0-py3-none-any.whl
| Download URL | mcp_server_toolhouse-0.2.0-py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6c720aa3232633e538b0e6c59f86ada7364b48622e7ba47951b515cefb47d273
|
|
BLAKE2b-256 checksum How to use checksums |
40628bb805ecffbe321482b9cbc1c1990704631ce9ce9a75e9d3246cd1edeb95
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.11
|
Security for mcp-server-toolhouse 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.