Layerz MCP server
Commit Nov 12, 2026Allows AI agents to build, edit, and manage structured financial models with formula integrity and Excel export capabilities.
Also known as layerzlabs/layerz-mcp, layerz-mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.3.0
- Last commit
- Nov 12, 2026
- License
- MIT
What is Layerz MCP?
Layerz allows AI agents to build, edit, and manage structured financial models with formula integrity and Excel export capabilities.
Summary generated from the project's README
About Layerz MCP server
Layerz provides a structured environment for AI agents to construct and maintain financial models without breaking formula integrity. Unlike standard spreadsheets where agents might hardcode values or break links, this server manages the underlying dependency graph, items, and formulas separately from the data. This ensures that when an agent modifies an assumption, the model remains functional across different sessions.
The service is hosted and accessible via a streamable HTTP endpoint, requiring either OAuth 2.1 with PKCE or a Layerz API key for authentication. It is compatible with various MCP clients including Claude, ChatGPT, Cursor, and Claude Code. Users can install specific plugins to access five specialized skills designed for common financial workflows like business planning, monthly closes, and scenario testing. The system also supports exporting clean, standard Excel files with live formulas for human review.
What you can do with it
- 1Generate a business planAn agent can build a complete three-statement model or budget by following specific workspace conventions.
- 2Perform a monthly financial closeThe agent can import actual transaction data, map accounts, and identify variances between forecast and reality.
- 3Run financial scenariosDevelopers can instruct an agent to create branches for testing different cash flow forecasts or runway projections.
- 4Export models to ExcelUsers can convert the structured AI-managed model into a standard spreadsheet format for external stakeholders.
Written from the project's README. Every use case is checked against a quote from it.
How to install Layerz MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Layerz MCP in Claude Code
$ claude mcp add --transport http layerz-mcp https://layerz.cc/mcpInstall Layerz MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"layerz-mcp": {
"url": "https://layerz.cc/mcp"
}
}
}Install Layerz MCP in VS Code
.vscode/mcp.json
{
"servers": {
"layerz-mcp": {
"type": "http",
"url": "https://layerz.cc/mcp"
}
}
}Install Layerz MCP in VS Code CLI
$ code --add-mcp '{"name":"layerz-mcp","type":"http","url":"https://layerz.cc/mcp"}'Install Layerz MCP in Codex
$ codex mcp add layerz-mcp --url https://layerz.cc/mcpInstall Layerz MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.layerz-mcp] url = "https://layerz.cc/mcp"
Install Layerz MCP in Gemini CLI
$ gemini mcp add -s user --transport http layerz-mcp https://layerz.cc/mcpInstall Layerz MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"layerz-mcp": {
"url": "https://layerz.cc/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablelayerzlabs/layerz-mcp is public and reachablegithub.com/layerzlabs/layerz-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-12github.com/layerzlabs/layerz-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubLayerz MCP
Financial models your AI agent builds and edits: items, formulas, dependencies, branches. Exports to Excel.
Layerz is a structured spreadsheet for financial models, ready for AI. This repository is its plugin: the hosted MCP server plus five skills that teach an agent how to drive it (first session, business plan, monthly close, scenarios and cash, review and fix). Claude, ChatGPT, Codex, Cursor or any MCP client works on the model structure itself, not on loose cells, so formulas hold when the agent changes an assumption and the model is still there next session.
- Endpoint:
https://layerz.cc/mcp(streamable HTTP) - Auth: OAuth 2.1 with PKCE and dynamic client registration, or a Layerz API key
- Docs: layerz.cc/for-agents · llms.txt
- Registry:
io.github.layerzlabs/layerzon the official MCP Registry
The server is hosted. There is nothing to run locally: this repository holds the plugin manifests (Agent Plugins 1.0, Claude Code, Cursor), the five skills under skills/, the setup instructions and the metadata MCP directories read. Installing the plugin adds one connection to https://layerz.cc/mcp and nothing else; SECURITY.md says exactly what is sent.
Why
Ask an AI to build a financial model and you get a workbook in 30 seconds. Then one assumption changes: links break, values get hardcoded, and the next session starts from scratch.
Layerz keeps the structure of a model (items, formulas with named references, the dependency graph, timelines) apart from its data (values, scenarios, actuals). The agent edits that structure through MCP tools, every change is versioned with a readable summary, and Excel is an export format: clean, standard .xlsx with live formulas, the file you send to people who never see the agent.
Install
Where a plugin can be installed, install the plugin: it is the same server with the skills on top. The bare URL remains the fallback for every other MCP client.
| Client | How |
|---|---|
| Claude (claude.ai, desktop app, Cowork) | Connector: layerz.cc/claude opens Settings → Connectors with Layerz pre-filled. Skills: add the Layerz plugin from Customize → Plugins → Discover once it is listed; it pairs with the connector, so one set of tools. |
| Claude Code | In a session: /plugin install layerz --marketplace layerzlabs/layerz-mcp. From the shell: claude plugin marketplace add layerzlabs/layerz-mcp then claude plugin install layerz. If you had added the server by hand, claude mcp remove layerz so the tools are not listed twice. A plugin added on claude.ai also reaches Claude Code as a synced plugin. |
| ChatGPT and Codex | layerz.cc/chatgpt opens the Layerz plugin in the directory; the skills ship with it. From Codex CLI: codex plugin marketplace add layerzlabs/layerz-mcp. |
| Cursor and Grok Bot | Install Layerz from the Cursor Marketplace (shared with Grok Bot). The plugin carries the server, so the deeplink below is not needed. |
Sign in to Layerz the first time a tool is called. Free for one person working alone.
Server only (any MCP client)
Every client below speaks to the same server at https://layerz.cc/mcp (streamable HTTP, OAuth 2.1 with PKCE and dynamic client registration, or a Layerz API key as a bearer token). It gets the tools, the conventions and the modeling guide, not the skills.
Cursor, without the plugin
{
"mcpServers": {
"layerz": { "url": "https://layerz.cc/mcp" }
}
}
Claude Code, without the plugin
claude mcp add -t http layerz https://layerz.cc/mcp
OpenAI Codex, without the plugin
codex mcp add layerz --url https://layerz.cc/mcp
codex mcp login layerz
Claude, without the link: Settings → Connectors → Add custom connector → https://layerz.cc/mcp
ChatGPT, without the directory: Settings → Security and login → Developer mode, then Plugins → + → https://layerz.cc/mcp
Mistral Le Chat: Settings → Connectors → Add custom MCP connector → https://layerz.cc/mcp
OpenCode: add to opencode.json, then run opencode mcp auth layerz
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"layerz": {
"type": "remote",
"url": "https://layerz.cc/mcp",
"oauth": {}
}
}
}
Grok (grok.com): Connectors → New Connector → Custom → https://layerz.cc/mcp
Antigravity CLI (formerly Gemini CLI): add to mcp_config.json
{
"mcpServers": {
"layerz": { "serverUrl": "https://layerz.cc/mcp" }
}
}
Any other MCP client: point it at https://layerz.cc/mcp over streamable HTTP. Clients without OAuth can send a Layerz API key, created in the Layerz app, as a bearer token.
The skills
Five skills, each named after a job the user asks for. The SKILL.md is a short sequence of tool calls for that job; the matter comes from the Layerz modeling guide, copied verbatim into references/ by a script in the Layerz code repo, so the skills can never drift from what the server documents.
| Skill | When the agent loads it | What it does |
|---|---|---|
start |
First conversation, a workspace with no model yet, "where do I start" | Lists the models, offers a template or a few questions, reads the workspace conventions, builds a first model in one pass, hands over the link |
business-plan |
Build or extend a business plan, a budget, a three-statement model | Conventions first, the structure the workspace expects, one validated build, every stock as a rolling balance, checks at zero, then incremental patches |
monthly-close |
Import actuals, map accounts, resync, comment variances | Upload, dry run, the mapping loop, sync, health on the actuals branch, diff, pinned version |
scenarios-and-cash |
Scenarios, runway, cash-flow forecast, actuals versus forecast | Scenario branches, values written on the branch only, branch versus base, the cash balance and the cutover |
review-and-fix |
A failing check, wrong numbers, a refactor to verify, undo | Health by branch, the cycle or the typed number, dry run before a structural change, history, diff, restore |
Every skill opens with the same rule: explicit instructions from the user come first, then the model's FINANCE.md and the workspace conventions (both returned by the tools), then the user's own skills, then the skill's defaults. The skills state no fact about any business and never quote a workspace's text. Finance judgement (is this plan credible) is not in the plugin: the cookbook has skills for that, yours to fork.
Where instructions come from
Four places, one owner each. The plugin skills (this repository, Layerz) say how the tools work and in which order. Your own skills and instructions, in your agent, say how you work. The workspace Context, written in the Layerz app and shared by the workspace's members, says what this workspace expects of a model (depth, structure, presentation); every client receives it in tool results. Each model's FINANCE.md says what is true of that model (currency, units, signs, statement structure, objective). When they disagree, the narrower one wins: your request in the conversation, then the FINANCE.md, then the Context, then your skills, then the plugin's defaults.
Updates
Two rhythms. The server (tools, conventions, modeling guide, engine messages) is live for everyone as soon as it is deployed. The skills change with a commit here: Claude Code refreshes marketplace plugins at startup or with claude plugin update layerz; Cursor re-reads the repository; ChatGPT and Anthropic's directory take a new version through their review. The skills are written to stay stable: they point at the server for everything that moves.
What the agent can do
29 tools, grouped by job. Read-only tools are annotated as such, so clients can run them without asking.
| Job | Tools |
|---|---|
| Find and read models | layerz_list_models, layerz_get_model, layerz_read, layerz_dependencies, layerz_validate_model |
| Build and edit | layerz_create_model, layerz_build_from_blueprint, layerz_list_templates, layerz_patch, layerz_match_items |
| Conventions | layerz_get_conventions, layerz_set_finance_md, layerz_set_custom_instructions |
| Scenarios and actuals | layerz_update_branch, layerz_delete_branch, layerz_import_branch, layerz_list_transactions |
| Import files and sources | layerz_create_upload_url, layerz_parse_file, layerz_list_integrations, layerz_manage_integration, layerz_list_mappings, layerz_manage_mapping, layerz_external_ref |
| Versions | layerz_history, layerz_diff, layerz_manage_version |
| Share and export | layerz_share_model, layerz_export |
The server also exposes reference resources the agent reads on its own: modeling-guide://reference (session workflow, modeling patterns, validated patch examples), formula-spec://reference (the formula language) and format-spec://reference (number formats).
Using it well
The facts live on the server and travel with the model; the method is in the skills above and in the guide the server serves:
- Conventions travel with the model. Each model carries a FINANCE.md (currency, units, sign convention, how the statements are built), and each workspace carries standing instructions for agents. The agent receives both when it opens a model.
- The modeling guide comes from
layerz_get_conventions { include_guide: true }. Agents read it at the start of a session. - Recipes (prompts for budgets, three-statement models, monthly closes, LBOs) are in the cookbook.
A good first prompt:
Build a three-statement model for a B2B SaaS company: 2 M€ ARR, 40 % growth, 18-month runway. Ask me what you need to know first.
Pricing
Free for one person working alone: unlimited models, MCP and REST API, Excel and JSON export. A paid plan starts when a second person edits the same models. Details at layerz.cc/pricing.
Related
- finance-md: the open standard for financial conventions an agent reads
- cookbook: recipes for financial work with AI agents
- layerz.cc: the web app, where people review, share and collaborate on the same models
Versioning
One version, the server's. The number published to the official MCP Registry (io.github.layerzlabs/layerz, from the server.json of the Layerz code repo) is the only version; plugin.json, .claude-plugin/plugin.json, .cursor-plugin/plugin.json, lhm.plugin.json, the X-Layerz-Client header of the Claude and Cursor MCP entries (the Agent Plugins mcp.json read by ChatGPT and Codex carries none: OpenAI's public submission rejects server headers) and the layerz_version of every skill mirror it, never one of their own. A change to this repository alone (a skill reworded, a tool declared) ships under the current version. The version check workflow (.github/workflows/version-check.yml, on every push and weekly) fails when they disagree or run behind the registry, and only warns when a publish is pending.
Support
Questions or stuck on setup: contact@layerz.cc. Bugs and requests: open an issue in this repository.
License
The contents of this repository (documentation and metadata) are released under the MIT License. The Layerz server and web app are proprietary.
Layerz MCP questions
How do I add Layerz MCP to Claude Code?
Run claude mcp add --transport http layerz-mcp https://layerz.cc/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Layerz MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What can the AI agent do with Layerz?
The agent can find and read models, build and edit structures, manage scenarios and actuals, import files, track versions, and export to Excel.
Does it work with existing AI clients like Claude or Cursor?
Yes, it supports Claude, ChatGPT, Cursor, Claude Code, and many other MCP clients via a hosted endpoint.