Skip to content

feat(mcp): Publish MCP server to mcp.so directory #3643

@owenwahlgren

Description

@owenwahlgren

Summary

Publish the Builders Hub MCP server to mcp.so and ensure external clients (Claude Desktop, Cursor) can connect.

Tasks

1. Publish to mcp.so

Submit server with:

  • Name: avalanche-docs
  • Endpoint: https://build.avax.network/api/mcp
  • Tools: avalanche_docs_search, avalanche_docs_fetch, avalanche_docs_list_sections
  • Categories: documentation, blockchain, developer-tools

2. Enable External Access

  • Configure CORS for cross-origin requests
  • Add health check endpoint (GET /api/mcp)
  • Add rate limiting (60 req/min per client)
  • Track external client connections

3. Create Documentation

Add docs page showing how to connect from:

  • Claude Desktop
  • Cursor IDE
  • Other MCP clients

4. Add MCP Manifest

Create /public/mcp-manifest.json for discovery.

Files to Modify

  • app/api/mcp/route.ts - CORS, health check, rate limiting
  • lib/mcp-rate-limit.ts (new) - Rate limiting
  • content/docs/tools/mcp-server.mdx (new) - Integration docs
  • public/mcp-manifest.json (new) - Server manifest

Acceptance Criteria

  • Listed on mcp.so directory
  • CORS configured for external requests
  • Health check returns server status
  • Rate limiting prevents abuse
  • Documentation page created
  • Works with Claude Desktop (tested)
  • Works with Cursor (tested)
  • External connections tracked in PostHog

Target

50 unique external MCP clients within 30 days


Part of AI/MCP Roadmap Phase 1

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions