MCP: connect Claude (web, Cowork) to a cluster as a custom connector, without the CLI
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
Línea de trabajo
Start by reading the Studio flows that configure clusters and providers; the issue does not name their files or entry points, so locate them in the repository. Verify whether Claude completes OAuth against Harper’s /mcp without a challenge, and decide whether connectors may access the operations part. Done means Studio gives eligible clusters a no-CLI setup path for Claude’s application tools, explains the public-address requirement where relevant, and retains the CLI route for other cases.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Why
#2011 (PR #2096) connects an AI tool through the harper CLI: harper login on the user's machine, then a local bridge in the client's config. That works for engineers. A reviewer who isn't one asked whether they could instead paste the cluster's MCP address into Claude (web or Cowork) as a custom connector. For non-engineers that is the lowest-friction way in, and today it isn't possible. This was left out of #2096 on purpose.
What a connector needs
A Claude custom connector signs in with OAuth against the MCP server itself. Harper's built-in MCP server has no OAuth of its own, but the @harperfast/oauth plugin can act as the authorization server for it:
- With
mcp.enabled: true, on a Harper that hasserver.registerBearerValidator(first tagged in v5.4.0-alpha.1), the plugin registers its token check with Harper, so Harper's own/mcpaccepts the plugin's tokens with no custom route (oauthdocs/mcp-oauth.md"Option A"). - No per-cluster registration with Anthropic. claude.ai identifies itself with a Client ID Metadata Document (
client_id=https://claude.ai/oauth/mcp-oauth-client-metadata, per HarperFast/oauth#199), and the plugin accepts those by default (docs/mcp-oauth.md#L33). - Per-cluster sign-in provider setup is needed. The plugin sends people to a configured provider (GitHub, Google, Okta, …) to log in, and
redirectUrimust be the cluster's public origin plus/oauth/callback(docs/getting-started.md#L27). So each cluster needs a provider app (or a shared one listing each cluster's callback) and its client id and secret. - Each login has to become a Harper user. The token's subject must resolve to an active Harper user with a role, either by provisioning matching users or by mapping identities in an
onLoginhook (docs/mcp-oauth.md#L69-L72).
Gaps found in Harper
- Only the application part can be reached this way. Harper skips the plugin's token check on the operations server (
security/auth.ts#L350:hasActiveValidators = !request.isOperationsServer && …). A connector could use the application part (mcp.application: tables and resources), not the operations part (admin commands). That may be the right limit; it should be a stated decision. - Harper's
/mcpdoesn't challenge. It answers a request with no token as an anonymous session, and its 401 carries noWWW-Authenticate: Bearer resource_metadata=…header (docs/mcp-oauth.md#L73-L79). A client that waits for that challenge before starting OAuth never signs in. Unverified: whether Claude's connector looks up/.well-known/oauth-protected-resourceon its own.
Open questions
- Does Claude's connector complete sign-in against Harper's
/mcptoday (gap 2), or does Harper need to send the challenge? - Should a connector ever reach the operations part (gap 1)?
- Who sets this up on Fabric: a Studio page that configures the plugin and provider per cluster, Fabric provisioning it, or docs only?
- Self-managed clusters: the connector reaches the server from Anthropic's side, not the user's machine, so the address must be public. Verify, and say so where Studio shows it.
Done when
A non-engineer can follow steps in Studio to add a cluster to Claude as a custom connector, sign in through a browser, and use the application part's tools, with no CLI. Studio shows that path only where the cluster can serve it, and keeps the harper login route for everything else.
🤖 Generated by Claude Code (Claude Opus 5.5); posted via @dawsontoth.
Epic: HarperFast/harper#2102 (MCP server & OpenAPI schema generation).
- Lenguaje dominante
- TypeScript
- Estrellas
- 5
- Forks
- 4
- Merge medio
- 2 d 13 h
- PR fusionados (30 d)
- 60
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de HarperFast/studio
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
HarperFast/studio#2111 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
HarperFast/studio#2109 ·
Los mantenedores suelen responder en 1 día
-
rum
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
HarperFast/studio#2085 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
HarperFast/studio#2070 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
HarperFast/studio#2067 ·
Los mantenedores suelen responder en 1 día
Todos los issues de HarperFast/studio
Issues similares
-
bot:ai-assisted component:platform-js status:untriaged
Dificultad 1/5 Menos de una hora Aptitud para principiantes 74/100
midnightntwrk/platform-js#38 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
ranxianglei/billion-context#7068 ·
Los mantenedores suelen responder en 1 día
-
vendor: bump whisper.cpp past 6a8addd — the current pin aborts the app on a failed Metal initAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
mybigday/whisper.rn#348 ·
-
enhancement severity:low
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Battle-Cattle/BCUK-Bot-4#1075 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
ilan-pinto/roaring-lions#1552 ·
Los mantenedores suelen responder en 1 día