hitch-rails

by tylerkloseio.github.tylerklose/hitch-railsv0.5.0

Hitch lets MCP clients -- Claude, ChatGPT, Cursor -- call your Rails app's tools as a specific signed-in user, with access you can revoke. You do not stand up a separate auth server, add Redis, or adopt a new sign-in system. Hitch uses the authentication your app already has (current_user or Current.user) and your configured cache store. Underneath it is a full OAuth 2.1 authorization server implementing the MCP 2026-07-28 authorization profile: PKCE (S256), audience-bound tokens (RFC 8707), discovery metadata (RFC 8414 + RFC 9728), revocation (RFC 7009), Client ID Metadata Documents, and optional Dynamic Client Registration (RFC 7591). It adds an authenticated /mcp endpoint backed by the official Ruby MCP SDK and a deny-default tool registry with schema validation and size caps. SQLite and PostgreSQL supported.

No known advisories
MIT

Uptime

Not checked. It lists no endpoint our checks can reach: https on port 443 or 8443.

How we check

This server lists no remote endpoint or package we can write a config for yet.

For agents: the install prompt

Every step above as one Markdown text, for an assistant installing it for you.

# Install the MCP server hitch-rails (`io.github.tylerklose/hitch-rails`)

Its page: https://plug.directory/servers/io.github.tylerklose/hitch-rails

plug.directory has no install config for this server: its listing names no remote endpoint and no package that starts over stdio from npm, PyPI or an OCI registry. Read the install steps in its own repository instead.

Known advisories

None known for its packages.

Checked 2026-10-28 against OSV.dev and deps.dev.

From RubyGems. Report a problem