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

@stanley2058/local-reflect-mcp

v1.0.0

Published

This is a simple tool to reflect server side tool calls for multilayer tool calling.

Readme

local-reflect-mcp

This is a simple tool to reflect server side tool calls for multilayer tool calling.

If you are like me and have the following requirement:

  1. You have a server with tools.
  2. You have a client also with tools.
  3. You want to be able to call both client and server tools without shadowing any of them.

On your server you can replace reflect tool calls with the actual tool name to make the model think it's calling the correct tool. Example code using AI-SDK:

type ReflectIOShape = {
  id: string;
  name: string;
  input: unknown;
  output: unknown;
};
function convertServerSideToolCallsWithReflection(
  messages: ModelMessage[],
  reflectionToolName: string,
) {
  const toolResultMap = new Map<string, ReflectIOShape>();
  const output = structuredClone(messages);
  for (let i = 0; i < output.length; i++) {
    const message = output[i]!;
    if (message.role === "assistant") {
      if (typeof message.content === "string") continue;
      for (let j = 0; j < message.content.length; j++) {
        const content = message.content[j]!;
        if (content.type === "tool-call") {
          if (content.toolName !== reflectionToolName) continue;
          const payload = content.input as ReflectIOShape;
          toolResultMap.set(payload.id, payload);

          content.toolName = payload.name;
          content.input = payload.input;
        }
        if (content.type === "tool-result") {
          if (content.output.type !== "text") continue;
          if (content.toolName !== reflectionToolName) continue;

          const payload = toolResultMap.get(content.toolCallId);
          if (!payload) continue;

          content.toolName = payload.name;
          content.output = {
            type: "text",
            value: JSON.stringify(payload.output),
          };
        }
      }
    }

    if (message.role === "tool") {
      for (let j = 0; j < message.content.length; j++) {
        const content = message.content[j]!;

        if (content.output.type !== "text") continue;
        if (content.toolName !== reflectionToolName) continue;
        const payload = toolResultMap.get(content.toolCallId);
        if (!payload) continue;
        content.toolName = payload.name;
        content.output = {
          type: "text",
          value: JSON.stringify(payload.output),
        };
      }
    }
  }
  return output;
}