npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

byourside-mcp

v0.1.0

Published

MCP server giving AI agents a phone via By Your Side outbound AI calls.

Readme

byourside-mcp

MCP server that gives any MCP client (Claude Desktop, Cursor, etc.) a phone -- place outbound AI calls, poll for results, and list call history via the By Your Side Agent API.

Prerequisites

  • Node 18 or newer
  • A By Your Side agent API key (starts with bys_ak_)

Quick start

cd mcp
npm install
BYOURSIDE_API_KEY=bys_ak_your_key_here npm start

MCP client configuration

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on your OS:

{
  "mcpServers": {
    "byourside": {
      "command": "node",
      "args": ["/absolute/path/to/voip-agent/mcp/src/server.js"],
      "env": { "BYOURSIDE_API_KEY": "bys_ak_your_key_here" }
    }
  }
}

Cursor

Add to .cursor/mcp.json in your project (or the global ~/.cursor/mcp.json):

{
  "mcpServers": {
    "byourside": {
      "command": "node",
      "args": ["/absolute/path/to/voip-agent/mcp/src/server.js"],
      "env": { "BYOURSIDE_API_KEY": "bys_ak_your_key_here" }
    }
  }
}

To point at a staging or self-hosted instance, add "BYOURSIDE_API_BASE": "https://staging.example.com" to the env block.

Tools

place_call

Places an outbound AI phone call toward an objective. Returns a callId immediately; the call runs asynchronously. Poll get_call with that callId until status is terminal.

Inputs:

| Field | Type | Required | Description | |---|---|---|---| | to | string | yes | Destination number in E.164 (e.g. +14155550123) | | objective | string | yes | What the call should accomplish | | context | string | no | Background context for the assistant | | fields | array | no | Structured fields to extract (up to 20 items: { name, type?, description? }) | | webhookUrl | string | no | HTTPS URL to receive the signed result when the call ends | | callerId | string | no | Caller ID override; must be a number on your account |

Returns: { callId, status } where status is queued on success.

get_call

Fetches the current status and result of a call.

Inputs:

| Field | Type | Required | Description | |---|---|---|---| | callId | string | yes | The callId from place_call |

Returns: { id, status, summary, transcript, extracted, recordingUrl, to, objective, startedAt, endedAt, durationSec, error? }

list_calls

Lists recent calls placed by your account (most recent first).

Inputs:

| Field | Type | Required | Description | |---|---|---|---| | limit | number | no | Max calls to return (default 20, max 100) |

Returns: { calls: [ { id, to, objective, status, summary, createdAt, startedAt, endedAt, durationSec, error? } ] }

Call statuses

| Status | Terminal? | Meaning | |---|---|---| | queued | no | Call accepted, not yet dialing | | ringing | no | Dialing the destination | | in_progress | no | Call is live | | completed | yes | Call finished normally | | no_answer | yes | Destination did not pick up | | voicemail | yes | Reached voicemail | | declined | yes | Call was rejected | | failed | yes | Technical failure |

Place your first call

  1. Configure your MCP client as above.
  2. Ask your assistant: "Place a call to +14155550123 with the objective: confirm the meeting time for tomorrow at 2pm."
  3. The assistant calls place_call and gets back a callId.
  4. Ask: "Check on call <callId> -- did it complete?"
  5. The assistant calls get_call and returns the status, summary, and any extracted fields.

Manual end-to-end test

  1. Set BYOURSIDE_API_KEY and optionally BYOURSIDE_API_BASE in your MCP client config.
  2. Configure the client using the JSON above.
  3. Ask your agent to call a number you control with a specific objective and one extraction field (e.g. { name: "confirmed", type: "boolean" }).
  4. Confirm place_call returns a callId.
  5. Call get_call repeatedly until status is terminal; verify extracted.confirmed is present.
  6. Try a blocked destination (e.g. a premium-rate number) and confirm the mapped error message is returned.

Development

Run tests:

cd mcp && node --test

Check server parses:

node --check mcp/src/server.js

Smoke test (missing key, should exit 1):

node mcp/src/server.js

Smoke test (with dummy key, should print "ready on stdio" to stderr):

BYOURSIDE_API_KEY=bys_ak_test node mcp/src/server.js