[staging-devin-ai-integration]

Summary

Plugin descriptions listed facts about the server ("Official X remote MCP server for…", "X's hosted MCP server: …") and some carried full install instructions inline. This rewrites all 227 authored descriptions as one short, action-oriented sentence about what a user can do. The rewrite keeps the old copy's capabilities and figures (e.g. Zapier's 8,000+ apps, Mobbin's 600,000+ screens). It also adds an optional manifest field so the UI can render install requirements as a notice and/or steps.

// plugins/google-drive/.devin-plugin/plugin.json
"description": "Use Google Drive as one unified Google file plugin for search, file organization, sharing, and Google Docs, Google Sheets, and Google Slides workflows",
"shortDescription": "Drive files and document search",
"setup": {
  "notice": "Google does not support automatic client registration. You must provide your own OAuth client credentials.",
  "steps": [
    "In the Google Cloud console, enable the Google Drive API and the Google Drive MCP API",
    "Create an OAuth client (web application)",
    "Add Devin's OAuth callback URL as an authorized redirect URI",
    "Enter the OAuth client ID and secret when installing this server"
  ]
}

• setup is { notice?: string, steps?: string[] }. At least one key is required, values must be non-empty, and no other keys are allowed (scripts/validate.py). Only 23 plugins have it. They are the ones with requirements outside the install form, a field hint, or a connection caveat:

  • Google custom OAuth: gmail, google-calendar, google-drive, google-cloud-monitoring
  • Microsoft 365 Entra app registration
  • dbt setup modes
  • aws-agent-toolkit
  • Elastic 9.2+ Kibana and the Splunk MCP Server app
  • the Dynatrace host format
  • the HubSpot private app
  • Snowflake auth mode
  • slack-remote shared identity and supabase-remote per-user OAuth
  • AngelList entitlements
  • Strix credits
  • vanta-eu/aus regions

  setup doesn't repeat credential placeholders, because the install form already prompts for each one.

• Descriptions are about 60–150 chars, with no trailing period and no "integration" / "MCP server" filler. shortDescription is unchanged. Upstream plugins are untouched.

• Authoring guidance in README.md and .agents/skills/adding-a-plugin/SKILL.md covers the new style and field.

• The webapp change that carries setup through the catalog and renders it ships separately in devin-webapp. Until then, the field is ignored.

python3 scripts/validate.py → ok: 230 entries (227 authored, 3 upstream)

Release notes

Plugin descriptions in the marketplace are shorter and focus on what each connection lets you do. Setup requirements (e.g. bringing your own Google OAuth client) will show as separate setup steps.

Link to Devin session: https://staging.itsdev.in/sessions/986a645b5a794823a40f4d6c5a4957df
Open in Devin Desktop: https://staging.itsdev.in/desktop/session/986a645b5a794823a40f4d6c5a4957df?variant=devin-insiders
Requested by: @bwhuffman

---

Note

Devin errored when opening this Pull Request as bwhuffman.
As a fallback, Devin opened this PR as itself.

---

Devin Review

Status	Commit
⚪ Not started	—

Run Devin Review

Enable auto-review to review your pull requests automatically.

[staging-devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring

---

Original prompt from Bennett

i want you to revise the long descriptions for each of the plugins/MCPs to be more concise and action-oriented. It should describe what a user gets from the connection rather than just facts about the plugin, and communicate the real value. It looks like for some plugins we also bundle instructions for how to install the plugin, and that should be separated into a different field we can render appropriately as a notice or steps.

Take google drive for example:

Google Drive (current): Official Google Drive remote MCP server for searching, reading, and creating files in Drive. Google does not support automatic client registration, so you must provide your own OAuth client credentials: in the Google Cloud console, enable the Google Drive API and the Google Drive MCP API, create an OAuth client (web application), and add Devin's OAuth callback URL (https://api.devin.ai/mcp/oauth/callback, or the equivalent for your Devin environment) as an authorized redirect URI. Then enter the OAuth client ID and secret when installing this server.

What we want is something like chatgpt's approach

1. short_description: Drive, docs, sheets or slides

2. description: Use Google Drive as one unified Google file plugin for search, file organization, sharing, and Google Docs, Google Sheets, and Google Slides workflows

3. extra requirements: Google does not support automatic client registration. You must provide your own OAuth client credentials.

• In the Google Cloud console, enable the Google Drive API and the Google Drive MCP API
• Create an OAuth client (web application)
• Add Devin's OAuth callback URL as an authorized redirect URI
• Enter the OAuth client ID and secret when installing this server