Skip to content

vaults: implement MCP OAuth credential validation #51

@hrhrng

Description

@hrhrng

Background

`apps/main/src/routes/vaults.ts:278` returns 501:

"MCP OAuth credential validation not yet implemented on this server"

The OAuth refresh + introspection logic lives in `apps/integrations/`, but main worker needs to RPC into it to validate stored credentials before exposing them as session-bound vault entries.

Work

  • Define a service-binding RPC contract on integrations worker: `POST /internal/mcp_oauth_validate { credential_id }` → `{ valid: bool, expires_at? }`
  • Wire the binding from main → integrations
  • Replace the 501 stub with a forward + envelope wrap

Why deferred from #PR

Cross-worker change, requires extending the integrations worker's internal API. Not part of AMA wire alignment.

References

`apps/main/src/routes/vaults.ts:272-285`

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions