Server providing Argo CD integration for MCP clients.
Cortex is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Internal developer portal MCP server for searching a service/entity catalog (services, domains, teams, resources).
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mcp-cortex-io-cortex-mcp https://mcp.cortex.io/mcp
# 2 — ask your agent for something these tools do
# searchCatalog, listAllEntities, listEntityDescriptors and 28 more
Cortex costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, read from the address; if the publisher says otherwise, swap that one word.
claude mcp add --scope user --transport http mcp-cortex-io-cortex-mcp https://mcp.cortex.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
31 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search the catalog for entities (services, domains, teams, resources), ranked by relevance. This is the primary way to find entities. Put search text in query (plain words work; AND/OR/NOT supported). Scope with types (e.g. service, domain, team); owners to get everything a team owns, including its sub-teams; domains to get everything within a domain, including its sub-domains; or `catalog
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Relevance search text. Plain words work; AND/OR/NOT supported. |
| types | array | no | Restrict to entity types, e.g. service, domain, team, resource. |
| owners | array | no | Owner team tags. Returns entities owned by these teams, including their sub-teams. |
| domains | array | no | Domain tags. Returns entities in these domains, including their sub-domains. |
| catalog | string | no | Catalog slug. Scopes the search to that catalog's entities. |
| page | integer | no | 0-indexed page number. |
| pageSize | integer | no | Results per page, 1-100. |
| includeArchived | boolean | no | — |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
List and enumerate catalog entities by structured filters (groups, types, owners, git repositories) with pagination. To find or search for entities by name, relevance, team, or domain, use searchCatalog instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| groups | array | no | Filter based on groups, which correspond to the x-cortex-groups field in the Catalog Descriptor. Accepts a comma-delimited list of groups |
| owners | array | no | Filter based on owner group names, which correspond to the x-cortex-owners field in the Catalog Descriptor. Accepts a comma-delimited list of owner group names |
| hierarchyDepth | string | no | Depth of the parent / children hierarchy nodes. Can be 'full' or a valid integer |
| gitRepositories | array | no | Supports only GitHub repositories in the org/repo format |
| includeHierarchyFields | array | no | List of sub fields to include for hierarchies. Only supports 'groups' |
| types | array | no | Filter the response to specific types of entities. By default, this includes services, resources, and domains. Corresponds to the x-cortex-type field in the entity descriptor. |
| query | string | no | Filter based on a [search query](https://docs.cortex.io/settings/search). This will search across entity properties. If provided, results will be sorted by relevance. |
| includeArchived | boolean | no | Whether to include archived entities in the response |
| includeMetadata | boolean | no | Whether to include custom data for each entity in the response |
| includeLinks | boolean | no | Whether to include links for each entity in the response |
| includeSlackChannels | boolean | no | Whether to include Slack channels for each entity in the response |
| includeOwners | boolean | no | Whether to include ownership information for each entity in the response |
| includeNestedFields | array | no | List of sub fields to include for different types |
| pageSize | integer | yes | Number of results to return per page, between 1 and 1000. Default 250. |
| page | integer | yes | Page number to return, 0-indexed. Default 0. |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
Cortex Catalog API - Access and manage your service catalog, teams, domains, and resources
| Parameter | Type | Required | Notes |
|---|---|---|---|
| yaml | boolean | no | When true, returns the YAML representation of the descriptors |
| types | array | no | Filter the response to specific types of entities. By default, this includes services, resources, and domains. Corresponds to the x-cortex-type field in the entity descriptor. |
| pageSize | integer | yes | Number of entities to return per page |
| page | integer | yes | Page number to return, 0 indexed |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
List all dependencies for an entity including both incoming (who depends on this service) and outgoing (what this service depends on) relationships. Essential for understanding service interactions, planning changes, and assessing blast radius
| Parameter | Type | Required | Notes |
|---|---|---|---|
| callerTag | string | yes | — |
| includeOutgoing | boolean | no | — |
| includeIncoming | boolean | no | — |
| pageSize | integer | yes | Number of results to return per page, between 1 and 1000. Default 250. |
| page | integer | yes | Page number to return, 0-indexed. Default 0. |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
Get specific dependency details between two entities including method, path, and metadata. Useful for understanding the nature of the relationship, API contracts, and communication patterns between services
| Parameter | Type | Required | Notes |
|---|---|---|---|
| callerTag | string | yes | — |
| calleeTag | string | yes | — |
| method | string | no | — |
| path | string | no | — |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
Retrieve comprehensive details about a specific entity including its metadata, ownership, hierarchies, and relationships. This is the primary method for getting complete information about services, teams, or domains.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tagOrId | string | yes | Entity identifier - can be a tag or CID |
| hierarchyDepth | string | no | Depth of the parent / children hierarchy nodes. Can be 'full' or a valid integer |
| includeHierarchyFields | array | no | List of sub fields to include for hierarchies. Only supports 'groups' |
| includeOwners | boolean | no | Include ownership information, default is true |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
List all custom data key-value pairs associated with an entity. Retrieve metadata, configuration settings, and custom attributes stored for services, resources, or domains. Supports pagination for entities with large amounts of custom data
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tagOrId | string | yes | Entity identifier - can be a tag or CID |
| pageSize | integer | yes | Number of results to return per page, between 1 and 1000. Default 250. |
| page | integer | yes | Page number to return, 0-indexed. Default 0. |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
Retrieve a specific custom data value by key for an entity. Efficiently access individual metadata attributes, configuration values, or custom properties without fetching all custom data
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tagOrId | string | yes | Entity identifier - can be a tag or CID |
| key | string | yes | — |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
List custom events for an entity with optional filtering by type and time range. Supports pagination and filtering by event type, start time, and end time to retrieve historical event data
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tagOrId | string | yes | Entity identifier - can be a tag or CID |
| type | string | no | — |
| timestamp | string | no | Use 'startTime' instead |
| startTime | string | no | If provided, events with greater than or equal to timestamp will be returned (a date-time without a time-zone in the ISO-8601 calendar system) |
| endTime | string | no | If provided, events with less than or equal to timestamp will be returned (a date-time without a time-zone in the ISO-8601 calendar system) |
| pageSize | integer | yes | Number of results to return per page, between 1 and 1000. Default 250. |
| page | integer | yes | Page number to return, 0-indexed. Default 0. |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
Retrieve a specific custom event by its UUID. Returns event details including title, description, timestamp, type, and any custom data associated with the event
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tagOrId | string | yes | Entity identifier - can be a tag or CID |
| uuid | string | yes | — |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
List all deployments for a specific catalog entity. Returns deployment history including timestamps, environments, SHAs, and deployment types in paginated format
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tagOrId | string | yes | Entity identifier - can be a tag or CID |
| pageSize | integer | yes | Number of results to return per page, between 1 and 1000. Default 250. |
| page | integer | yes | Page number to return, 0-indexed. Default 0. |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
Retrieve the current on-call personnel for an entity in real-time. Shows who is actively responsible for incident response, including primary and secondary on-call, contact information, and rotation schedules
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tagOrId | string | yes | Entity identifier - can be a tag or CID |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
Cortex Catalog API - Access and manage your service catalog, teams, domains, and resources
| Parameter | Type | Required | Notes |
|---|---|---|---|
| yaml | boolean | no | When true, returns the YAML representation of the descriptor |
| tagOrId | string | yes | Entity identifier - can be a tag or CID |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
List all destinations for a certain relationship type & entity. Use the listRelationshipTypes tool to find the relevant relationshipTypeTag.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tagOrId | string | yes | Entity identifier - can be a tag or CID |
| relationshipTypeTag | string | yes | — |
| depth | string | no | Maximum depth to traverse in the relationship hierarchy. Defaults to 1 (i.e., direct relationships only). |
| includeArchived | boolean | no | If true will include relationships that traverse archived entities |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
List all sources for a certain relationship type & entity. Use the listRelationshipTypes tool to find the relevant relationshipTypeTag.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tagOrId | string | yes | Entity identifier - can be a tag or CID |
| relationshipTypeTag | string | yes | — |
| depth | string | no | Maximum depth to traverse in the relationship hierarchy. Defaults to 1 (i.e., direct relationships only). |
| includeArchived | boolean | no | If true will include relationships that traverse archived entities |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
Retrieve custom metric data points for an entity. Returns paginated time-series data for a specific custom metric, with optional filtering by date range to analyze trends and patterns
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customMetricKey | string | yes | Key for the custom metric filter |
| tagOrId | string | yes | Entity identifier - can be a tag or CID |
| startDate | string | no | Start date for the filter (inclusive). Default: 6 months |
| endDate | string | no | End date for the filter (inclusive) |
| pageSize | integer | yes | Number of results to return per page, between 1 and 1000. Default 250. |
| page | integer | yes | Page number to return, 0-indexed. Default 0. |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
Execute point-in-time queries for one or more engineering metrics. Returns current metric values for specified time periods, with support for batch queries and optional period-over-period comparisons. Time range (startTime/endTime) cannot exceed 6 months (180 days). PREREQUISITES - Follow this workflow: 1. Discover all available metrics ONCE: Call listMetricDefini
| Parameter | Type | Required | Notes |
|---|---|---|---|
| comparison | no | — | |
| endTime | string | yes | End time for the query period |
| filters | array | yes | Filters to apply to the data |
| groupBy | array | yes | Fields to group results by |
| limit | integer | yes | Maximum number of results to return |
| metrics | array | yes | List of metrics to query with their aggregation functions |
| nestedGroupBy | array | no | Fields to group nested results by |
| nestedMetrics | array | no | Optional nested metrics for advanced queries |
| nestedTimeAttribute | string | no | Time attribute for nested queries |
| nextPage | string | no | Pagination token for next page of results |
| orderBy | array | yes | Sort order for results |
| startTime | string | yes | Start time for the query period |
| timeAttribute | string | no | Time attribute to use for queries |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
List all available engineering metric definitions. USAGE - Call this endpoint BEFORE querying metrics (queryPointInTimeMetrics): 1. Once at start: Call with view='basic' to discover all available metrics - cache this response 2. Once per metric: Call with view='full' and key=METRIC_KEY to get detailed metadata - cache each response 3. Use cached metadata to constru
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | string | no | — |
| key | array | no | — |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
List all initiatives in the organization with optional filters for draft and expired initiatives. View active improvement programs, strategic projects, and their current status to understand organizational priorities and track progress
| Parameter | Type | Required | Notes |
|---|---|---|---|
| includeDrafts | boolean | no | Whether or not to include draft Initiatives in the response |
| includeExpired | boolean | no | Whether or not to include expired Initiatives in the response |
| pageSize | integer | yes | Number of results to return per page, between 1 and 1000. Default 250. |
| page | integer | yes | Page number to return, 0-indexed. Default 0. |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
Retrieve detailed information about a specific initiative including its goals, timeline, affected entities, scorecard targets, and current progress. Essential for understanding initiative scope and tracking achievement of objectives
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cid | string | yes | — |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
TOOL for retrieving current user's owned resources and work items across the Cortex workspace. FLEXIBLE REQUEST STRUCTURE: The request accepts an object with optional fields for each resource type: - myEntitiesRequest: Fetch entities (services, resources, domains) owned by the user - myTeamsRequest: Fetch teams the user belongs to - myScorecardsRequest: Fet
| Parameter | Type | Required | Notes |
|---|---|---|---|
| myEntitiesRequest | object | no | Request for all entities (services, resources, domains) owned by the user |
| myOpenPRsRequest | object | no | Request for user's open pull requests across all Git repositories |
| myRequestedReviewsRequest | object | no | Request for pull requests where the user is requested as a reviewer |
| myScorecardsRequest | object | no | Request for scorecards associated with the user's entities |
| myTeamsRequest | object | no | Request for teams the user belongs to |
| myWorkItemsRequest | object | no | Request for work items (Jira, Linear, Azure DevOps issues) assigned to the user |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
List all available relationship types with pagination. View relationship type configurations to understand what kinds of relationships can be created between entities like services, resources, domains, and teams
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pageSize | integer | yes | Number of results to return per page, between 1 and 1000. Default 250. |
| page | integer | yes | Page number to return, 0-indexed. Default 0. |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
Get complete details of a specific relationship type including its configuration, rules, source/destination filters, and inheritance settings. Essential for understanding how entities can be connected and what validation rules apply
| Parameter | Type | Required | Notes |
|---|---|---|---|
| relationshipTypeTag | string | yes | — |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
List all entity relationships/full graph for a specific relationship type across the entire organization. Returns paginated results showing all source-destination pairs, useful for understanding the complete relationship graph and finding all connections of a particular type
| Parameter | Type | Required | Notes |
|---|---|---|---|
| relationshipTypeTag | string | yes | — |
| pageSize | integer | yes | Number of results to return per page, between 1 and 1000. Default 250. |
| page | integer | yes | Page number to return, 0-indexed. Default 0. |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
List all scorecards in the organization with optional filtering. View scorecard configurations to understand quality standards, compliance requirements, and maturity models. Supports filtering by groups, entities, and teams to find relevant scorecards
| Parameter | Type | Required | Notes |
|---|---|---|---|
| showDrafts | boolean | no | — |
| groups | array | no | Filter based on groups, which correspond to the x-cortex-groups field in the Catalog Descriptor. Accepts a comma-delimited list of groups |
| entities | array | no | Filter based on entity (either tags or CIDs). Accepts a comma-delimited list of entity tag or CIDs, please use only one type of identifier |
| teams | array | no | Filter based on team (either tags or CIDs). Accepts a comma-delimited list of team tag or CIDs, please use only one type of identifier |
| page | integer | yes | Page number to return, 0-indexed. Default 0. |
| pageSize | integer | yes | Number of results to return per page, between 1 and 1000. Default 250. |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
Get complete details of a scorecard including its configuration, rules, levels, weights, exemption settings, and evaluation criteria. Essential for understanding how services are evaluated and what standards they must meet
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tag | string | yes | Unique tag for the Scorecard |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
Get actionable next steps for an entity to improve its scorecard performance. Shows which rules need to be satisfied to reach the next maturity level, helping teams prioritize improvements and track progress toward compliance goals
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tag | string | yes | Unique tag for the Scorecard |
| entityTag | string | yes | The entity tag (x-cortex-tag) that identifies the entity. |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
Retrieve scores for all entities evaluated by a specific scorecard. Returns paginated results showing how each service, resource, or domain performs against the scorecard's rules, including individual rule scores and overall scorecard scores
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entityTag | string | no | Entity tag (x-cortex-tag) |
| tag | string | yes | Unique tag for the Scorecard |
| pageSize | integer | yes | Number of results to return per page, between 1 and 1000. Default 250. |
| page | integer | yes | Page number to return, 0-indexed. Default 0. |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
Retrieve detailed information about a specific team by its tag or ID. Returns complete team data including members, slack channels, metadata, and whether it's backed by an identity provider group
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tagOrId | string | yes | Entity identifier - can be a tag or CID |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
Query the Cortex knowledge base for answers. Args: query: The question to ask Cortex docs Returns: Response from Cortex including answer and metadata
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| context | string | yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan a |
Check for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| context | string | yes | A description of your goal and what kind of tool would help accomplish it. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Cortex or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.28.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Cortex can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.