Finance Toolkit
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
作者による説明(英語の原文)
Public read-only Précis Finance MCP demo with synthetic data; no account or credentials required.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
ウェブ、デスクトップ、モバイルのClaudeで使えます:
https://mcp.precis.finance/mcpターミナルでこれを実行します
claude mcp add --transport http precis-finance https://mcp.precis.finance/mcpプロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"precis-finance": {
"url": "https://mcp.precis.finance/mcp"
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"precis-finance": {
"type": "http",
"url": "https://mcp.precis.finance/mcp"
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
ChatGPTがつなげるのは、インターネット上のサーバーだけです:
https://mcp.precis.finance/mcpメニューの名前は、プランや時期によって少し違うことがあります。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
ツールの名前と説明は、サーバーが2026年11月6日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。
precis_orientationCall this first. Returns how to use Précis over this connector: the data model (scenarios, metrics, statements, dimensions), the reporting-tool variants, and how to build charts. Read it before composing queries.
list_scenariosList the available planning scenarios and their status.
list_kpisBrowse the metric catalogue — metric keys, formats, domains, and the dimensions available per metric.
list_inspection_sourcesList the row-level sources available for inspection.
get_inspection_schemaGet the column schema for an inspection source.
inspect_rowsInspect the row-level detail behind a figure, from an enabled inspection source. Returns a capped sample for reasoning plus a grid for the user.
run_statementRun a financial statement — P&L, variance report, or executive summary. Rows are statement lines (Revenue, Direct Cost, Gross Margin, …); columns are scenarios. Supports an optional dimension breakdown (e.g. by period or cost centre). For an unspecified general P&L, prefer `full_
run_statement_dataRun a financial statement — P&L, variance report, or executive summary. Rows are statement lines (Revenue, Direct Cost, Gross Margin, …); columns are scenarios. Supports an optional dimension breakdown (e.g. by period or cost centre). For an unspecified general P&L, prefer `full_
run_metricBreak one or more metrics down by a dimension — revenue by project, utilisation by employee, headcount trends, GL account drill-down. Rows are the dimension; columns are metrics × scenarios. Pass `scenarios` explicitly and give every scenario a concise, user-facing `alias` such a
run_metric_dataBreak one or more metrics down by a dimension — revenue by project, utilisation by employee, headcount trends, GL account drill-down. Rows are the dimension; columns are metrics × scenarios. Pass `scenarios` explicitly and give every scenario a concise, user-facing `alias` such a
search_hierarchySearch the dimension hierarchies (cost centres, accounts, …) to find valid codes and ids before composing a query.
list_dimensionsList the dimensions defined in the model — keys, labels, and kinds (leaf / derived / ragged hierarchy). Catalogue metadata only; use search_hierarchy to list a dimension's members.
list_variantsList the what-if variants of a scenario.
eval_chart_transformCreate a chart from data_refs (an array of snapshot IDs), a bounded JavaScript function, and chart_spec. Supports line, bar, area, waterfall, scatter, horizontal_bar, forecast_line, cohort_heatmap and sparkline_row. Query first and inspect rows; the transform takes one result per
export_datasetExport a previously returned data_ref to json or xlsx without rerunning the query. Use this for standard Excel exports of reports already shown, rather than rebuilding their JSON with Python. Financial XLSX uses shared server formatting and retains source/region metadata for add-
get_file_downloadRenew a download capability for an available, owned artifact.
list_load_historyList data-load attempts from the ingestion audit trail — when each dataset landed, with what status. Answers "is April in yet?" / "when was this data last loaded?".
get_load_statusFetch one data load's full detail by load_id — timestamps, status, rows landed, and any error message.
list_bindingsList the configured data feeds (ingestion bindings) with their schedule — which datasets load, from where, how often.
get_bindingFetch one data feed's full configuration: source, target dataset, schedule, and extract parameters.
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月8日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント precis-finance で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
516ミリ秒で応答(HTTP 200)
サインイン不要
20件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック3項目のうち3項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。
GitHubリポジトリの最終更新は–、最新バージョン(0.4.0)がレジストリに届いたのは一昨日です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ(開発者モードのChatGPTなど)でも使えます。
同じカテゴリには:Finance Toolkit, SolidInvoice, Korea Tax Calculator
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
A read-only, self-hosted Model Context Protocol (MCP) server for financial reporting on Databricks or ClickHouse, built for Financial Planning & Analysis (FP&A) and management reporting. Give Claude, ChatGPT or another MCP-capable client access to governed metrics, financial statements, variance comparisons, row-level drill-down, charts and Excel exports from your own financial data. It is source-available under Elastic License 2.0 and forms the open core of Précis, the Finance Intelligence Platform.
You describe your business metrics once — KPIs, hierarchies, and financial-statement layouts in a YAML catalogue over a semantic layer of plain SQL views, versioned in git — and any MCP-capable client gets consistent, defensible numbers. Use your existing Databricks data model or start a local self-contained service with the bundled ClickHouse engine. Your own financials, not market data.
/excel; enable its OAuth client when you want live read-only workbook functions.Every figure aggregates from the semantic views — account, cost centre, period, scenario — and the measures generic metric layers can't express (a utilisation denominator averaged across periods, re-aggregated by quarter or business unit, with subtotals in the layout) are first-class catalogue definitions.
Connect a remote MCP client to https://mcp.precis.finance/mcp to explore Précis Finance MCP without installing anything or creating an account. The shared server exposes read-only tools over a synthetic finance dataset; it does not contain your financial data. No API key or sign-in is required.
For Claude Code:
claude mcp add --transport http precis-demo https://mcp.precis.finance/mcp
Then ask precis_orientation what the demo supports, or request a P&L with comparatives. See the public demo connection guide for other MCP clients and the limits of this shared instance.
export MCP_DEV_KEY=$(openssl rand -hex 32)
export ARTIFACT_SIGNING_KEY=$(openssl rand -hex 32) docker compose -f deploy/docker-compose.local.yml up -d --build docker compose -f deploy/docker-compose.local.yml exec precis-mcp \ python -m precis_mcp.sample_data # populate the demo model
One stack — the server plus ClickHouse, Postgres and Valkey — a shared dev key, bound to 127.0.0.1. Point any MCP client at http://127.0.0.1:8768/mcp with the dev key as bearer token. For example, with Claude Code:
claude mcp add --transport http precis http://127.0.0.1:8768/mcp \
--header "Authorization: Bearer $MCP_DEV_KEY"
Then ask a finance-specific question to prove this is not a generic SQL MCP: *"Show the P&L for FY2025 with comparatives."* · *"Drill revenue down by cost centre."* · *"Show utilisation by month for the Digital Transformation team."*
Full walkthrough, including the demo data and bringing your own model: docs/getting-started/quickstart.md.
Rather do this on a call? We pair with early adopters to stand Précis Finance MCP up against their own warehouse — precis.finance or hello@precis.finance.
deploy/docker-compose.yml runs the multi-user stack — the open server, PostgreSQL, ClickHouse (if using the bundled deployment), Valkey, artifact storage, and OAuth 2.1 + PKCE sign-in. Deployment is modular along independent axes:
bundled-proxy profile, on by default) terminates TLS with automatic Let's Encrypt certificates from nothing but PRECIS_DOMAIN. The app itself is proxy-agnostic: drop the profile to front it with an ingress you already operate (reference nginx vhost in deploy/nginx/, host helper scripts/install-precis-mcp.sh --nginx)backup compose profile: scheduled bundles (Postgres dump + ClickHouse backup + instance config) to a local volume or S3, with restore and drill commands: docs/operations/backups.md/excel; enable with the bundled Keycloak client or a public client in your external IdP: docs/excel/scripts/deploy-mcp.sh --data-mode ... --auth-mode ... is the friendly front door over the Compose profiles. Every knob is an environment variable: docs/configuration/environment-variables.md.
Your model lives in an instance/ directory — metric catalogue, semantic SQL views, ingestion bindings — and the bundled demo instance shows the shape. Start at docs/configuration/catalogue-and-semantic.md, then docs/configuration/ingestion.md and docs/operations/onboarding-ingestion.md to load your data. For Databricks, see the Databricks schema contract. The developer guide for adding server tools is docs/development/adding-read-tools.md.
Start with the mechanisms, not the promise.
Use your existing Databricks environment as the analytical backend for Précis Finance MCP. Keep your financial data and pipelines in place, without copying the inputs into another analytical database.
Map your data to reporting views and agree the metric and statement definitions; finance can then request a monthly P&L, compare actuals with budget or drill into the drivers of a variance through a compatible MCP client.
What Précis adds alongside Databricks Genie: consistent financial calculations and presentation. Your agreed aggregation rules, statement layouts, comparison columns and number formats carry through each report. The agent requests established financial operations from the reporting engine, reducing repeated query generation and the scope for calculation errors as the investigation develops.
Our FP&A case study: Précis and Databricks Genie compares five financial requests against the same Databricks data, showing the differences in calculation fidelity, financial presentation and waiting time. Précis completed responses in 16–35 seconds, compared with 73–108 seconds for Genie in that session. The study compares the full Précis workspace with the native Genie interface; Finance MCP uses the same reporting engine, while response times depend on the connected client and deployment.
Read the Databricks product update for the broader platform benefits, including approved planning writeback. Précis Finance MCP remains read-only.
Full documentation: docs.precis.finance.
| Area | Start here |
|---|---|
| Getting started | quickstart |
| Deployment | ClickHouse data modes · Databricks setup · OAuth / Keycloak · external IdP recipes |
| Excel |
冒頭だけを表示しています。続きはリポジトリで読めます