Skip to main content
Glama
zjandrew

mcp-te-server

by zjandrew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

@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

Related MCP server: MCP OAuth Gateway

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@latest"],
      "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@latest.

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

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers