Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
6,000+ web scrapers for your AI agent, start free logo6,000+ web scrapers for your AI agent, start free

Apify gives your agent live web data: 6,000+ prebuilt scrapers and actors, MCP-ready. Sign up free with $5 in usage credits.

Try Apify free
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 48,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

MCP server for JCGE discovery, modeling guidance, solving, validation, and equation rendering.

README.md

<picture> <source media="(prefers-color-scheme: dark)" srcset="docs/src/assets/jcge_agentinterface_logo_dark.png"> <source media="(prefers-color-scheme: light)" srcset="docs/src/assets/jcge_agentinterface_logo_light.png"> <img alt="JCGE AgentInterface logo" src="docs/src/assets/jcge_agentinterface_logo_light.png" height="150"> </picture>

JCGEAgentInterface

<!-- mcp-name: io.github.equicirco/JCGEAgentInterface.jl -->

What is a CGE?

A Computable General Equilibrium (CGE) model is a quantitative economic model that represents an economy as interconnected markets for goods and services, factors of production, institutions, and the rest of the world. It is calibrated with data (typically a Social Accounting Matrix) and solved numerically as a system of nonlinear equations until equilibrium conditions (zero-profit, market-clearing, and income-balance) hold within tolerance.

What is JCGE?

JCGE is a block-based CGE modeling and execution framework in Julia. It defines a shared RunSpec structure and reusable blocks so models can be assembled, validated, solved, and compared consistently across packages.

What is this package?

MCP-compatible interface layer for agents that need to discover, load, solve, validate, and inspect

JCGE models. It exposes a small action API and a standard MCP stdio server over the same functionality.

The agent surface is intentionally focused on:

  • discovering installed JCGE packages and available functionality,
  • listing and describing reusable JCGEBlocks components,
  • guiding users through CGE model development with JCGE blocks,
  • guiding formulation choices such as equality systems, inequalities, MCP/complementarity, and optimization-style representations,
  • guiding calibration with the currently available JCGECalibrate loaders, SAM helpers, labeled containers, and parameter workflows,
  • guiding solver choice and reporting from generated equations,
  • solving registered RunSpec models,
  • validating solved contexts,
  • rendering implemented equations, blocks, and symbols through JCGEOutput,
  • reporting or applying updates to released JCGE packages in the active Julia environment.

The package services are grouped in the documentation as discovery, modeling guidance, model interaction, reporting, environment maintenance, and MCP runtime services. See docs/src/services.md for the full service contract and current limits.

MCP server

The standard MCP transport is:

using JCGEAgentInterface
serve(transport=:mcp_stdio)

Minimal local MCP client configuration:

{
  "mcpServers": {
    "jcge": {
      "command": "julia",
      "args": [
        "--project=/path/to/JCGEAgentInterface.jl",
        "-e",
        "using JCGEAgentInterface; serve(transport=:mcp_stdio)"
      ]
    }
  }
}

The MCP tools use the jcge_ prefix:

  • jcge_capabilities
  • jcge_list_blocks
  • jcge_describe_block
  • jcge_modeling_guide
  • jcge_formulation_guide
  • jcge_solver_guide
  • jcge_calibration_guide
  • jcge_reporting_guide
  • jcge_package_status
  • jcge_update_packages
  • jcge_list_models
  • jcge_load_model
  • jcge_solve
  • jcge_validate_model
  • jcge_render_model
  • jcge_export_results

The original custom JSON action protocol remains available:

serve() reads JSON requests from stdin and writes JSON responses to stdout.

Docker and MCP Registry

OCI-oriented MCP registry metadata is declared in server.json.

Future version tags matching v..* trigger .github/workflows/publish-mcp.yml, which:

  • verifies the tag version matches Project.toml,
  • builds the MCP Docker image,
  • pushes it to GitHub Container Registry as ghcr.io/equicirco/jcge-agentinterface-mcp:<release-version>,
  • updates server.json for that release,
  • publishes the metadata to the official MCP Registry through GitHub OIDC.

The Docker image includes the MCP ownership label required by the MCP Registry:

LABEL io.modelcontextprotocol.server.name="io.github.equicirco/JCGEAgentInterface.jl"

No release, tag, image publication, or registry publication is performed by editing this repository.

How to cite

If you use the JCGE framework, please cite:

Boero, R. JCGE - Julia Computable General Equilibrium Framework [software], 2026. DOI: 10.5281/zenodo.18282436 URL: https://JCGE.org

@software{boero_jcge_2026,
  title  = {JCGE - Julia Computable General Equilibrium Framework},
  author = {Boero, Riccardo},
  year   = {2026},
  doi    = {10.5281/zenodo.18282436},
  url    = {https://JCGE.org}
}

If you use this package, please cite:

Boero, R. JCGEAgentInterface.jl - MCP-compatible agent interface for JCGE tooling. [software], 2026. DOI: 10.5281/zenodo.18335121 URL: https://AgentInterface.JCGE.org SourceCode: https://github.com/equicirco/JCGEAgentInterface.jl

@software{boero_jcgeagentinterface_2026,
  title  = {JCGEAgentInterface.jl - MCP-compatible agent interface for JCGE tooling.},
  author = {Boero, Riccardo},
  year   = {2026},
  doi    = {10.5281/zenodo.18335121},
  url    = {https://AgentInterface.JCGE.org}
}

If you use a specific tagged release, please cite the version DOI assigned on Zenodo for that release (preferred for exact reproducibility).

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Cloud & DevOps servers.