Componecat
Componecat is your organization's software catalog: every system, service, library, and API you run, with owners, dependencies, documentation, and endpoints…
От сообщества: Добавлен пользователем или импортирован; проверьте владельца перед подключениемРаботаетБез входаГлобальныйБесплатноМожет изменять данные
Что умеет
- Create Documentation Section: Create a new documentation section on a catalog entity. Section types: OVERVIEW, ARCHITECTURE, RUNBOOK, API_REFERENCE, ADRS, CHANGELOG, CUSTOM. Content is Markdown-format
- Get Relationships: List relationships for a catalog entity. Optionally filter by relationship kind key (e.g. 'depends-on', 'parent-of') and direction. Use depth > 1 for transitive traversal (e.g. all
- Get Team: Get detailed information about a specific team by ID. Returns team name, description, member count, owned entity count, and timestamps.
Какие данные видит
Нужен ли аккаунт
Не нужен: сервер работает без входа
Componecat is your organization's software catalog: every system, service, library, and API you run, with owners, dependencies, documentation, and endpoints in one place. This plugin gives ChatGPT direct access to that catalog.
Ask questions in plain language and get answers from your real software landscape: which team owns the billing service, what depends on the auth API, where the runbook for the payments gateway lives, or which endpoints a component exposes. Search takes precise filters, so one question can cover a whole slice of the catalog. Documentation for each component is available in full, including sections synced from Git, so you can read it and reason about it without leaving the conversation.
You can also keep the catalog current from chat: add or update components, record relationships, attach documentation links, and review recent activity.
Componecat's own product documentation is included too, so ChatGPT can explain how the platform works and walk you through it.
A Componecat account is required. Catalogs are private to your organization, and you sign in with your existing account when connecting.
Список инструментов сервера (47)
Технические названия из tools/list. Нужны только разработчикам.
| create_documentation_section | Create a new documentation section on a catalog entity. Section types: OVERVIEW, ARCHITECTURE, RUNBOOK, API_REFERENCE, ADRS, CHANGELOG, CUSTOM. Content is Markdown-formatted text. |
| get_relationships | List relationships for a catalog entity. Optionally filter by relationship kind key (e.g. 'depends-on', 'parent-of') and direction. Use depth > 1 for transitive traversal (e.g. all transitive dependencies). Direction 'source' means the entity is the source (outgoing), 'target' means entity is target (incoming), 'both' returns all. |
| get_team | Get detailed information about a specific team by ID. Returns team name, description, member count, owned entity count, and timestamps. |
| sync_git_sourced_documentation | Trigger an immediate sync of all Git-sourced documentation sections on a catalog entity. Requires an enabled DocumentationSync capability on a provider matching each section's host (GitHub / GitLab / Bitbucket). The sync runs in the background; poll list_git_sourced_documentation for the resulting sync status. |
| create_catalog_entity | Create a new catalog entity. Works for built-in kinds (system, component, resource, knowledge-base, tool, ai-skillset, template) and any custom kind defined in the organization — use list_entity_kind_definitions to discover custom kind keys. Requires displayName, kind, and an owner team ID; lifecycle defaults to EXPERIMENTAL and description defaults to the displayName. Components support languages and repository. Use namespace to organize entities (optional, omit for no namespace). If the kind has required custom fields, supply them via fieldValuesJson (use list_entity_field_definitions to discover the keys and types) — otherwise the create is rejected. |
| create_interface | Create a new interface on a catalog entity (Component or Resource). Interfaces represent APIs, CLIs, MCP servers, UIs, data shares, or packages. |
| add_relationship | Create a relationship between two catalog entities. Specify source and target by entity ref URI (e.g. 'component://my-service') and the relationship kind key (e.g. 'depends-on', 'parent-of'). Use get_relationship_kinds to see available kinds. |
| get_impact_analysis | Analyze the downstream impact of a catalog entity by traversing transitive relationships. Returns all entities that are transitively connected via the specified relationship kind (default: the dependency relationship kind — one marked isDependency=true), with hop counts indicating distance from the root entity. Useful for understanding blast radius of changes. |
| list_componecat_documentation | List every page of Componecat's own product documentation — how to use the platform, not the contents of this organization's catalog. Returns each page's path, title, summary, and public URL. Call this first, then read_componecat_documentation for the page you need. |
| search_catalog | Search the catalog for entities using full-text search with typo tolerance, or a structured query expression. Returns ranked results with name, displayName, ref, namespace, kind, owner, lifecycle, tags, field values, and relevance score. Supports optional filters by kinds, lifecycle, owner, tags, languages, and field values. The query is optional — omit it to rank by filters alone; for unranked browsing or full enumeration of a kind, use list_catalog_entities instead. Use list_entity_kind_definitions to discover valid kind keys and list_entity_field_definitions to discover available field keys before filtering. |
| list_git_sourced_documentation | List the Git-sourced documentation bindings on a catalog entity. Returns each section's repository, file path pattern, branch, sync status, and last sync error/time. Static (manually-authored) documentation sections are excluded — use get_documentation for those. |
| update_documentation_section | Update an existing documentation section's title, content, or other properties. Only provided fields will be updated; omitted fields remain unchanged. |
| delete_documentation_link | Delete a documentation link. |
| list_entity_field_definitions | List all entity field definitions in the organization. Returns each field's id, key, display name, description, field type, category, options (for Select/MultiSelect types), default value, and whether it is searchable. Field types: Text, Number, Boolean, Date, Url, Select, MultiSelect, User, Team, Tag, Json. |
| list_entity_kind_definitions | List all entity kind definitions in the organization. Returns each kind's id, key, display name, description, icon, color, enabled features (documentation, repository, interfaces, activity log), and allowed interface kinds. Pass a returned 'key' as the 'kind' argument of create_catalog_entity. |
| delete_team | Delete a team from the organization. Fails if the team still owns catalog entities — reassign ownership first, e.g. with update_catalog_entity. |
| list_by_owner | List all catalog entities owned by a specific team. Search by team ID or team name. Returns each entity's type (kind), lifecycle, and description. |
| remove_git_sourced_documentation | Remove the Git source binding from a documentation section without deleting the section. Clears the repository, file path pattern, and branch and stops syncing — the section becomes a manually-editable section. To delete the section entirely instead, use delete_documentation_section. |
| remove_team_member | Remove a member from a team. Pass the member's id as shown by get_team — that works for members with and without a catalog account. A user ID is also accepted. |
| create_documentation_link | Create a new documentation link on a catalog entity. Link types: CONFLUENCE, NOTION, GOOGLE_DOCS, GIT_HUB, GIT_LAB, OTHER. |
| update_interface | Update an existing interface's properties. Only provided fields will be updated; omitted fields remain unchanged. |
| get_interfaces | Get all interfaces for a catalog entity whose kind has the interfaces feature enabled. Returns interface name, kind, protocol, URL, authentication method, spec URL, labels, visibility, health check URL, and rate limit information. |
| list_activity_log_entries | List the activity log entries for a catalog entity, newest first. Each entry has Markdown content, a creation timestamp, the ID of the user who created it (or '(system)' for entries created automatically), and an optional expiration. Only available on entities whose kind has the activity log feature enabled. |
| configure_git_sourced_documentation | Configure Git-sourced documentation on a catalog entity. Creates a documentation section whose content is synced automatically from a Git repository, mirroring the UI's 'Configure Git-Sourced Documentation' dialog. Section types: OVERVIEW, ARCHITECTURE, RUNBOOK, API_REFERENCE, ADRS, CHANGELOG, CUSTOM. After configuring, use sync_git_sourced_documentation to fetch the content (requires an enabled DocumentationSync capability on a matching provider). |
| update_catalog_entity | Update an existing catalog entity's properties. Only provided fields will be updated; omitted fields remain unchanged. Supports updating name, displayName, namespace, description, lifecycle, tags, owner, and the repository and languages of kinds that have them. Changing name or namespace changes the entity's ref URI, which breaks anything referring to the old ref. Use update_entity_field_values to set custom field values. |
| add_activity_log_entry | Append a new entry to a catalog entity's activity log. Content is Markdown-formatted text. Optionally set an expiration after which the entry is automatically purged. Entries are append-only and cannot be edited. |
| get_catalog_entity | Get detailed metadata for a specific catalog entity of any kind, by ID or entity ref URI. Provide exactly one of 'id' (UUID) or 'ref' (entity ref URI, e.g. 'component://my-service'). Returns name, displayName, ref, namespace, kind, lifecycle, owner, description, tags, custom field values, and timestamps. For kinds with a repository, also returns the repository URL, sync status, and a preview of the README. Hierarchy and dependencies are not included — use get_relationships for those, and get_interfaces / get_documentation for interfaces and documentation sections. |
| import_interface_spec | Import or re-import the API specification for an interface. The interface must have a specUrl configured. Fetches the spec from the URL and parses it (OpenAPI, AsyncAPI). |
| delete_documentation_section | Delete a documentation section from a catalog entity. |
| read_componecat_documentation | Read one page of Componecat's product documentation in full, as Markdown. Use the path from list_componecat_documentation, e.g. 'guides/team-sync' or 'reference/descriptor-file'. |
| delete_interface | Delete an interface from a catalog entity. |
| delete_activity_log_entry | Delete an activity log entry from a catalog entity. |
| list_documentation_links | List all documentation links for a catalog entity. Documentation links point to documentation on platforms like Confluence, Notion, Google Docs, GitHub, or GitLab. |
| update_entity_field_values | Set field values on a catalog entity. Accepts key-value pairs where keys correspond to field definition keys. Values are validated against the field definitions. Set a value to null to remove a field value. Use list_entity_field_definitions first to discover available keys and their types. |
| list_teams | List teams in the organization, most recently updated first. Returns team name, description, and member count. Results are paginated — when more pages exist, pass the returned cursor as 'after' to continue. |
| update_git_sourced_documentation | Update an existing Git-sourced documentation binding (repository, file path pattern, branch, title, or sort order). Only provided fields are changed. Changing the file path pattern re-queues the section for syncing. Use list_git_sourced_documentation to find the section ID. To delete the section entirely use delete_documentation_section; to stop syncing but keep the section use remove_git_sourced_documentation. |
| list_catalog_entities | List catalog entities for browsing and enumeration — no search query required. Returns entities ordered by name with optional filters by kinds, lifecycle, owner, and tag. Use this for "show me everything" or "list all <kind>" workflows; use search_catalog instead when you have text to rank results against. Results are paginated — when more pages exist, pass the returned cursor as 'after' to continue. Call list_entity_kind_definitions to discover valid kind keys. |
| global_search | Search everything in the application — records, documents, pages — and return one merged, relevance-ranked result list. Use this to locate an item before operating on it with other tools. |
| update_team | Update an existing team's name or description. Returns the updated team details. |
| remove_relationship | Remove a relationship by its ID. Requires edit access to the relationship's source entity. Use get_relationships to find relationship IDs first. |
| get_relationship_kinds | List all available relationship kind definitions for the organization. Returns each kind's key, display name, description, cardinality, cycle policy, delete policy, and directional labels. Use the 'key' values with get_relationships and add_relationship. |
| get_documentation | Get documentation sections for a catalog entity. Returns all documentation sections with section type, title, and Markdown content. Optionally filter by section type (OVERVIEW, ARCHITECTURE, RUNBOOK, API_REFERENCE, ADRS, CHANGELOG, CUSTOM). |
| delete_catalog_entity | Delete a catalog entity (soft-delete). The entity can be restored by an admin using the trash management features. |
| add_team_members | Add one or more members to a team. Members named by user ID must belong to the organization. To record someone who has no account in the catalog, pass their name and/or email in memberNames instead — they appear on the roster and are linked to a user automatically if one turns up later. |
| get_current_organization | Get information about the current organization |
| list_relationship_kind_definitions | List all relationship kind definitions in the organization. Returns each relationship kind's id, key, display name, description, cardinality, cycle policy, delete policy, source/target labels, and semantic flags (isHierarchical, isDependency, isApiProvider). Cardinality: ONE_TO_MANY or MANY_TO_MANY. CyclePolicy: FORBID, WARN, or ALLOW. DeletePolicy: BLOCK_SOURCE, CASCADE, or ALLOW. |
| update_documentation_link | Update an existing documentation link's properties. Only provided fields will be updated; omitted fields remain unchanged. |