Shibui Finance MCP Server

9,900+ US equities, 64 years of prices, financials, technicals, and earnings. Ask in plain English.

Tools

Last Updated

Jun 14, 2026

What is the Shibui Finance MCP Server?

The Shibui Finance MCP server gives AI agents structured, permission-aware access to Shibui Finance through the Model Context Protocol. With 11 pre-built actions, agents can read, create, and update Shibui Finance data on behalf of authorized users.

Willow ships the Shibui Finance MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Shibui Finance is being used by every AI agent in your stack.

Tools

stock_data_query

Stock prices, earnings, revenue, P/E, dividends, filings, screener, comparisons Run a SQL query against 64 years of US stock market data. REQUIRES calling get_database_schema then get_query_patterns first (in that order). This tool has no schema or query patterns built in. Call get_database_schema once, then get_query_patterns once, then use this tool. Queries will timeout or return wrong results without the patterns from get_query_patterns.

get_database_schema

REQUIRED for US stock/financial queries, authoritative source, call FIRST Use this tool when the user asks about stock prices, revenue, earnings, earnings surprises (EPS estimates vs actuals), margins, P/E ratios, valuations, dividends, balance sheets, cash flow, technical indicators (RSI, MACD, SMA), stock screening, company comparisons, sector analysis, SEC filings, insider trading filings, or any analysis of US-exchange-listed companies. Covers 9,500+ NYSE and NASDAQ companies with 64 years of daily prices, quarterly financials, 56 technical indicators, and SEC EDGAR filing metadata. Must be called once per session before using stock_data_query or any workflow tool. After this tool returns, call get_query_patterns before writing any SQL.

get_query_patterns

REQUIRED before stock_data_query, 20 SQL patterns prevent timeouts/wrong results Must be called once per session immediately after get_database_schema. Contains query patterns for time-series selection, return calculations, screening joins, window functions, backtesting, and performance optimization. Time-series queries will timeout or return wrong results without these patterns. After this tool returns, call stock_data_query to execute SQL.

load_fundamental_workflow

Load fundamental workflow for valuation, cash flow, margins, balance sheet. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL when the user asks about company valuation, "is X a good buy", financial health, debt levels, profitability ratios, revenue trends, earnings quality, or any deep-dive company analysis. Can be combined with other workflow tools.

load_technical_workflow

Load technical workflow for RSI, MACD, SMA, Bollinger Bands, entry/exit. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL when the user asks about RSI, MACD, moving averages, Bollinger Bands, support/resistance, overbought/oversold, momentum, trend, chart patterns, golden cross, entry/exit signals, or "is X oversold/overbought". Can be combined with other workflow tools.

load_screening_workflow

Load screening workflow to find, filter, rank stocks, "top N by...". REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL when the user asks to find, screen, rank, or filter stocks — "find stocks that...", "top 10 by...", "best dividend stocks", value/growth screens, sector ranking, or any multi-factor selection. Can be combined with other workflow tools.

load_comparison_workflow

Load comparison workflow for X vs Y, peer analysis, relative valuation. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL when the user asks to compare companies, "X vs Y", "how does X compare to Y", peer benchmarking, sector peers, side-by-side metrics, or relative valuation. Can be combined with other workflow tools.

load_earnings_workflow

Load earnings workflow for EPS surprises, beat/miss, estimates, revenue. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL when the user asks about earnings results, EPS surprises, beat/miss history, "did X beat estimates", quarterly earnings, revenue growth trends, earnings season, or estimates vs actuals. Can be combined with other workflow tools.

load_backtesting_workflow

Load backtesting workflow for signal testing, forward returns, win rates. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL when the user asks to backtest, test a strategy, check "what happens after X", compare forward returns, measure win rates, "is it better to buy when X vs Y", evaluate trading signals historically, or compute any hypothetical return over past data. Contains hard rules for survivorship bias, outlier handling, sampling design, and risk-adjusted metrics (Sharpe, Sortino, drawdown). Can be combined with other workflow tools.

load_filing_workflow

Load filing workflow for SEC / EDGAR, insider trades, 8-K, Form 4, 10-K queries. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL whenever the user asks about filings, "who filed", "filed a form", filing dates, filing activity, SEC filings, EDGAR, insider trading/buys/sells (Form 3/4/5), 8-K events, 10-K/10-Q reports, ownership filings (SC 13G/13D), proxy statements, or any query involving the sec_filings table. Can be combined with other workflow tools.

1–10 of 11 tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

Set Up Your Shibui Finance MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json

{
  "mcpServers": {
    "willow-shibui-finance": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/shibui-finance"
    }
  }
}

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "willow-shibui-finance": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/shibui-finance"
    }
  }
}

Claude Code

CLI

claude mcp add willow-shibui-finance --transport http https://<org>.mcp-s.com/mcp/mcp/shibui-finance

n8n

HTTP Request Node

{
  "url": "https://<org>.mcp-s.com/mcp/mcp/shibui-finance",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for Shibui Finance

Willow adds the layer Shibui Finance and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

Shibui Finance MCP Server FAQ

What is the Shibui Finance MCP server?

The Shibui Finance MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Shibui Finance data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's Shibui Finance MCP server different from the official one?

The official Shibui Finance MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the Shibui Finance MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the Shibui Finance MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Shibui Finance, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which Shibui Finance actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow Shibui Finance MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Shibui Finance MCP locally, you'll see it.

What does the Shibui Finance MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the Shibui Finance MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.