---
title: "Mcp Get"
method: GET
path: "/mcp/{owner}/{name}"
tags: ["mcp"]
---

# Mcp Get

`GET /mcp/{owner}/{name}`

GET on the MCP endpoint — 405, because we offer no SSE stream here.

A Streamable HTTP client may GET the endpoint to open an SSE channel
for server-initiated messages. We never push any, and 405 with an
``Allow`` header is the transport's answer for "no stream at this
endpoint" — the one response a conforming client treats as final.

This used to return a friendly 200 with a JSON hint, which is what a
client sees as "the stream died": it reconnected forever. In July
2026 that loop was 80% of all production requests (~600k/day from
six clients, zero successful tool calls). The hint survives in the
405 body, so a curl probe still learns the right method.

## Path parameters

- `owner` string, required
- `name` string, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/repowise/apis/repowise-hosted-api.md) · [All operations](https://skmtc.dev/repowise/apis/repowise-hosted-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/repowise/repowise-hosted-api/revisions/1e57283a9737/schema)