Proposal: Official TC39 MCP Server for Proposals, FAQs, and Contribution Guidelines

Summary

I propose that TC39 provide an official Model Context Protocol (MCP) server to make TC39 proposals, FAQs, and contribution guidelines more accessible through AI tools.

Background

Model Context Protocol (MCP) is an open standard that enables AI assistants to securely access data sources. An MCP server would allow developers to query TC39 proposals directly from their AI tools (Claude Desktop, VSCode with AI extensions, etc.) rather than manually browsing documentation.

Proposed Features

An official TC39 MCP server could provide:

1. Proposal Management

   • Search proposals by name, description, champion, or author
   • Filter by stage (-1, 0, 1, 2, 2.7, 3, 4)
   • Get detailed proposal information including specification status
   • Compare proposals side-by-side
   • List proposals by champion

2. FAQ Access

   • Query TC39 frequently asked questions
   • Search FAQ topics
   • Get process-related information

3. Contribution Guides

   • Access "How to Contribute" documentation
   • Understand the proposal process
   • Get meeting participation guidelines

Benefits

• Developer Experience: Developers can query "What TC39 proposals are at Stage 3?" directly in their AI tools
• Discoverability: Makes TC39 work more discoverable to the broader JavaScript community
• Real-time Access: Always up-to-date information sourced from the official dataset
• Standardized Interface: Consistent API for all MCP-compatible tools

Proof of Concept

I've built a working implementation as a proof of concept: https://tc39-mcp.deno.dev

The server currently provides:

• Tools for searching, filtering, and comparing proposals
• Resources for accessing individual proposals and summaries
• Prompts for common queries

GitHub: https://github.com/hemanth/tc39-mcp

Implementation Considerations

• Could be deployed on Deno Deploy, Cloudflare Workers, or similar edge platform (free tier sufficient)
• Would use the existing https://tc39.es/dataset/proposals.json as the data source
• Low maintenance - mostly automated updates from the dataset
• Could integrate with tc39.es authentication if needed for write operations

Related Work

• Model Context Protocol specification: https://modelcontextprotocol.io/
• Anthropic's MCP announcement: https://www.anthropic.com/news/model-context-protocol

Would the TC39 team be interested in maintaining an official MCP server, or alternatively, endorsing/linking to community implementations?

See it in action 👇

https://github.com/user-attachments/assets/b9b72e2b-83f4-4e0a-8501-a2e6a3263579

Review the existing dataset at https://tc39.es/dataset/proposals.json and the linked proof-of-concept implementation to understand the proposed scope. A next step would be deciding whether TC39 wants to maintain or endorse an MCP server, then defining an implementation location, supported features, and acceptance criteria.