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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@remoteoss/mcp

v0.1.5

Published

A CLI to run the Remote AI Agent Toolkit MCP server.

Readme

Remote AI Agent Toolkit: Model Context Protocol

The Remote Agent Toolkit supports the Model Context Protocol (MCP).

Getting Started

You don't need to clone this repository to use the toolkit. You can run the MCP server directly using npx.

The server acts as a bridge between an AI agent and the Remote API, allowing the agent to access a suite of tools for interacting with Remote's services.

Requirements

  • Node.js 18+
  • A Remote API key

Usage

To run the MCP server, you can use npx:

npx -y @remoteoss/mcp --api-key=YOUR_REMOTE_API_KEY

Replace YOUR_REMOTE_API_KEY with your actual Remote API key. Alternatively, you can set the REMOTE_API_KEY environment variable.

The server will start and listen for MCP messages on stdin and stdout. All server logs and status messages are printed to stderr.

When the server is running successfully, you'll see:

✅ Remote API MCP Server running on stdio

Tool Configuration

You can control which tools are available by passing the --tools option to the npx command. This is useful for security and for ensuring the agent only has access to the functions it needs for a specific task.

Provide a comma-separated list of tool names. For example, to only allow the agent to list employments and create time off requests, you would run:

npx -y @remoteoss/mcp \
  --api-key=YOUR_REMOTE_API_KEY \
  --tools=list_employments,create_time_off

This enhances security by restricting the capabilities of the agent to only what's necessary.

Advanced Configuration

The server can be configured via command-line arguments or environment variables.

| Argument | Environment Variable | Description | Required | | ---------------- | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | | --api-key | REMOTE_API_KEY | Your Remote API key. | Yes | | --tools | REMOTE_ALLOWED_TOOLS | A comma-separated list of tool names to expose to the agent. If not provided, all available tools are exposed. See the main README for a full list of names. | No | | --api-base-url | REMOTE_API_BASE_URL | The base URL for the Remote API. Defaults to the production URL. | No |

Usage with Claude Desktop

Add the following to your claude_desktop_config.json. See here for more details.

{
  "mcpServers": {
    "remote": {
      "command": "npx",
      "args": ["-y", "@remoteoss/mcp", "--api-key=REMOTE_API_KEY"]
    }
  }
}