Changelog
Improved

Connect the MCP server with OAuth, no API key

Claude Code and other MCP clients can now connect to Rendobar's hosted MCP server through a browser sign-in. One command, no key to copy.

API MCP

Rendobar’s hosted MCP server at api.rendobar.com/mcp now completes the full OAuth handshake that MCP clients expect. Point your client at the URL and your browser opens once to approve access. No API key to create, copy, or paste into a config file.

Terminal window
claude mcp add --transport http rendobar https://api.rendobar.com/mcp

What changed under the hood:

  • Unauthenticated requests to /mcp now return the WWW-Authenticate challenge from the MCP authorization spec, so clients discover the sign-in flow on their own.
  • The RFC 9728 resource metadata is served at /.well-known/oauth-protected-resource/mcp, the path derived from the server URL.
  • Every MCP tool now declares a title and read-only, destructive, and idempotent annotations, returns typed structuredContent, and reports failures with one error shape: a stable machine code, a human message, and a retryable flag.

API keys keep working as before, both on the hosted server and in the local @rendobar/mcp package, which remains the way to upload files straight from your disk.

File uploads over the same hosted server landed in upload files to the MCP server.

Share