Toolhouse MCP Server

GitHub
Python
MIT
3
  • Apple
-
security - not tested
A
license - permissive license (MIT)
-
quality - not tested

This MCP server allows you to connect MCP clients with Toolhouse's tools.

  1. Tools
  2. Prompts
  3. Resources
  4. Server Configuration
  5. README.md

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Tools

Functions exposed to the LLM to take actions

NameDescription

No tools

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GROQ_API_KEYYesYour Groq API key obtained from the API console.
TOOLHOUSE_API_KEYYesYour Toolhouse API key obtained from the Toolhouse dashboard.
TOOLHOUSE_BUNDLE_NAMEYesThe name of your Toolhouse bundle.
Need Help?View Source CodeReport Issue
README.md

Toolhouse MCP Server

Toolhouse MCP Server implementation

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

Getting API Keys

  1. Toolhouse API Key:
    • Sign up at Toolhouse and create an account.
    • Obtain your API key from the Toolhouse dashboard.
  2. Groq API Key:
    • Sign up at Groq if you don’t already have an account.
    • Get your API key from the API console.
  3. Toolhouse Bundle:
    • Navigate to Toolhouse Bundles and create a bundle with a name i.e. mcp-toolhouse
    • Add the tools that you want to use on your client i.e. Scrape the web, Memory, Send Email
    • Save the bundle
  4. (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.json

On Windows:

%APPDATA%/Claude/claude_desktop_config.json

Modify 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.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", "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-mcp

The Inspector will display a URL to access debugging tools in your browser.

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues with dependencies of the server.
  • Extract server characteristics such as tools, resources, prompts, and required parameters.

Our directory badge helps users to quickly asses that the MCP server is safe, server capabilities, and instructions for installing the server.

Copy the following code to your README.md file:

Alternative MCP servers

  • zendesk-mcp-server

    -
    security
    F
    license
    -
    quality
    This server provides a comprehensive integration with Zendesk. Retrieving and managing tickets and comments. Ticket analyzes and response drafting. Access to help center articles as knowledge base.

  • jira-mcp-server

    -
    security
    -
    license
    -
    quality
    Tools for executing JQL queries. Tools for creating, editing, and deleting Jira tickets. Tools for listing Jira projects and statuses
    • Apple

  • airtable-mcp-server

    A
    security
    A
    license
    A
    quality
    A Model Context Protocol server that provides read and write access to Airtable databases. This server enables LLMs to inspect database schemas, then read and write records.
    MIT

  • mcp-atlassian

    A
    security
    A
    license
    A
    quality
    Model Context Protocol (MCP) server for Atlassian Cloud products (Confluence and Jira). This integration is designed specifically for Atlassian Cloud instances and does not support Atlassian Server or Data Center deployments.
    MIT