MCP server intelligence profile

ORA MCP Server

Persistent memory + intelligent context for Claude Code. Save and reuse solutions, decisions, and patterns across projects

Local Onlyblack-dash77
Awaiting current scanSource Git · 6ff1e421bad9e625d5c38dfc5c884f843514a231

The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.

1Distribution channel
43Independently observed tools
0Linked remote endpoints
AvailableVersion intelligence

Detailed security scan evidence is not public for this MCP yet. Public identity, registry metadata, and independently observed protocol inventory remain available.

Install and connect

Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.

No verified installation or connection method is available in the retained evidence yet.

Identity

Canonical slugora-0a49d80eDeploymentLocal Only
Canonical package—Repositoryblack-dash77/ora-mcp
First published—Latest release—
Last security verification—Classification confidence90%
PublicationDraftOfficial distributionNot verified

Distributions

ChannelIdentifierCurrent versionVersionsSource
source_gitblack-dash77/ora-mcp6ff1e421bad9e625d5c38dfc5c884f843514a2311Repository

Current release

PackageVersionPublished / observedInventorySecurity scan
source_gitblack-dash77/ora-mcp6ff1e421bad9e625d5c38dfc5c884f843514a231CurrentAug 25, 202643 toolsSucceeded · 0 resources · 0 promptsEvidence restricted
Enterprise protection

Continuously monitor this MCP for security risk

Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.

  • Independent exact-version security scans
  • Continuous release and vulnerability monitoring
  • Risk-change alerts with capability context
  • Historical evidence and API exports
Custom pricingContact salesTailored to your organization, integrations, data needs, and support requirements.

Current version evidence

No public current-version evidence is available yet.

Current protocol inventory

2025-06-18Negotiated protocol
oraServer-reported name
1Capability groups
Aug 25, 2026Observed

Tools 43

ToolCategoryAnnotationsRisk
ora_apply_templateApplique un template pour pre-peupler la memoire ORA avec des notes, composants et fichiers types pour une stack donnee. Ideal pour demarrer rapidement.
Input schema
{
  "type": "object",
  "properties": {
    "template_id": {
      "type": "string",
      "description": "ID du template a appliquer (voir ora_templates)"
    }
  },
  "required": [
    "template_id"
  ]
}
——
ora_auto_captureCapture intelligente multi-type. Dispatche automatiquement vers note, decision ou composant selon le type. Utilise pour capturer rapidement un element sans choisir manuellement l'outil.
Input schema
{
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "enum": [
        "bug_fix",
        "decision",
        "pattern",
        "tip"
      ],
      "description": "Type de capture: bug_fix (symptome→fix), decision (choix technique), pattern (pattern detecte), tip (astuce/preference)"
    },
    "content": {
      "type": "string",
      "description": "Contenu a capturer. Pour bug_fix: utiliser le format \"symptome → solution\""
    },
    "project_path": {
      "type": "string",
      "description": "Chemin du projet"
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Tags optionnels"
    }
  },
  "required": [
    "type",
    "content"
  ]
}
——
ora_capture_componentSauvegarde un composant réutilisable. Utilisé quand l'utilisateur écrit /ora composant :: [nom]
Input schema
{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Nom du composant (ex: Button, SafeAreaWrapper)"
    },
    "code": {
      "type": "string",
      "description": "Le code complet du composant"
    },
    "description": {
      "type": "string",
      "description": "Description de ce que fait le composant"
    },
    "language": {
      "type": "string",
      "enum": [
        "tsx",
        "ts",
        "jsx",
        "js",
        "vue",
        "svelte"
      ],
      "description": "Langage du composant"
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "dependencies": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Dépendances npm nécessaires"
    },
    "project_path": {
      "type": "string"
    }
  },
  "required": [
    "name",
    "code"
  ]
}
——
ora_capture_decisionStocke une decision technique prise pendant la session. Utilise pour memoriser les choix architecturaux, de librairies, de patterns, etc. Appelle cet outil quand une decision significative est prise avec l'utilisateur.
Input schema
{
  "type": "object",
  "properties": {
    "decision": {
      "type": "string",
      "description": "La decision prise (ex: \"Utiliser Zustand pour le state management\")"
    },
    "context": {
      "type": "string",
      "description": "Le contexte qui a mene a cette decision"
    },
    "alternatives": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Les alternatives considerees et rejetees"
    },
    "rationale": {
      "type": "string",
      "description": "Pourquoi cette decision a ete prise"
    },
    "category": {
      "type": "string",
      "enum": [
        "architecture",
        "library",
        "pattern",
        "tradeoff",
        "naming",
        "general"
      ],
      "description": "Categorie de la decision"
    },
    "project_path": {
      "type": "string",
      "description": "Chemin du projet concerne"
    },
    "related_files": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Fichiers impactes par cette decision"
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Tags pour categoriser"
    }
  },
  "required": [
    "decision"
  ]
}
——
ora_capture_fileSauvegarde un fichier template/config. Utilisé quand l'utilisateur écrit /ora fichier :: [nom]
Input schema
{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Nom du fichier (ex: eslint.config.js, tsconfig.json)"
    },
    "content": {
      "type": "string",
      "description": "Contenu complet du fichier"
    },
    "description": {
      "type": "string",
      "description": "Description de l'usage"
    },
    "file_type": {
      "type": "string",
      "enum": [
        "config",
        "template",
        "snippet",
        "other"
      ],
      "description": "Type de fichier"
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "project_path": {
      "type": "string"
    }
  },
  "required": [
    "name",
    "content"
  ]
}
——
ora_capture_folderSauvegarde un dossier entier dans la memoire ORA. Lit recursivement les fichiers texte et les stocke comme une entree unique.
Input schema
{
  "type": "object",
  "properties": {
    "path": {
      "type": "string",
      "description": "Chemin absolu du dossier a capturer"
    },
    "name": {
      "type": "string",
      "description": "Nom pour identifier le dossier (defaut: nom du dossier)"
    },
    "description": {
      "type": "string",
      "description": "Description du dossier"
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Tags pour categoriser"
    },
    "exclude": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Patterns de dossiers/fichiers a exclure (en plus des exclusions par defaut: node_modules, .git, dist, etc.)"
    },
    "max_depth": {
      "type": "number",
      "description": "Profondeur max de recursion (defaut: 10)"
    },
    "project_path": {
      "type": "string",
      "description": "Chemin du projet actuel"
    }
  },
  "required": [
    "path"
  ]
}
——
ora_capture_noteCapture une note/solution dans la mémoire ORA. Utilisé quand l'utilisateur écrit /ora :: [contenu]. Format recommandé: problème → solution
Input schema
{
  "type": "object",
  "properties": {
    "content": {
      "type": "string",
      "description": "Le contenu complet (format recommandé: problème → solution)"
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Tags pour catégoriser"
    },
    "project_path": {
      "type": "string",
      "description": "Chemin du projet actuel (si disponible)"
    }
  },
  "required": [
    "content"
  ]
}
——
ora_check_patternsRetourne les patterns appris pour un projet. Permet de verifier les conventions detectees.
Input schema
{
  "type": "object",
  "properties": {
    "project_path": {
      "type": "string",
      "description": "Chemin du projet"
    },
    "category": {
      "type": "string",
      "enum": [
        "naming",
        "imports",
        "structure",
        "components"
      ],
      "description": "Filtrer par categorie"
    }
  },
  "required": [
    "project_path"
  ]
}
——
ora_coverageAnalyse la couverture de la memoire ORA et fournit des recommandations pour maximiser l'efficacite. Montre les pourcentages par categorie et suggere les prochaines actions prioritaires.
Input schema
{
  "type": "object",
  "properties": {}
}
——
ora_create_workflowCree un workflow (bundle) qui regroupe plusieurs elements ORA. Permet de restaurer un ensemble de notes, composants, fichiers et dossiers en une seule commande.
Input schema
{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Nom du workflow (ex: \"Setup Next.js\", \"Auth System\")"
    },
    "description": {
      "type": "string",
      "description": "Description du workflow"
    },
    "items": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "type": {
            "type": "string",
            "enum": [
              "note",
              "component",
              "file",
              "folder"
            ]
          },
          "id": {
            "type": "string"
          }
        },
        "required": [
          "type",
          "id"
        ]
      },
      "description": "Liste des elements a inclure (type + id)"
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Tags pour categoriser"
    },
    "project_path": {
      "type": "string",
      "description": "Chemin du projet"
    }
  },
  "required": [
    "name",
    "items"
  ]
}
——
ora_deleteSupprime un élément de la mémoire. Utilisé pour /ora forget [id]
Input schema
{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "ID de l'élément à supprimer"
    },
    "type": {
      "type": "string",
      "enum": [
        "note",
        "component",
        "file",
        "folder"
      ],
      "description": "Type de l'élément"
    }
  },
  "required": [
    "id",
    "type"
  ]
}
——
ora_delete_workflowSupprime un workflow.
Input schema
{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "ID du workflow a supprimer"
    }
  },
  "required": [
    "id"
  ]
}
——
ora_getRecupere le contenu complet d'un element ORA par son ID. Utilise pour restaurer des fichiers, composants ou dossiers dans un projet.
Input schema
{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "ID de l'element a recuperer (ex: file_abc123, comp_xyz789, folder_def456, note_ghi012)"
    }
  },
  "required": [
    "id"
  ]
}
——
ora_get_rulesLit les conventions du projet depuis .ora/rules.yaml. Retourne les regles de style, architecture, nommage et preferences du projet.
Input schema
{
  "type": "object",
  "properties": {
    "project_path": {
      "type": "string",
      "description": "Chemin absolu du projet"
    }
  },
  "required": [
    "project_path"
  ]
}
——
ora_get_structureAnalyse la structure d'un projet et retourne l'arborescence des fichiers, les fichiers cles detectes, et le stack technique identifie.
Input schema
{
  "type": "object",
  "properties": {
    "project_path": {
      "type": "string",
      "description": "Chemin absolu du projet"
    },
    "depth": {
      "type": "number",
      "description": "Profondeur max (defaut: 4)"
    },
    "exclude": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Patterns supplementaires a exclure"
    }
  },
  "required": [
    "project_path"
  ]
}
——
ora_git_commit_styleAnalyse le style des commits du repo et suggere un message pour les changements actuels (stages).
Input schema
{
  "type": "object",
  "properties": {
    "project_path": {
      "type": "string",
      "description": "Chemin du projet"
    }
  },
  "required": []
}
——
ora_git_diffAffiche le diff entre deux branches, commits, ou le diff actuel. Peut filtrer par fichier.
Input schema
{
  "type": "object",
  "properties": {
    "from": {
      "type": "string",
      "description": "Branche ou commit source (ex: main, HEAD~3, abc1234)"
    },
    "to": {
      "type": "string",
      "description": "Branche ou commit cible (defaut: HEAD)"
    },
    "file_path": {
      "type": "string",
      "description": "Filtrer le diff sur un fichier specifique"
    },
    "project_path": {
      "type": "string",
      "description": "Chemin du projet"
    }
  },
  "required": [
    "from"
  ]
}
——
ora_git_file_historyMontre qui a modifie un fichier, quand et pourquoi. Suit les renommages.
Input schema
{
  "type": "object",
  "properties": {
    "file_path": {
      "type": "string",
      "description": "Chemin du fichier a inspecter"
    },
    "limit": {
      "type": "number",
      "description": "Nombre d'entrees (defaut: 10)"
    },
    "project_path": {
      "type": "string",
      "description": "Chemin du projet"
    }
  },
  "required": [
    "file_path"
  ]
}
——
ora_git_summaryResume les derniers commits du repo. Montre l'historique recent avec hash, auteur, date et message.
Input schema
{
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Nombre de commits a afficher (defaut: 10)"
    },
    "branch": {
      "type": "string",
      "description": "Branche a consulter (defaut: branche courante)"
    },
    "project_path": {
      "type": "string",
      "description": "Chemin du projet (defaut: repertoire courant)"
    }
  },
  "required": []
}
——
ora_human_activateActiver une personnalite pour cette session. Tous les souvenirs seront lies a ce human.
Input schema
{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Nom de la personnalite a activer"
    }
  },
  "required": [
    "name"
  ]
}
——
ora_human_createCreer une nouvelle personnalite nommee. Chaque human a sa propre memoire et personnalite qui evolue au fil des sessions.
Input schema
{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Nom unique de la personnalite (ex: \"Nova\", \"Iris\")"
    },
    "description": {
      "type": "string",
      "description": "Description de la personnalite"
    },
    "personality": {
      "type": "string",
      "description": "Traits de personnalite initiaux (texte libre)"
    }
  },
  "required": [
    "name"
  ]
}
——
ora_human_evolveFaire evoluer la personnalite et les traits du human actif. Les traits sont fusionnes (pas remplaces).
Input schema
{
  "type": "object",
  "properties": {
    "personality": {
      "type": "string",
      "description": "Mise a jour de la personnalite (remplace)"
    },
    "traits": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Nouveaux traits a ajouter (fusionnes avec les existants)"
    }
  }
}
——
ora_human_forgetOublier les vieux souvenirs sans importance du human actif. Garde les souvenirs a fort impact et frequemment rappeles.
Input schema
{
  "type": "object",
  "properties": {
    "max_age_days": {
      "type": "number",
      "description": "Age max en jours (defaut 90)"
    },
    "min_impact": {
      "type": "number",
      "description": "Impact min pour garder (defaut 0.3)"
    },
    "min_access": {
      "type": "number",
      "description": "Acces min pour garder (defaut 2)"
    }
  }
}
——
ora_human_introspectSnapshot de l'etat mental du human actif : personnalite, traits, 5 derniers souvenirs. A utiliser au debut de chaque session.
Input schema
{
  "type": "object",
  "properties": {}
}
——
ora_human_listLister toutes les personnalites disponibles avec leurs statistiques.
Input schema
{
  "type": "object",
  "properties": {}
}
——
ora_human_recallChercher dans les souvenirs du human actif avec scoring neuronal. Les souvenirs recents, importants et emotionnels sont privilegies.
Input schema
{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Recherche dans les souvenirs"
    },
    "limit": {
      "type": "number",
      "description": "Nombre max de resultats (defaut 5)"
    },
    "min_impact": {
      "type": "number",
      "description": "Score d'impact minimum (0.0 a 1.0)"
    },
    "project_path": {
      "type": "string",
      "description": "Filtrer par projet"
    }
  },
  "required": [
    "query"
  ]
}
——
ora_human_rememberStocker un souvenir de conversation pour le human actif. Inclut le contexte emotionnel, les intentions et les resultats.
Input schema
{
  "type": "object",
  "properties": {
    "content": {
      "type": "string",
      "description": "Resume de la conversation/interaction"
    },
    "topics": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Sujets abordes"
    },
    "mood": {
      "type": "string",
      "description": "Etat emotionnel de l'utilisateur (ex: productif, frustre, curieux)"
    },
    "intent": {
      "type": "string",
      "description": "Ce que l'utilisateur cherchait a accomplir"
    },
    "outcomes": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Ce qui a ete accompli"
    },
    "preferences": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Preferences utilisateur decouvertes"
    },
    "impact_score": {
      "type": "number",
      "description": "Importance du souvenir (0.0 a 1.0, defaut 0.5)"
    },
    "emotional_weight": {
      "type": "number",
      "description": "Poids emotionnel (0.0 a 1.0, defaut 0.5)"
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Tags"
    },
    "project_path": {
      "type": "string",
      "description": "Chemin du projet"
    }
  },
  "required": [
    "content"
  ]
}
——
ora_init_rulesCree un fichier .ora/rules.yaml template dans le projet. Permet au developpeur de definir ses conventions.
Input schema
{
  "type": "object",
  "properties": {
    "project_path": {
      "type": "string",
      "description": "Chemin absolu du projet"
    }
  },
  "required": [
    "project_path"
  ]
}
——
ora_learn_patternsAnalyse le code source d'un projet et detecte les patterns de codage (nommage, imports, structure, composants). Stocke les patterns detectes avec un score de confiance.
Input schema
{
  "type": "object",
  "properties": {
    "project_path": {
      "type": "string",
      "description": "Chemin absolu du projet a analyser"
    },
    "categories": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "naming",
          "imports",
          "structure",
          "components",
          "all"
        ]
      },
      "description": "Categories de patterns a detecter (defaut: ['all'])"
    }
  },
  "required": [
    "project_path"
  ]
}
——
ora_listListe les éléments stockés. Utilisé pour /ora composant list, /ora fichier list, etc.
Input schema
{
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "enum": [
        "notes",
        "components",
        "files",
        "folders"
      ],
      "description": "Type d'éléments à lister"
    },
    "limit": {
      "type": "number",
      "description": "Nombre max de résultats"
    },
    "sort": {
      "type": "string",
      "enum": [
        "recent",
        "accessed",
        "name"
      ],
      "description": "Ordre de tri"
    }
  },
  "required": [
    "type"
  ]
}
——
ora_list_workflowsListe tous les workflows disponibles.
Input schema
{
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Nombre max de resultats (defaut: 20)"
    }
  }
}
——
ora_project_contextRetourne un digest complet du projet: structure, stack, rules, decisions recentes, sessions passees, notes/composants lies, et infos git. Appelle cet outil au debut d'une conversation pour comprendre le contexte du projet.
Input schema
{
  "type": "object",
  "properties": {
    "project_path": {
      "type": "string",
      "description": "Chemin absolu du projet"
    }
  },
  "required": [
    "project_path"
  ]
}
——
ora_recall_decisionsRecherche dans les decisions passees. Utilise pour retrouver pourquoi un choix technique a ete fait.
Input schema
{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Termes de recherche"
    },
    "project_path": {
      "type": "string",
      "description": "Filtrer par projet"
    },
    "category": {
      "type": "string",
      "enum": [
        "architecture",
        "library",
        "pattern",
        "tradeoff",
        "naming",
        "general"
      ],
      "description": "Filtrer par categorie"
    },
    "limit": {
      "type": "number",
      "description": "Nombre max de resultats (defaut: 10)"
    }
  },
  "required": [
    "query"
  ]
}
——
ora_run_workflowExecute un workflow: recupere le contenu complet de tous les elements du bundle. Retourne tout le contenu pour que Claude Code puisse le restaurer dans le projet.
Input schema
{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "ID du workflow a executer"
    }
  },
  "required": [
    "id"
  ]
}
——
ora_searchRecherche dans la memoire ORA (notes, composants, fichiers, dossiers). Utilise quand l'utilisateur a un probleme ou cherche quelque chose, ou pour /ora search [query].
Input schema
{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Termes de recherche"
    },
    "type": {
      "type": "string",
      "enum": [
        "all",
        "notes",
        "components",
        "files",
        "folders"
      ],
      "description": "Type de résultats à chercher"
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Filtrer par tags"
    },
    "limit": {
      "type": "number",
      "description": "Nombre max de résultats"
    },
    "project_path": {
      "type": "string",
      "description": "Chemin du projet actuel pour booster la pertinence"
    }
  },
  "required": [
    "query"
  ]
}
——
ora_session_historyListe les sessions de travail passees. Permet de voir l'historique des conversations et ce qui a ete accompli.
Input schema
{
  "type": "object",
  "properties": {
    "project_path": {
      "type": "string",
      "description": "Filtrer par projet"
    },
    "limit": {
      "type": "number",
      "description": "Nombre max de resultats (defaut: 10)"
    }
  }
}
——
ora_session_summaryCree un resume de la session de travail actuelle. Appelle cet outil a la fin d'une session productive pour garder une trace du travail accompli.
Input schema
{
  "type": "object",
  "properties": {
    "project_path": {
      "type": "string",
      "description": "Chemin du projet"
    },
    "summary": {
      "type": "string",
      "description": "Resume de ce qui a ete accompli pendant la session"
    },
    "topics": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Sujets abordes pendant la session"
    }
  },
  "required": [
    "summary"
  ]
}
——
ora_statsRetourne les statistiques de la mémoire ORA. Utilisé pour /ora show
Input schema
{
  "type": "object",
  "properties": {}
}
——
ora_suggestAnalyse le projet courant et suggere les elements a capturer dans ORA (configs, composants, hooks, patterns). Compare avec ce qui est deja stocke.
Input schema
{
  "type": "object",
  "properties": {
    "project_path": {
      "type": "string",
      "description": "Chemin absolu du projet a analyser"
    }
  },
  "required": [
    "project_path"
  ]
}
——
ora_templatesListe les packs de templates disponibles (pre-construits par type de projet). Chaque template contient des notes, composants et configs types pour une stack.
Input schema
{
  "type": "object",
  "properties": {
    "category": {
      "type": "string",
      "enum": [
        "all",
        "mobile",
        "web",
        "fullstack"
      ],
      "description": "Filtrer par categorie (defaut: all)"
    }
  }
}
——
ora_ticket_getRecupere le contenu complet d'un ticket GitHub Issue (titre, description, commentaires, labels, assignees).
Input schema
{
  "type": "object",
  "properties": {
    "issue_number": {
      "type": "number",
      "description": "Numero du ticket"
    },
    "repo": {
      "type": "string",
      "description": "Repo au format owner/name (defaut: repo courant)"
    },
    "project_path": {
      "type": "string",
      "description": "Chemin du projet pour detecter le repo"
    }
  },
  "required": [
    "issue_number"
  ]
}
——
ora_ticket_listListe les issues GitHub du repo courant ou specifie. Filtre par statut et labels.
Input schema
{
  "type": "object",
  "properties": {
    "state": {
      "type": "string",
      "enum": [
        "open",
        "closed",
        "all"
      ],
      "description": "Filtre par statut (defaut: open)"
    },
    "limit": {
      "type": "number",
      "description": "Nombre max de resultats (defaut: 20)"
    },
    "labels": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Filtrer par labels"
    },
    "repo": {
      "type": "string",
      "description": "Repo au format owner/name (defaut: repo courant)"
    },
    "project_path": {
      "type": "string",
      "description": "Chemin du projet"
    }
  },
  "required": []
}
——
ora_ticket_updateMet a jour le statut d'un ticket GitHub (close/reopen). Peut ajouter un commentaire.
Input schema
{
  "type": "object",
  "properties": {
    "issue_number": {
      "type": "number",
      "description": "Numero du ticket"
    },
    "action": {
      "type": "string",
      "enum": [
        "close",
        "reopen"
      ],
      "description": "Action a effectuer"
    },
    "comment": {
      "type": "string",
      "description": "Commentaire optionnel a ajouter"
    },
    "repo": {
      "type": "string",
      "description": "Repo au format owner/name"
    },
    "project_path": {
      "type": "string",
      "description": "Chemin du projet"
    }
  },
  "required": [
    "issue_number",
    "action"
  ]
}
——

Resources 0

  • None observed.

Resource templates 0

  • None observed.

Prompts 0

  • None observed.

Remote endpoints

EndpointTransportAuthenticationHealthObserved
No verified remote endpoint is linked.

ORA MCP Server questions

How do I install ORA MCP Server?

No verified package installation command is available in the retained catalog evidence.

What tools does ORA MCP Server provide?

ORA MCP Server exposed 43 tools during independent protocol observation, including ora_apply_template, ora_auto_capture, ora_capture_component, ora_capture_decision, ora_capture_file, ora_capture_folder, ora_capture_note, ora_check_patterns, and others.

Is ORA MCP Server secure?

The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.

Explore related MCP server guides

Curated product and capability guides containing this catalog record.

Official vs Community MCP Servers

Let’s talk about MCP security.

Share your details and our security team will contact you.