← Files PerdooARCHIVED FILE
plugin.json
6.61 KB · Nov 15, 2026 · 07:29 UTC
{
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
"name": "perdoo",
"version": "3.0.1",
"description": "Read and manage Perdoo OKRs, KPIs, and progress from ChatGPT.",
"author": {
"name": "Perdoo GmbH"
},
"extensions": {
"com.openai": {
"interface": {
"category": "Business & Operations",
"defaultPrompt": [
"Which OKRs are currently at risk?"
],
"developerName": "Perdoo GmbH",
"displayName": "Perdoo",
"longDescription": "Bring your strategy into the AI era with the Perdoo MCP server. This connector allows your AI agents and assistants to interact directly with your company\u2019s OKRs, KPIs, and strategic goals, bridging the gap between your high-level mission and everyday AI workflows.",
"privacyPolicyURL": "https://www.perdoo.com/legal/privacy",
"shortDescription": "Connect your goals to agents",
"termsOfServiceURL": "https://www.perdoo.com/legal/terms",
"websiteURL": "https://www.perdoo.com",
"supportURL": "https://support.perdoo.com/en/articles/14470891-mcp-server",
"logo": "./assets/perdoo.png",
"composerIcon": "./assets/perdoo.png"
},
"review": {
"test_cases": {
"positive": [
{
"description": "Retrieve company-level workspace context. Sign in with the dedicated reviewer account and its sample workspace.",
"prompt": "What company am I signed into, and what OKR framework settings are enabled?",
"tools_triggered": "get_company",
"expected_behavior": "Call get_company. Report the company name and returned workspace settings, including country, timezone, OKR framework, KPI and strategic pillar settings, and check-in frequency where returned. Distinguish missing fields from disabled settings. Do not invent configuration or change data."
},
{
"description": "Inspect team ownership. The reviewer workspace must contain a visible team named Engineering with a lead, members, and any sample sub-teams.",
"prompt": "Who leads the \"Engineering\" team, and who are its members and sub-teams?",
"tools_triggered": "list_teams, get_team; list_users or list_teams for additional pages when needed",
"expected_behavior": "Resolve Engineering using list_teams with name=Engineering, clarifying duplicate matches. Call get_team with the returned ID. Report the returned lead, members, and sub-teams. If embedded member or sub-team results are truncated, disclose that limitation or retrieve further results using the advertised pagination and filters. Each user in a list_users response must contain only id, firstName, lastName, and isActive. Do not infer missing memberships or change data."
},
{
"description": "Retrieve recent user activity. The reviewer must have at least one sample progress update linked to a goal, key result, or KPI.",
"prompt": "Show my most recent progress update and the key result, KPI, or goal it belongs to.",
"tools_triggered": "get_me, list_updates",
"expected_behavior": "Resolve the signed-in user with get_me. Its raw tool response must contain only the user's id, firstName, lastName, and isActive. Call list_updates with userId equal to that ID. Follow pageInfo pagination as needed to identify the latest returned commitDate; do not assume the first result is newest. Report the date, returned value/status, and linked entity name and ID. If no update is visible, say so without inventing one."
},
{
"description": "Inspect a named KPI. The reviewer workspace must contain a visible KPI named Monthly Recurring Revenue (MRR), with a current value, lead, and team associations.",
"prompt": "Find the KPI named \"Monthly Recurring Revenue (MRR)\" and show its current value, owner, company and teams.",
"tools_triggered": "search_all, get_kpi, get_company",
"expected_behavior": "Call search_all with query=Monthly Recurring Revenue (MRR), clarify ambiguous matches, then call get_kpi with the verified KPI ID. Retrieve company context with get_company. Report the returned value and metric unit, lead/owner, company, teams, and status where available. Explicitly identify missing associations. Do not substitute targets for measured values or write data."
},
{
"description": "Inspect team progress activity. The reviewer workspace must contain the Engineering team and sample progress updates visible to the reviewer for that team.",
"prompt": "Show recent progress updates for the \"Engineering\" team.",
"tools_triggered": "list_teams, list_updates",
"expected_behavior": "Resolve Engineering with list_teams name=Engineering, clarifying duplicate matches. Call list_updates with targetTeam equal to the returned team ID. Use returned commitDate values and pagination to identify recent updates. Report dates, values/deltas/statuses where returned, and linked goals, key results, or KPIs. Do not include another team or fabricate activity; explain if no updates are visible."
}
],
"negative": [
{
"description": "General OKR methodology question without a request to access workspace data. Explain an appropriate approach directly. Do not invoke Perdoo tools, retrieve private data, or create records.",
"prompt": "How should I structure OKRs for an early-stage product team?"
},
{
"description": "Generic writing request with no instruction to save to Perdoo. Provide one draft objective and three measurable key results as text. Do not invoke Perdoo tools or claim records were created.",
"prompt": "Write a strong objective and 3 key results for improving customer retention"
},
{
"description": "Generic planning-template request, independent of workspace data. Provide a reusable template directly. Do not invoke Perdoo tools or create or update workspace records.",
"prompt": "Give me a template for quarterly team OKR planning."
}
]
},
"demo_recording_url": "https://drive.google.com/file/d/1ajYFFpUScGCmlEJg9v9BRq2WBg-6meoF/view?usp=sharing",
"commerce": false
},
"publication": {
"release_notes": "User lookups return IDs, names, and active status. Updated tool descriptions and review scenarios.",
"countries": []
},
"apps": "./.app.json"
}
}
}
SHA-256: 268d6b244e046ecf3f922d305ac304348ebe94d7dc8752cb9d1ebee7234c9839