plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "app-6ab3ad1d96a0819184a4ecefbe03ead0",
  "version": "1.0.1",
  "description": "Give your AI agents real-time access to live customer context from Computer by DevRev: support tickets, conversations, product feedback, and customer health.",
  "author": {
    "name": "DevRev",
    "email": "support@devrev.ai",
    "url": "https://devrev.ai"
  },
  "homepage": "https://devrev.ai",
  "keywords": [
    "devrev",
    "customer support",
    "tickets",
    "issues",
    "enhancements",
    "product feedback",
    "mcp"
  ],
  "extensions": {
    "com.openai": {
      "interface": {
        "displayName": "Computer by DevRev",
        "shortDescription": "Customer context from DevRev",
        "longDescription": "Computer by DevRev brings your DevRev workspace into ChatGPT and Codex through DevRev's remote Model Context Protocol (MCP) server. Ask about customer-reported problems, product feedback, and engineering work without losing the connections between them.\n\nA customer ticket can point to the issue being worked on; an issue can sit under an enhancement; and an enhancement can show how a product change affects customers. The connection helps your AI assistant retrieve that DevRev context, summarize what matters, and identify the next step. Where supported and authorized, it can also help create or update DevRev work items.\n\nWhat you can do:\n- Search and retrieve DevRev work and related customer context from a conversation.\n- Trace customer-reported issues to the engineering work addressing them.\n- Summarize an enhancement's status, linked tickets, and areas needing attention.\n- Create or update supported work items when authorized and available to the signed-in user.\n\nWhy it matters:\n- Context: Understand relationships across customer tickets, issues, and enhancements rather than reading each record in isolation.\n- Action: Move from an answer to a supported DevRev work-item change when the signed-in user has permission.\n- Control: Use the organization's DevRev access boundaries and the client's action-approval controls, where available.\n\nThe connection uses the signed-in user's DevRev access. Available records, tools, and actions depend on the organization's configuration and that user's permissions. A DevRev account and access to the relevant workspace are required. Review any proposed write action before allowing it.",
        "developerName": "DevRev",
        "category": "Productivity",
        "capabilities": [
          "Search tickets and issues",
          "Read work items and context",
          "Trace tickets to engineering work",
          "Summarize enhancements",
          "Create and update work items"
        ],
        "websiteURL": "https://devrev.ai",
        "supportURL": "https://support.devrev.ai/",
        "privacyPolicyURL": "https://devrev.ai/legal/privacy-policy",
        "termsOfServiceURL": "https://devrev.ai/legal/terms-of-service",
        "defaultPrompt": [
          "Which customer tickets are about billing, and which issues are fixing them?",
          "Summarize the Self-serve Billing enhancement and its linked customer reports."
        ],
        "composerIcon": "./assets/icon.svg",
        "logo": "./assets/icon.svg"
      },
      "review": {
        "test_cases": {
          "positive": [
            {
              "description": "Account review: an account manager checks a customer's open support issues before a call.",
              "prompt": "I have a call with Sakura Logistics tomorrow. Do they have any open tickets in DevRev, and how are they feeling?",
              "tools_triggered": "hybrid_search, discover_schema, list_objects",
              "expected_behavior": "Finds the account Sakura Logistics KK and returns one open ticket, TKT-7, \"Invoice for Tokyo office is 100x the expected amount\": severity blocker, sentiment Frustrated."
            },
            {
              "description": "Escalate with a comment: a support agent escalates a known bug by leaving an internal note for engineering.",
              "prompt": "Leave an internal note on the yen invoicing bug in DevRev saying Sakura Logistics is blocked and ask engineering for a fix ETA.",
              "tools_triggered": "hybrid_search, add_comment",
              "expected_behavior": "Finds ISS-24, \"Bug: invoice totals off by rounding when currency is JPY\", and posts an internal comment on it from the signed-in user stating Sakura Logistics KK is blocked and asking for a fix ETA."
            },
            {
              "description": "Move work forward: an engineer starts work on a prioritized bug, using only a valid workflow transition.",
              "prompt": "I'm picking up the Okta logout bug in DevRev, move it into development.",
              "tools_triggered": "hybrid_search, discover_schema, get_valid_stage_transitions, update_object",
              "expected_behavior": "Finds ISS-18, \"Bug: session not invalidated after IdP-initiated logout (SLO)\", confirms In Development is a valid transition from Prioritized, and moves the issue to In Development."
            },
            {
              "description": "Link records: a support agent records that a customer request is waiting on specific engineering work.",
              "prompt": "In DevRev, the Azure AD SSO request from that enterprise prospect can't move until the SSO admin settings page ships. Link the two.",
              "tools_triggered": "hybrid_search, link_objects",
              "expected_behavior": "Finds ticket TKT-6, \"Request: SSO login with Azure AD for our workspace\", and issue ISS-16, \"SSO admin settings UI: IdP metadata upload and test connection\", and creates a link where TKT-6 depends on ISS-16."
            },
            {
              "description": "Create work: an engineer files a new bug under an existing project and assigns it to themselves.",
              "prompt": "File a P2 bug under the SSO project in DevRev: the login page shows no error when the IdP certificate has expired. Assign it to me.",
              "tools_triggered": "hybrid_search, get_self, discover_schema, create_object",
              "expected_behavior": "Finds the Enterprise SSO (SAML 2.0 & OIDC) enhancement and creates an issue under it titled \"SSO login shows no error when IdP certificate has expired\", priority P2, owned by the signed-in user, returning the new issue ID."
            }
          ],
          "negative": [
            {
              "description": "General Stripe question that shares billing and invoice vocabulary with DevRev records but needs no workspace data.",
              "prompt": "How does Stripe handle zero-decimal currencies like JPY when I create an invoice?"
            },
            {
              "description": "Generic SSO setup help for a third-party product; mentions Okta and SAML but involves no DevRev work items.",
              "prompt": "Walk me through setting up SAML SSO between Okta and Google Workspace."
            },
            {
              "description": "Tickets that live in a different system (Jira); the word 'tickets' should not route the request to DevRev.",
              "prompt": "Show me my open Jira tickets in the PAY project that are assigned to me."
            }
          ]
        }
      },
      "publication": {
        "release_notes": "Adds review test cases and listing metadata for the Computer by DevRev MCP connection."
      },
      "apps": "./.app.json"
    }
  }
}