1. Conduid
  2. Developer Tools
  3. Toolhouse Community MCP Server Toolhouse
MCP server · Developer Tools

Toolhouse Community MCP Server Toolhouse

Mirror of https://github.com/toolhouse-community/mcp-server-toolhouse

Unclaimed MIT last commit a year ago devtools
47Fair

Scored 4 months ago · breakdown

About Toolhouse Community MCP Server Toolhouse

Toolhouse Community MCP Server Toolhouse is an MCP server published by mcpflow in the Developer Tools category: mirror of https://github.com/toolhouse-community/mcp-server-toolhouse. It has been installed 0 times through Conduid.

Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx toolhouse-community-mcp-server-toolhouse

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about Toolhouse Community MCP Server Toolhouse

Powered by Claude · Grounded in docs

I know everything about Toolhouse Community MCP Server Toolhouse. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

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.

README mirrored from the source repository 4 months ago. The original is authoritative.

Questions

About Toolhouse Community MCP Server Toolhouse

How do I install Toolhouse Community MCP Server Toolhouse?

Run npx toolhouse-community-mcp-server-toolhouse, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Toolhouse Community MCP Server Toolhouse safe to use with an AI agent?

Its trust score is 47 out of 100 (fair). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Toolhouse Community MCP Server Toolhouse still maintained?

The last commit was a year ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.