Where to Find TypeScript/JavaScript MCP Servers: The Complete Curated Guide

The awesome-mcp-servers repository catalogs every TypeScript/JavaScript MCP server implementation under the 📇 emoji marker in its main README.md file.

The punkpeye/awesome-mcp-servers repository serves as the definitive curated index for Model Context Protocol (MCP) implementations. For developers specifically seeking TypeScript/JavaScript MCP servers, the repository employs a consistent visual tagging system that makes discovery immediate and programmatically accessible.

Identifying TypeScript/JavaScript Servers in the README

Every entry in the "Server Implementations" section that includes the 📇 emoji denotes a server written in TypeScript or JavaScript. This convention appears starting at line 51 in README.md, where the legend explains that 📇 represents the TypeScript/JavaScript ecosystem.

When browsing the repository, look for bullet entries formatted as:

- **username/repo-name** – Description 📇 [Link]

This emoji-based categorization allows both manual browsing and automated parsing. The 📇 marker consistently appears before the GitHub repository link, making it possible to filter the entire list programmatically.

Notable TypeScript/JavaScript MCP Servers

The repository contains dozens of production-ready TS/JS servers. Below are prominent examples from the curated list, each installable via npx:

• Correctover/mcp-server – Contract validation and self-healing failover for LLM APIs featuring 6-dimensional verification and 87 auto-healing rules. Install with npx -y correctover-mcp-server.
• forgemeshlabs/coinopai-mcp – Local stdio server for crypto intelligence with pre-flight checks and x402 payment audit tools. Run via npx -y coinopai-mcp.
• 1mcp/agent – Unified MCP aggregator that combines multiple servers into a single endpoint, supporting both cloud and local deployments. Launch with npx -y 1mcp-agent.
• 2s-io/sdk – Unified API providing 180+ tools including geocoding, weather, and finance utilities. Install using npm i @2sio/mcp then npx -y @2sio/mcp.
• aidevelopers2/remoteopenclaw-mcp – CLI and stdio server enabling search across 13,000+ MCP servers from the command line. Execute npx remoteopenclaw search <query>.
• depwire/depwire – Dependency-graph analysis server that parses TypeScript/JavaScript codebases to expose graph-analysis capabilities. Install via npm i depwire.

Additional specialized servers include adw0rd/awesome-mcp-tools-mcp (line 165) for catalog searching, glima-ai/gliana-mcp (line 177) for pay-per-call AI model access, and gpu-bridge/mcp-server (line 178) for unified GPU inference APIs.

Automated Discovery Using Node.js

You can programmatically extract all TypeScript/JavaScript MCP servers by parsing README.md for the 📇 emoji. The following Node.js script (v18+) fetches the raw README and filters for TS/JS entries:

// list-ts-js-mcp.js
import https from 'https';
import { createInterface } from 'readline';

const README_URL =
  'https://raw.githubusercontent.com/punkpeye/awesome-mcp-servers/main/README.md';

https.get(README_URL, (res) => {
  const rl = createInterface({ input: res });
  rl.on('line', (line) => {
    if (line.includes('📇')) {
      // Extract the first markdown link in the line
      const match = line.match(/\[([^\]]+)\]\((https?:\/\/[^)]+)\)/);
      if (match) {
        const [, name, url] = match;
        console.log(`${name} → ${url}`);
      }
    }
  });
});

Execute the script:

node list-ts-js-mcp.js

This outputs repository names and URLs for every TypeScript/JavaScript MCP server listed in the catalog.

Installing and Calling TS/JS MCP Servers

Most TypeScript/JavaScript MCP servers in the repository follow a standard execution pattern using npx. For example, to start the Correctover server:

# Install and run the server (launches local HTTP MCP endpoint)

npx -y correctover-mcp-server &

Once running, interact with the server using a standard MCP client. The following example demonstrates calling a tool from a TypeScript/JavaScript server:

// client.js – minimal MCP client using fetch
import fetch from 'node-fetch';

async function callTool(serverUrl, toolName, args = {}) {
  const resp = await fetch(`${serverUrl}/call`, {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({ tool: toolName, args }),
  });
  const json = await resp.json();
  console.log('Result:', json);
}

// Example: invoke a validation tool
callTool('http://localhost:3000', 'contractValidate', { contract: '...' });

Run the client with node client.js. This pattern works with any TS/JS MCP server implementing the standard MCP HTTP schema (POST /call with tool and args parameters).

Key Repository Files for Developers

Understanding the repository structure helps locate TypeScript/JavaScript servers efficiently:

• README.md – The central source of truth containing all server entries, categorized by the 📇 emoji. This file drives the discovery process.
• CONTRIBUTING.md – Specifies guidelines for adding new MCP servers, including the requirement to tag TypeScript/JavaScript entries with the 📇 emoji and required metadata format.
• LICENSE – MIT license covering the curated list, clarifying permissions for commercial and personal use.
• README-zh.md, README-ja.md, etc. – Localized versions of the main index that maintain the same 📇 tagging convention for international developers.

Summary

• The punkpeye/awesome-mcp-servers repository uses the 📇 emoji to identify every TypeScript/JavaScript MCP server.
• Entries appear in README.md starting at line 51, with full server implementations listed throughout the "Server Implementations" section.
• Install most TS/JS servers immediately using npx -y <package-name> without local cloning.
• Parse the README programmatically by filtering for the 📇 Unicode character to build automated discovery tools.
• Key files include README.md for discovery, CONTRIBUTING.md for submission guidelines, and localized READMEs for non-English documentation.

Frequently Asked Questions

How do I know if an MCP server is written in TypeScript or JavaScript?

Look for the 📇 emoji next to the repository name in the awesome-mcp-servers README. According to the repository's legend at line 51, this emoji specifically denotes the TypeScript/JavaScript ecosystem. Entries without this emoji are implemented in other languages like Python (🐍) or Go (💨).

Can I run these servers without installing them permanently?

Yes. Most TypeScript/JavaScript MCP servers in the catalog support execution via npx, which downloads and runs the package temporarily without permanent installation. For example, npx -y correctover-mcp-server launches the server immediately without adding it to your global node_modules.

How do I add my own TypeScript MCP server to the list?

Submit a pull request to the punkpeye/awesome-mcp-servers repository following the format outlined in CONTRIBUTING.md. You must include the 📇 emoji in your entry to indicate TypeScript/JavaScript implementation, along with a brief description, installation command, and link to your repository.

Are the TypeScript/JavaScript servers compatible with all MCP clients?

Generally yes. TS/JS servers in the repository implement the standard Model Context Protocol specification, exposing tools via HTTP POST endpoints or stdio interfaces. As long as your client follows the MCP schema (sending JSON payloads with tool and args parameters), these servers will respond correctly regardless of the client's own implementation language.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}