Skip to content

Phase 2: MCP host fork and discovery tools #1294

Closed

Description

@neuromechanist

Part of epic #1065. Add the mcp fork to backend/src/services/host-routing.ts with MCP_HOSTNAME env, the mcp.nemar.org and mcp-test.nemar.org routes in wrangler-sccn.toml, and a path mount for the workers.dev fallback. Stand up the MCP server skeleton (initialize, tools/list) and the first two tools: search_datasets wrapping the existing catalog filter and search services, and describe_dataset from the catalog row plus an index summary. Every response carries the provenance envelope from phase 1. One Analytics Engine data point per tool call, tool name as discriminator; the existing rate limiter applies.

Definition of done: tests drive the app through its request entry point with the real D1 helper, per the repo's no-mock rule; both tools work against staging data on mcp-test.

Activity

  1. neuromechanist commented on Sep 8, 2026

    @neuromechanist
    ContributorAuthor

    Delivered by #1323, squash-merged into the epic branch feature/issue-1065-epic-mcp-server as d14a9d5 (a merge into a non-default branch does not auto-close). The mcp host fork, search_datasets, describe_dataset, the ANALYTICS_MCP metrics point, and the workerd smoke script landed; the staging walk-through on mcp-test waits for the epic to reach dev, since the dev worker deploys only from dev. Local wrangler dev --local for the full worker is tracked in #1324.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew feature or enhancement

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions