Other · Local MCP server

Handset

A business phone system for AI agents: send texts, place calls, read transcripts, buy numbers.

Visit Handset's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.handset-hq/handset
Version
0.1.1
Status
Active
Category
other
Transport
stdio (local process)
Package
npm
Published
2026-08-18
Updated
2026-08-18
Publisher
handset-hq (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/handset-hq) · how
Website
docs.handset.dev/ai.html
Repository
github.com/handset-hq/handset-ui
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
npm@handset/mcp0.1.1stdioHANDSET_API_KEY (required, secret), HANDSET_ALLOW_LIVE

How to connect Handset

Handset runs locally from a Node.js package published to the npm registry: @handset/mcp version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @handset/mcp@0.1.1. It reads these environment variables: HANDSET_API_KEY (required, secret) and HANDSET_ALLOW_LIVE; set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "handset": {
      "command": "npx",
      "args": [
        "-y",
        "@handset/mcp@0.1.1"
      ],
      "env": {
        "HANDSET_API_KEY": "<secret>",
        "HANDSET_ALLOW_LIVE": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More other servers

All 8,395 →
ServerRunsEndpoint or package
Handoff - shareable agent result pages + human-in-the-loop approval gatesFollowable agent result pages + human-in-the-loop yes/no approval gates before irreversible actions.Remote · HTTPhandoff.notdown-app.workers.dev
Handoff MCP ServerDurable agent-to-agent handoffs and shared scratchpad for multi-agent workflows.Remote · HTTPLive check: sign-in requiredhandoff-mcp-server-production.mcp.xpay.sh
HandoverShared, versioned context that humans and AI agents can publish, review, annotate, and continue.Remote · HTTPLive check: ✓ handshakehandover.sh
Hands for AgentsHuman-operated physical world in the EU: make, assemble, measure, verify, ship.Remote & Local · HTTP, stdioLive check: ✓ handshakemcp.handsforagents.com
HANRIA agent mandate checkCheck an agent action against its operator's mandate before acting: permit, deny or escalate.Remote · HTTPLive check: ✓ handshakecheck.hanria.ai
HAPI MCP ServerHAPI MCP server: Dynamically exposes OpenAPI REST APIs as MCP tools for AI assistants.Remote & Local · HTTP
HAPI Strava MCP ServerStrava MCP tools for AI: athletes, activities, segments, clubs, routes. Powered by HAPI MCP server.Remote · HTTPLive check: ✓ handshakestrava.run.mcp.com.ai
Har Forensics MCPTells you what leaked in a.har capture, who's on the page, and what to strip. No network calls.Local · stdionpm: har-forensics-mcp