MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
作者提供的说明(英文原文)
Portfolio analytics via the okama library: backtests, Monte Carlo, efficient frontier, PNG charts
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"okama": {
"command": "uvx",
"args": [
"okama-mcp"
]
}
}
}在终端中运行这条命令
claude mcp add okama -- uvx okama-mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"okama": {
"command": "uvx",
"args": [
"okama-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"okama": {
"type": "stdio",
"command": "uvx",
"args": [
"okama-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 mbk-dev 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(3.1.0)于11天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
An MCP server retrieving transcripts of YouTube videos
GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MCP (Model Context Protocol) server that exposes the okama investment portfolio toolkit and okama Planner to AI assistants — Claude Desktop, Claude Code, Cursor, Codex, and any other MCP-compatible client.
With okama-mcp installed, you can ask an AI things like:
*"Backtest a portfolio of 30% gold and 70% real estate over the last 15 years."*
*"Run a Monte Carlo retirement forecast on that portfolio, withdrawing $1,000/month
indexed to inflation, over 25 years."*
*"What's the tangency portfolio of SPY, BND, and GLD with a 3% risk-free rate?"*
…and the AI uses the MCP tools to call okama directly — no Python code needed.
Built on FastMCP. Single codebase, two transports: stdio (for local clients) and streamable-http (for self-hosting). okama-mcp is free and open source. Run it locally or on your own server. The HTTP transport is intended for self-hosting; mcp.okama.io serves the project landing page, not a public MCP endpoint. Client registry tools and Excel exports require a compatible Planner companion and a configured local stdio installation.
Development status (26 October 2026): main prepares MCP 3.1.0 with Planner 0.5.0; neither version has been published yet. Use the source setup below. PyPI still provides MCP 3.0.0 with Planner 0.4.1 and its earlier contracts.
Requires Python ≥ 3.11 (same floor as okama itself); okama ≥ 4.0.0 and okama-planner[reports]>=0.5.0,<0.6.0 are required.
Client data modes (source checkout): local MCP defaults to anonymous reads. client_data_mode_set({"mode":"personal_data"}) enables full client CRUD; {"mode":"anonymous"} disables client writes again. The setting persists per database across connections. uv sync installs a pinned Planner 0.5.0 source revision with the required access API. PyPI still provides Planner 0.4.1, so the prepared release remains blocked until the compatible companion is published; see installation and release gates. Market and finplan_* tools remain available independently. See the 3.0 migration notes for the earlier release behavior.
The easiest way — no clone, no venv — is uv or pipx:
uvx okama-mcp stdio # run straight from PyPI
pipx install okama-mcp
Plain pip works too:
pip install okama-mcp
[!WARNING]
With pip, prefer a dedicated virtual environment: on most modern Linux distros the
system Python is marked externally managed (PEP 668), so
pip installoutside a venv
fails, and a shared environment risks dependency conflicts. In your MCP client config,
point
commandat the absolute path of theokama-mcpscript inside the venv — GUI
clients don't see your shell
PATH.uvxandpipxavoid all of this by isolating
the install automatically.
To work on the code, install from source instead:
git clone https://github.com/mbk-dev/okama-mcp
cd okama-mcp uv python install 3.14 uv sync --python 3.14 --all-groups
Until Planner 0.5.0 is published, tool.uv.sources pins an immutable development companion. Release gates use uv sync --all-groups --no-sources and require published dependencies; no source substitution is used for publication. Remove the development pin after published-pair acceptance passes.
# stdio — for Claude Desktop, Claude Code, Cursor (local IPC)
okama-mcp stdio
okama-mcp http --host 127.0.0.1 --port 8765
When running from a source checkout, prefix each command with uv run. Each worktree has its own .venv; test and dev groups are installed by default. uv.lock is generated locally and is not committed, so fresh checkouts resolve compatible versions independently. Orca runs the bootstrap in orca.yaml before starting the agent; its source MCP configuration uses uv run --no-sync after setup.
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": { "okama": { "command": "uvx", "args": ["okama-mcp", "stdio"] } } }
Restart Claude Desktop; the server appears in the tools menu.
To make the server available in every project (works from any directory):
claude mcp add --scope user okama -- uvx okama-mcp stdio
Developers running from a source checkout can use claude mcp add okama -- uv run okama-mcp stdio from the project root instead.
Or commit a .mcp.json at the project root so the whole team picks it up:
{
"mcpServers": { "okama": { "command": "uvx", "args": ["okama-mcp", "stdio"] } } }
Add the server to .cursor/mcp.json in your project (or ~/.cursor/mcp.json to make it global):
{
"mcpServers": { "okama": { "command": "uvx", "args": ["okama-mcp", "stdio"] } } }
Add the server with one command:
codex mcp add okama -- uvx okama-mcp stdio
Or declare it in ~/.codex/config.toml (or a project-scoped .codex/config.toml in trusted projects):
[mcp_servers.okama]
command = "uvx" args = ["okama-mcp", "stdio"]
The Codex CLI, desktop app, and IDE extension share this configuration — set it up once and it works in all three.
Run okama-mcp on your own server and share it across your MCP clients:
okama-mcp http --host 127.0.0.1 --port 8765 --path /mcp
(From source: uv run okama-mcp http ...)
Then point your MCP client at http:// :8765/mcp. For a production setup put nginx + TLS in front; ready-made examples live in deploy/:
deploy/systemd/okama-mcp.service — systemd unit (hardened, runs as a dedicated user)deploy/nginx/self-hosted.conf — nginx vhost: TLS, SSE-friendly proxying of /mcpThe server is open by design — free to run, no registration. If your instance must not be public, restrict access at the nginx level (allow-list, VPN, or HTTP basic auth).
A multi-stage financial plan (contribute $1,000/month for 20 years into a 70/30 SPY/AGG portfolio, then withdraw $6,000/month indexed to inflation for 25 years), a Monte Carlo retirement forecast (30% gold / 70% real estate, withdrawing $1,000/month indexed to inflation over 25 years) and the efficient frontier of SPY/BND/GLD:
Financial tools are stateless — pass the full portfolio specification with every call. Optional local client tools use stable registry codes and a persistent, database-scoped access mode. Client creation is not idempotent: inspect the registry before retrying an ambiguous creation result. The server caches expensive okama objects (Portfolio, EfficientFrontier) by content hash, so repeated calls on the same spec are fast.
Nested portfolios. Wherever a list of assets is accepted — the assets field of PortfolioSpec/FrontierSpec, or the portfolios argument on the comparison tools — an entry may be a ticker string or a nested portfolio object (the same spec shape). This lets you treat a whole portfolio as a single component: e.g. compare a 60/40 portfolio against gold, or put a sub-portfolio on the efficient frontier.
| Tool | Purpose | ||
|---|---|---|---|
search_assets(query="", namespace?, asset_type?, oldest_first?, limit=50, offset=0) | Search by name / local name / ticker / ISIN, with exact identifiers and names ranked first; follow next_offset while has_more is true. Filter by okama type and sort by first_date; for example, namespace="MOEX", asset_type="ETF", oldest_first=true, limit=5 finds the five oldest MOEX-listed BPIFs. | ||
| `list_namespaces(kind="all"\ | "assets"\ | "macro")` | Show namespace descriptions plus usage: asset/macro classification, support for asset returns, and available MCP tools. |
get_asset_info(symbol) | Metadata for one symbol — name, country, currency, type, date range. |
| Tool | Purpose |
|---|---|
get_asset_history(symbol, kind, first_date?, last_date?) | Time series for one asset. kind ∈ {close_monthly, close_daily, adj_close, ror, dividends}. |
compare_assets(symbols, ccy, ..., portfolios?, rf_return?, t_return?) | Side-by-side statistics (describe() table: CAGR, risk, drawdowns by period) plus Sharpe & Sortino per asset. |
get_correlations(symbols, ccy, ..., portfolios?) | Correlation matrix of monthly returns. |
get_rolling_risk(symbols, ccy, window_months=12, ..., portfolios?) | Rolling annualized risk per asset. |
get_asset_returns(symbols, ccy, ..., portfolios?, period?, real=False) | Return metrics per asset: CAGR, cumulative return, mean / real mean return, monthly geometric mean, annual returns table. With inflation=False, nominal metrics remain available and real_mean_return is null; real=True requires inflation=True. |
get_rolling_returns(symbols, ccy, window_months=12, real=False, ..., portfolios?) | Rolling CAGR and rolling cumulative return per asset. |
get_benchmark_metrics(benchmark, symbols, ccy, ..., portfolios?, rolling_window?) | Beta, correlation, annualized tracking difference and tracking error of each asset vs a benchmark/index. |
get_dividend_info(symbols, ccy, ...) | LTM dividend yield, 5y mean yield, paying/growing streaks per asset. |
| Tool | Purpose |
|---|---|
analyze_portfolio(portfolio, rf_return=0, t_return=0) | Headline metrics (CAGR, annual mean/risk, Sharpe, Sortino) + full describe() for a PortfolioSpec. |
get_portfolio_drawdowns(portfolio) | Drawdown time series + max drawdown / recovery period. |
get_portfolio_var_cvar(portfolio, time_frame=12, level=1) | Historical Value at Risk and CVaR. |
get_portfolio_wealth_index(portfolio, full=False) | Wealth-index series (cumulative growth of 1000). |
get_rolling_cagr(portfolio, window_months=12, real=False) | Rolling CAGR time series (optionally inflation-adjusted). |
get_cagr_probability(portfolio, years, cagr_target) | Historical probability of CAGR below a target (e.g. of a loss) over N-year periods. |
| Tool | Purpose |
|---|---|
monte_carlo_forecast(portfolio, mc, cashflow) | Forward simulation with one of five cash-flow strategies (indexation, percentage, time_series, vanguard, cut_if_drawdown). Returns percentile wealth bands, terminal-wealth stats, survival metrics. Includes the money-weighted IRR distribution (percentiles + mean). |
get_portfolio_irr(portfolio, cashflow) | Historical money-weighted return (IRR) for a contribution/withdrawal plan. |
| `find_the_largest_withdrawa
只显示了开头部分;其余内容请在仓库中阅读