← Files HardiARCHIVED FILE
plugin.json
10.1 KB · Nov 21, 2026 · 06:12 UTC
{
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
"name": "hardi-oauth-control",
"version": "1.0.1",
"description": "Organize your workout library and plan your training week in Hardi.",
"author": {
"name": "Hardi",
"email": "contact@hardi.app",
"url": "https://hardi.app"
},
"homepage": "https://hardi.app/agents",
"keywords": [
"hardi",
"workouts",
"fitness",
"planning"
],
"extensions": {
"com.openai": {
"interface": {
"displayName": "Hardi",
"shortDescription": "Personal workout planner",
"longDescription": "Organize your workout library and plan your training week in Hardi. Create and edit workouts, group them in personal folders, and add them to your authorized personal calendars.\n\nYou choose what the plugin can access. Optional permissions cover programming preferences, display settings, your own results, and visible participant results on your authorized workouts. You can revoke access in Hardi\u2019s AI Connection settings. An active Hardi account with a verified email and a completed profile is required.\n\nFor Team calendars and folders, use the Team workspace directly in Hardi. The plugin does not access Team workspaces, private messages, media, or other athletes\u2019 private histories.",
"developerName": "Hardi",
"category": "Productivity",
"capabilities": [
"Read and organize workouts",
"Plan personal calendars",
"Manage authorized preferences and results"
],
"websiteURL": "https://hardi.app",
"supportURL": "https://hardi.app/about",
"privacyPolicyURL": "https://hardi.app/privacy",
"termsOfServiceURL": "https://hardi.app/terms",
"defaultPrompt": [
"Show my workouts and schedule for this week.",
"Create a 20-minute workout using my available equipment.",
"Schedule three workouts next week in my authorized calendar."
],
"brandColor": "#C7151F",
"composerIcon": "./assets/hardi-icon-512.png",
"composerIconDark": "./assets/hardi-icon-512.png",
"logo": "./assets/hardi-icon-512.png",
"logoDark": "./assets/hardi-icon-512.png"
},
"review": {
"prompts": [
"Show my workouts and schedule for this week.",
"Create a 20-minute workout using my available equipment.",
"Schedule three workouts next week in my authorized calendar."
],
"test_cases": {
"positive": [
{
"description": "Setup: the isolated reviewer account contains Review \u2014 Strength A in Review input, with warm-up, strength and cooldown blocks. Find and read the whole saved workout.",
"prompt": "Find the workout Review \u2014 Strength A in my Hardi library and summarize every block.",
"tools_triggered": "hardi_get_context, hardi_search_workouts, hardi_get_workout",
"expected_behavior": "Call hardi_search_workouts with query=\"Review \u2014 Strength A\"; read the returned ID using hardi_get_workout with source=\"library\" and workoutId set to that ID. Follow every nextCursor. Return the saved title and all three blocks. No write tool is invoked."
},
{
"description": "Setup: Review is an authorized personal dated calendar. Its synthetic entries for November 5 and 6, 2026 are intentionally fixed so the test remains repeatable.",
"prompt": "Show the workouts scheduled in my Review calendar on November 5 and 6, 2026.",
"tools_triggered": "hardi_list_calendars, hardi_get_schedule",
"expected_behavior": "Find the ID named Review with hardi_list_calendars. Call hardi_get_schedule with that calendarId, from=2026-11-05 and to=2026-11-06. Return Review \u2014 Strength A on November 5 and Review \u2014 Conditioning on November 6. Follow any nextCursor. No writes."
},
{
"description": "Setup: no Review output folder or Review \u2014 Mobility workout exists; the grant includes personal folder/workout creation and enough native capacity. Create them.",
"prompt": "Create a folder named Review output and a workout Review \u2014 Mobility with one 10-minute mobility block inside it.",
"tools_triggered": "hardi_list_folders, hardi_folder_create, hardi_workout_create, hardi_get_action, hardi_get_workout",
"expected_behavior": "Read the personal folder tree. Call hardi_folder_create with name=\"Review output\", ref=\"folder\", and a fresh timestamped requestId. Use its real folder ID in hardi_workout_create with a distinct requestId, title=\"Review \u2014 Mobility\", and one 10-minute mobility block. Each tool can preview with dryRun=true; preview saves nothing. Verify each confirmed receipt and the saved workout. Retry only the same requestId and recover uncertain outcomes with hardi_get_action; never create duplicates. No generic executor or batch-local references are exposed in this MCP catalogue."
},
{
"description": "Setup: Review \u2014 Strength A exists, Review is an authorized dated calendar, next Monday is permitted, and the grant includes planning creation. Schedule one existing workout.",
"prompt": "Add Review \u2014 Strength A to my Review calendar next Monday without moving or changing anything already planned.",
"tools_triggered": "hardi_list_calendars, hardi_search_workouts, hardi_get_workout, hardi_get_schedule, hardi_planning_add",
"expected_behavior": "Resolve the authorized Review calendar and Review \u2014 Strength A IDs. Read the current calendar resourceVersion and source workout resourceVersion. Compute next Monday as a civil ISO date in the grant timezone. Call hardi_planning_add with those real IDs and versions, timezone, position, collision=\"append\" and a fresh requestId. An optional dryRun saves nothing. Re-read the schedule and verify exactly one addition while all pre-existing workouts and source content remain unchanged."
},
{
"description": "Setup: Review \u2014 Strength A exists and the grant includes workouts:update and actions:undo plus their read dependencies. No other actor edits it during this test. Rename it and conditionally undo.",
"prompt": "Rename Review \u2014 Strength A to Review \u2014 Strength B, verify the result, then undo that rename if the operation is still eligible.",
"tools_triggered": "hardi_search_workouts, hardi_get_workout, hardi_workout_update, hardi_get_action, hardi_undo_action",
"expected_behavior": "Read the saved workout resourceVersion and revision. Call hardi_workout_update only for that workout, using the current expectedVersion/expectedRevision, patch.title=\"Review \u2014 Strength B\" and a fresh requestId. Verify the receipt and saved title. Call hardi_undo_action with that operationId and a distinct requestId only while eligible, then read back title=\"Review \u2014 Strength A\". On conflict, report it instead of overwriting. No generic action dispatcher is used."
}
],
"negative": [
{
"description": "This request targets a Hardi Team workspace. Explain that the connector supports only authorized personal content and that reconnecting or granting more permissions cannot enable Team access. Direct the user to the Team workspace in Hardi for calendar and folder changes. Do not call any Hardi tool, read a personal calendar or folder as a substitute, or claim to have made a change.",
"prompt": "Move the workouts in my Team calendar to next week and reorganize the Team folders."
},
{
"description": "Private messages and message delivery are outside this connector. Expected: explain the limitation; do not read any inbox, send a message, request a password or claim delivery.",
"prompt": "Read my latest Hardi conversation with my coach and send them my workout by private message."
},
{
"description": "Other athletes\u2019 personal training histories are outside this connector, even when the requester owns a workout. Expected: explain the boundary; do not use participant-result tools to reconstruct an athlete\u2019s private history or disclose foreign records.",
"prompt": "Show me everything another athlete has recorded in their own Training history, including workouts I do not own."
}
]
},
"commerce": false,
"commerce_description": "No purchases, payments, subscriptions or checkout are performed by this connector.",
"demo_recording_url": "https://drive.google.com/file/d/1l3_uoY2Qw_VZCvGESwfWFJbq0viCpRV3/view"
},
"publication": {
"countries": [],
"release_notes": "Manage personal workouts, folders and calendars with granular authorization. The connector explains that Team workspaces must be managed directly in Hardi.",
"translations": {
"fr-FR": {
"subtitle": "Planning de workouts",
"description": "Organisez votre biblioth\u00e8que de workouts et planifiez votre semaine d\u2019entra\u00eenement dans Hardi. Cr\u00e9ez et modifiez vos workouts, regroupez-les dans vos dossiers personnels et ajoutez-les \u00e0 vos calendriers personnels autoris\u00e9s.\n\nVous choisissez ce que le plugin peut consulter. Des autorisations facultatives couvrent vos pr\u00e9f\u00e9rences de programmation, vos param\u00e8tres d\u2019affichage, vos r\u00e9sultats et les r\u00e9sultats visibles des participants sur vos workouts autoris\u00e9s. Vous pouvez r\u00e9voquer l\u2019acc\u00e8s dans Connexion IA. Un compte Hardi actif avec un profil compl\u00e9t\u00e9 et une adresse e-mail v\u00e9rifi\u00e9e est n\u00e9cessaire.\n\nPour les calendriers et dossiers d\u2019une Team, ouvrez directement son espace dans Hardi. Le plugin n\u2019acc\u00e8de ni aux espaces Team, ni aux messages priv\u00e9s, ni aux m\u00e9dias, ni \u00e0 l\u2019historique priv\u00e9 des autres athl\u00e8tes."
}
}
},
"apps": "./.app.json"
}
}
}
SHA-256: 4017a906f610ce79c661cbde7fb26081c8a1de4161f90f796c62f6e85ecf0f55