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

@arcturn/mcp

v0.1.0

Published

Model Context Protocol client bridge for the Arcturn agent harness Internal to the arcturn CLI; API may change in any release.

Readme

@arcturn/mcp

Internal to the arcturn CLI. Published so arcturn resolves; its API may change in any release without a major version bump. Embedders should depend on @arcturn/core and @arcturn/ai, whose surfaces are the ones the SDK documents.

Model Context Protocol client bridge for the Arcturn agent harness. McpManager connects to a set of configured servers and bridges their tools into ordinary Tool[] from @arcturn/types — the model sees no difference between an MCP tool and a built-in one.

What's in it

src/index.ts exports:

  • McpManager, McpManagerOptions — connects to configured servers, exposes .tools(), .status(), .connect(), .close(), and change events (McpToolsChangedEvent, McpResourcesChangedEvent, McpPromptsChangedEvent, McpResourceUpdatedEvent).
  • loadMcpConfig, McpConfigError — reads and validates an MCP config file.
  • McpToolBridge, mcpToolFullName, sanitizeMcpName, toolResultFromMcp — the lower-level bridge from an MCP tool definition to a Tool.
  • listResources, readResource, listPrompts, getPrompt, listResourceTemplates — the rest of MCP beyond tools.
  • OAuth support: McpOAuthProvider, createMcpOAuthState, McpAuthRequiredError, isMcpAuthRequiredError, MemoryMcpOAuthStorage, DEFAULT_MCP_REDIRECT_URL.

Install

Arcturn is not yet published to npm. Until it is, use it from a clone of the monorepo as a pnpm workspace package:

git clone https://github.com/sitharaj88/arcturn.git && cd arcturn
pnpm install && pnpm -r build

Then depend on it from another workspace package: "@arcturn/mcp": "workspace:*".

Usage

import { loadMcpConfig, McpManager } from "@arcturn/mcp";
import { createAgent } from "@arcturn/core";

const config = await loadMcpConfig([".arcturn/mcp.json"]);
const manager = new McpManager(config);
await manager.connect(); // connects every configured server concurrently

const mcpTools = manager.tools(); // Tool[] — concatenate with your other tools
const agent = createAgent({ /* ...base options */ tools: [...mcpTools] });

manager.onToolsChanged((event) => {
  // A server's tool list changed live — rebuild the agent's tool set to match.
  agent.setTools([...mcpTools, ...manager.tools()]);
});

Per-server failures are isolated — one bad server never prevents the others from connecting. manager.status() reports each server's connection state ("disconnected" | "connecting" | "connected" | "failed") plus a toolCount or error. Call manager.close() to tear every connection down.

Docs

License

Apache-2.0 — see LICENSE.


👤 Author

Sitharaj Seenivasan

☕ Support

If this project helps you, consider buying me a coffee — it keeps the work going.

Buy Me A Coffee

📄 License

Licensed under the Apache License 2.0. © 2026 Sitharaj Seenivasan.