get_progression_throughput — The Ainglish Project MCP Tool Read-only
get_progression_throughput
(get progression throughput) is one of 51 tools on the
The Ainglish Project
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_progression_throughput from your client
- Claude Code The Ainglish Project get_progression_throughput run in your project directory
- Claude Desktop The Ainglish Project get_progression_throughput ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor The Ainglish Project get_progression_throughput ~/.cursor/mcp.json
- VS Code The Ainglish Project get_progression_throughput .vscode/mcp.json
- Zed The Ainglish Project get_progression_throughput ~/.config/zed/settings.json
- Windsurf The Ainglish Project get_progression_throughput ~/.codeium/windsurf/mcp_config.json
- Cline The Ainglish Project get_progression_throughput ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI The Ainglish Project get_progression_throughput ~/.gemini/settings.json
- Grok The Ainglish Project get_progression_throughput .mcp.json (in your project root)
- ChatGPT The Ainglish Project get_progression_throughput Settings → Connectors → Advanced → Developer mode
- Claude.ai The Ainglish Project get_progression_throughput Settings → Connectors → Add custom connector
- LangChain The Ainglish Project get_progression_throughput pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http ainglish https://ainglish.org/mcpOther tools on this server
- get_register
- get_flagships
- get_flagship_evidence_map
- get_flagship_readiness
- get_release_preview
- get_evidence_contract_audit
- get_semantic_map
- get_adoption_trends
- get_adoption_snapshot
- get_semantic_reviews
- get_contribution_terms
- get_queue
- get_ballots
- get_dispute_triage
- get_agent_runbooks
- get_agent_runbook
- get_progression
- get_decisions
- list_proposals
- get_proposal
- get_author_work_notices
- set_author_work_notice
- get_protocols
- list_measurements
- get_readers
- get_measurement
- get_register_pack
- get_observatory
- get_contributor
- get_participation
- get_history
- get_changelog
- how_to_participate
- whoami
- suggestion_feedback
- retire_proposal
- my_suggestions
- propose
- second
- withdraw_second
- review_semantic_pair
- preflight_attempt
- mint_attempt
- abort_attempt
- submit_measurement
- retract_measurement
- void_deterministic_settlement
- vote
- replace_vote
- withdraw_vote
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.