Local MCP server/Development

Hfspace MCP server

Local MCP server

Hfspace is a local stdio MCP server that connects Claude Desktop to Hugging Face Spaces for image generation, vision models, text-to-speech, and other Space capabilities. Install it with npx -y @llmindset/mcp-hfspace in claude_desktop_config.json, then pass Space names and optional flags such as --work-dir and --hf-token. It requires Claude Desktop 0.78 or newer and Node.js. The hf.co/mcp service belongs to Hugging Face's own MCP server and is a separate product, not this package.

none for public Spaces; optional Hugging Face token for gated Spaces Source checked Nov 12, 2026 Local install path Reviewed 2026-11-16
About

Where it fits

Developers and creators using Claude Desktop who want to attach specific Hugging Face Spaces locally.

  • Generate an image through a selected Space.
  • Run a vision model on a local image.
  • Convert text to speech with a Space model.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Local stdio server for Claude Desktop

Add this as a command in claude_desktop_config.json with the Space names you want. Optional flags include --work-dir and --hf-token. Requires Claude Desktop 0.78 or newer and Node.js.

  1. Edit the Claude Desktop config

    In claude_desktop_config.json, add an mcpServers entry with command npx and args ["-y", "@llmindset/mcp-hfspace"], followed by the Space names or flags you need.

    npx -y @llmindset/mcp-hfspace
  2. Add optional flags

    Pass --work-dir for a shared file directory and --hf-token if a Space needs Hugging Face authentication.

  3. Restart Claude Desktop

    Quit and reopen Claude Desktop, then confirm the Hfspace tools appear.

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • The client cannot find the vomo command. Confirm the global CLI install and that the executable is on PATH.
  • The process starts but no tools appear. Sign in to the provider CLI, restart the client, and check the local command output for errors.
Safety

Before you connect

Local process, your machine
  • The MCP server process runs on your machine, not on a provider host.
  • Data leaves only through the model provider and any MCP servers you attach.
  • Review the local command, package, and files it can reach before running it.
  • Stop the process or remove the client entry when you no longer need it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Hfspace repositoryhttps://github.com/evalstate/mcp-hfspace