Reason Marketplace

The plugins you can connect to Reason, the autonomous
software engineer. Each plugin gives Reason's agents the tools of a hosted MCP
server, such as Linear, Sentry, Notion, Stripe, or Supabase, so a session can read
issues, check logs, query a database, or update a ticket while it works.

This repository lists 386 plugins. It is the public catalog of what Reason offers; it holds
no credentials and no code that runs in your workspace.

Connect a plugin in Reason

1. Open Customize → Plugins in Reason
   (reasonmachines.com/customize?tab=plugins).
2. Pick a plugin and select Connect.
3. Sign in with the provider (OAuth), or paste an API key for plugins that use one.

Reason checks the connection before agents use it. A plugin can be connected for
the whole workspace or just for you. Anything not listed here can be added as a
custom MCP server from the same page.

Built into Reason, and not listed here: GitHub (repositories and pull requests),
Slack (work with Reason in Slack), Chrome, and Computer Use.

Layout

.reason-plugin/marketplace.json     every plugin in this repository
plugins/<slug>/.reason-plugin/plugin.json
plugins/<slug>/logo.svg             brand mark, when the plugin has a local one

A plugin manifest looks like this:

{
  "name": "sentry",
  "displayName": "Sentry",
  "description": "…",
  "homepage": "https://sentry.io",
  "docs": "https://docs.sentry.io/product/sentry-mcp/",
  "logo": "https://mcp.sentry.dev/favicon.ico",
  "auth": "oauth",
  "mcpServers": { "sentry": { "url": "https://mcp.sentry.dev/mcp" } }
}

auth is oauth (sign in with the provider), api_key (an ${API_KEY}
placeholder you fill in when connecting), or none (a public server). skills,
when present, links agent skills Reason loads alongside the plugin.

The MCP URLs are the providers' own public endpoints, so they also work in any
MCP client that supports remote Streamable HTTP servers.

Request a plugin

Open an issue with the provider's name and its MCP server URL.

All plugins

License

MIT