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

@spekoai/mcp

v1.0.8

Published

Local stdio bridge for the hosted SpekoAI MCP server

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

abdikabdikabat_spekoabat_speko

Keywords

spekospekoaimcpstdiovoice-ai

Readme

@spekoai/mcp

Interactive installer and local stdio-to-remote bridge for Speko MCP. The installer configures Speko's hosted remote MCP endpoint in coding tools that support it. The bridge command is only for MCP clients that require a local stdio command: it speaks stdio to the client, connects to Speko's hosted MCP server over HTTP, and does not contain Speko tool logic of its own.

Install

npx @spekoai/mcp@latest init

The package exposes the spekoai-mcp binary. Run init for a guided setup wizard that can configure Claude Code, Codex, OpenCode, Cursor, and generic MCP clients.

For scripted setup, pass the choices explicitly:

npx @spekoai/mcp@latest init --auth oauth --tools claude,codex --scope user --yes

Bridge

Most users should run init. Use bridge only when a client cannot connect to remote MCP directly and asks for a local command-based MCP server.

npx @spekoai/mcp@latest bridge

For API-key auth in a headless bridge setup, provide SPEKO_API_KEY in the MCP client environment. The bridge forwards it to the hosted MCP server as Authorization: Bearer ....

The bridge command adapts local stdio MCP to Speko's remote HTTP MCP endpoint. Use direct remote MCP configuration instead when your client supports it.

Defaults:

  • Endpoint: https://mcp.speko.ai/mcp

Environment variables:

  • SPEKO_API_KEY: forward an API key as a bearer token.

CLI examples:

npx @spekoai/mcp@latest bridge
SPEKO_API_KEY=sk_live_xxx npx @spekoai/mcp@latest bridge

All remaining arguments are passed through to mcp-remote.

Troubleshooting

Run:

npx @spekoai/mcp@latest bridge --help

When using bridge, OAuth state is handled by mcp-remote. It may create a local OAuth cache directory, or use MCP_REMOTE_CONFIG_DIR to store local OAuth credentials and debug logs. The init wizard does not write that directory.

For connection or OAuth issues, pass --debug and inspect the log path printed by mcp-remote.