Layerz

Connect your AI agent to a spreadsheet it can’t break.

Layerz is an MCP server your Claude agent calls natively. Read model structure, update assumptions, compute projections, export Excel, without re-explaining context every session. Named references, so the formulas hold when the agent touches them.

MCP-compatible · BYOA · Export to standard.xlsx

Claude is powerful — the layer underneath isn't.

You use Claude. You build financial analyses in chat. The next session, you start over.

There's no persistent model structure your agent can navigate. You paste numbers, re-explain assumptions, rebuild context.

A model your agent can actually navigate.

Your agent navigates the model. You review the outputs. The structure persists across sessions.

Variable names, types, formulas, dependencies.

Revenue, EBITDA, cash flow, any output at any period.

Change a growth rate or headcount number, all outputs recompute automatically.

Trigger a clean.xlsx from your agent session.

Your prompts, your data, your environment.

Layerz does not capture your Claude session. Connect your own Claude Max subscription or API key. Layerz is the structured backend, not the middleware.

Supported:Claude (MCP), any MCP-compatible agent, Claude Code.

Add the connector to your Claude configuration.

Your agent now has access to layerz_read, layerz_update_branch, layerz_get_model and more.

Your agent fills a model structure from a prompt — assumptions first, then projections. Change one variable, all outputs update. No re-run.

Define CAC, LTV, payback period once. Query across Claude sessions without rebuilding context.

Run base / upside / downside on a shared model structure. Export any scenario to.xlsx — your colleagues get a clean file, they never see the agent.

Say it in plain English. Your agent does the modeling.

“Show me the revenue assumptions in my latest Layerz model and explain how they drive EBITDA.”

“Raise the churn assumption to 2.5% from March and show me the impact on year-end cash.”

“Create an upside scenario with 20% faster hiring, compare it to base, then export it to Excel.”

Questions, or stuck on setup? Write to[](https://layerz.cc/cdn-cgi/l/email-protection#dab9b5b4aebbb9ae9ab6bba3bfa8a0f4b9b9)<<<[email protected].

Build the structure once. Query it from every session.

MCP-compatible · BYOA · Export to standard.xlsx

Bridge Town is an MCP-native, git-versioned financial modeling platform for FP&A teams and finance leaders. AI agents use Bridge Town tools to create projects, write Python model files, run models in isolated cloud sandboxes, query data, write outputs to Google Sheets, create dashboards, branch scenarios, and collaborate with teammates.

The Capital.com MCP Server lets your AI assistant talk to your trading account directly. Market data, position checks, trade previews – all in plain language, without leaving your AI tool.

Coinrule Agentic Trading MCP enables investors to create, backtest, execute, and manage trading agents through natural language across stocks, crypto and ETFs

Invest with Claude and other AI assistants

Australian Consumer Data Right Product Data

Remote MCP server for historical crypto & prediction-market data: search ~500K instruments, live market stats (OHLC, turnover, spreads, depth, slippage) and tick-data purchase. Keyless for catalog & stats; optional OAuth for account tools. Endpoint: https://cryptostruct.com/mcp

Cross-border debt collection from your AI assistant: check cases, get pricing, submit new cases.

Read-only MCP server for your Evibe investment portfolio + live market data (holdings, performance, dividends, benchmarks, screeners). Works with Claude & ChatGPT.

Financial and quantitative modeling engine for AI agents. Typed, named, deterministic.