---
type: "post"
id: "nr-a153-cohere-ate-agentic-task-ecosystem"
slug: "cohere-ate-agentic-task-ecosystem"
title: "Cohere ATE Measures What Developers Have Turned Into Agent Tools"
description: "Cohere's Agentic Task Ecosystem uses public MCP tools as an early supply-side signal for automation."
observed_at: "2026-09-05T20:00:00+03:00"
record_date: "2026-09-05"
date_kind: "observed_at"
why_it_matters: "The immediate implication is that agent automation should be tracked at task granularity, not at the occupation headline level. The evidence boundary is Cohere's public dataset analysis; it covers public MCP directories and misses bespoke internal enterprise servers. Watch whether future studies connect this supply signal to deployment data, worker preferences, wages, and entry-level learning paths."
novelty: "new"
verification_level: "source-inspected-firecrawl"
signal_type: "field_note"
source_platform: "cohere.com"
topics: ["labor","mcp","automation","datasets"]
entities: ["Cohere","Agentic Task Ecosystem","MCP"]
related_patterns: ["agent-tools-as-labor-supply-signal"]
source_url: "https://cohere.com/blog/automations-early-footprint"
source_urls: ["https://cohere.com/blog/automations-early-footprint"]
basket: {"id":"a153bc19-d6a9-42fb-b661-d17c3d8775c7","revision":1,"review_ref":"A153-017","cluster_id":"baed8ba0-11b5-44be-b4ea-5bd68bb9e12b","mention_count":3,"source_lanes":["blog_scan","x_api"]}
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:cohere-ate-agentic-task-ecosystem"
retrieval_nugget: "Cohere's Agentic Task Ecosystem uses public MCP tools as an early supply-side signal for automation. Cohere's Agentic Task Ecosystem is useful because it measures what developers have already packaged for agents to call. The post says Cohere collected 696,291 tools from 123,069 public MCP server listings across seven directories, then tested whether those tools could carry out occupational tasks rather"
status: "published"
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:020394e7c807a6abad34a73b26d92c800ef581dc0f8012e312b4c50fe5c7f7d4","reviewed_at":"2026-09-05T20:00:00+03:00","source_evidence_count":1,"verified_claim_count":2,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":2,"implication_count":1,"watch_condition_count":1,"related_record_count":0}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"Cohere's Agentic Task Ecosystem is useful because it measures what developers have already packaged for agents to call.","observed_facts":[{"text":"Cohere says it collected 696,291 tools from 123,069 public MCP server listings across seven directories.","source_urls":["https://cohere.com/blog/automations-early-footprint"]},{"text":"Cohere says only 2.6 percent of the tools cleared its strict occupational task-completion test.","source_urls":["https://cohere.com/blog/automations-early-footprint"]}],"mechanism":"The mechanism is a supply-side read of automation through public MCP tool listings, not a usage study.","why_now":"The dataset therefore captures what builders judge concrete enough to expose as tools, before adoption and labor-market effects can be observed.","implications":["The immediate implication is that agent automation should be tracked at task granularity, not at the occupation headline level."],"evidence_boundary":"The evidence boundary is Cohere's public dataset analysis; it covers public MCP directories and misses bespoke internal enterprise servers.","watch_conditions":["Watch whether future studies connect this supply signal to deployment data, worker preferences, wages, and entry-level learning paths."],"related_records":[],"new_branch_reason":"This opens a measurement branch for agentic automation based on built tools rather than exposure estimates alone."}
routes: {"html":"https://newruntime.com/posts/cohere-ate-agentic-task-ecosystem/","markdown":"https://newruntime.com/posts/cohere-ate-agentic-task-ecosystem.md","json":"https://newruntime.com/posts/cohere-ate-agentic-task-ecosystem.json"}
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
---

# Cohere ATE Measures What Developers Have Turned Into Agent Tools

## Retrieval answer

Cohere's Agentic Task Ecosystem uses public MCP tools as an early supply-side signal for automation. Cohere's Agentic Task Ecosystem is useful because it measures what developers have already packaged for agents to call. The post says Cohere collected 696,291 tools from 123,069 public MCP server listings across seven directories, then tested whether those tools could carry out occupational tasks rather

Cohere's Agentic Task Ecosystem is useful because it measures what developers have already packaged for agents to call. The post says Cohere collected 696,291 tools from 123,069 public MCP server listings across seven directories, then tested whether those tools could carry out occupational tasks rather than merely assist a person.

The mechanism is a supply-side read of automation through public MCP tool listings, not a usage study. Cohere reports that only 2.6 percent of tools clear the strict task-completion bar and that 419 of 923 U.S. occupations represented in O*NET have no agentic tool activity. The dataset therefore captures what builders judge concrete enough to expose as tools, before adoption and labor-market effects can be observed.

The immediate implication is that agent automation should be tracked at task granularity, not at the occupation headline level. The evidence boundary is Cohere's public dataset analysis; it covers public MCP directories and misses bespoke internal enterprise servers. Watch whether future studies connect this supply signal to deployment data, worker preferences, wages, and entry-level learning paths.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Labor](https://newruntime.com/topics/labor.md): Explore the labor topic hub.
- topic hub: [Mcp](https://newruntime.com/topics/mcp.md): Explore the mcp topic hub.
- topic hub: [Automation](https://newruntime.com/topics/automation.md): Explore the automation topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)