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

@zhoujinandrew/mcp-te-server

v1.0.1

Published

MCP proxy server for ThinkingEngine system with automatic authentication

Downloads

184

Readme

@zhoujinandrew/mcp-te-server

MCP proxy server for ThinkingEngine with automatic browser-based authentication.

Automates the login → token extraction → proxy flow so you never need to manually copy tokens.

How It Works

┌─────────────┐    stdio     ┌──────────────────┐     SSE      ┌──────────────┐
│ Claude Code  │ ←─────────→ │  mcp-te-server   │ ←──────────→ │ TE MCP Server│
│  (client)    │             │  (local proxy)    │  mcpToken    │  (remote)    │
└─────────────┘             └──────────────────┘              └──────────────┘
                                     │
                                     │ Auto-authentication
                                     ▼
                             ┌──────────────────┐
                             │  Default Browser  │
                             │  (AppleScript)    │──→ Login → Extract token
                             └──────────────────┘
  1. On startup, checks for cached tokens
  2. If no valid token, opens your default browser for login
  3. Extracts the bearer token from localStorage via AppleScript (macOS)
  4. Exchanges it for an mcpToken via the ThinkingEngine API
  5. Proxies all MCP requests transparently
  6. Auto-reconnects and re-authenticates on token expiry or connection errors

Prerequisites

  • Node.js >= 18
  • macOS with Chrome, Brave, Edge, Arc, or Safari
  • Access to a ThinkingEngine system instance

Installation

Via npx (recommended)

No installation needed — just configure your MCP client directly.

From source

git clone https://github.com/zjandrew/mcp-te-server.git
cd mcp-te-server
npm install
npm run build

Configuration

Claude Code

Add to ~/.claude.json:

{
  "mcpServers": {
    "ThinkingEngine": {
      "command": "npx",
      "args": ["-y", "@zhoujinandrew/mcp-te-server"],
      "env": {
        "TE_BASE_URL": "https://your-te-server.example.com",
        "TE_SSE_URL": "https://your-te-server.example.com:18988/mcp/sse"
      }
    }
  }
}

OpenClaw / Other MCP Clients

Same configuration format — use npx with @zhoujinandrew/mcp-te-server.

Environment Variables

| Variable | Required | Description | |----------|----------|-------------| | TE_BASE_URL | Yes | Base URL of your ThinkingEngine system (e.g., https://your-te-server.example.com) | | TE_SSE_URL | No | Override the MCP SSE endpoint URL. Default: {TE_BASE_URL hostname}:18988/mcp/sse |

From source (alternative)

{
  "mcpServers": {
    "ThinkingEngine": {
      "command": "node",
      "args": ["/path/to/mcp-te-server/dist/index.js"],
      "env": {
        "TE_BASE_URL": "https://your-te-server.example.com",
        "TE_SSE_URL": "https://your-te-server.example.com:18988/mcp/sse"
      }
    }
  }
}

Usage

  1. Configure your MCP client as shown above
  2. Start (or restart) the client
  3. On first launch, your default browser opens — log in to ThinkingEngine
  4. Token is extracted automatically after login
  5. Subsequent launches use cached tokens (no login until expiry)

Token Management

Tokens are cached at ~/.mcp-te-server/token.json.

To clear cached tokens:

rm ~/.mcp-te-server/token.json

Development

npm install
npm run build      # Build
npm run dev        # Watch mode
npm start          # Run directly

License

MIT