
dev1nagaich/mcp
Developer toolsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
This project turns a pile of financial documents into AI-generated . It is built in two stages:
概要
This project turns a pile of financial documents into AI-generated . It is built in two stages: - a ResearchAgent writes a brief from data retrieved out of a ChromaDB vector store, and a CriticAgent reviews it until it meets a quality checklist. - we take Lab 1's tangled retrieval logic and expose it as a clean of reusable "banking tools." A LangChain + Ollama agent then acts as the , discovering and calling those tools at runtime to build the brief — and reuses the Lab 1 CriticAgent for the final review. Lab 2 (chroma_db/). You do re-run ingest.py. is an open standard from Anthropic that defines how an AI application talks to external tools and data. Think of it as a universal adapter — like USB-C for AI tools. Without MCP, every agent hardcodes its own data access. In Lab 1, the agent reaches into ChromaDB. If a new team wants a loan advisor or a fraud analyst, they must copy and modify the whole codebase.
README
以下は原文 README の抜粋です。原文を見る。
MCP Banking Intelligence Layer (Lab 1 + Lab 2)
This project turns a pile of financial documents into AI-generated investment briefs. It is built in two stages:
- Lab 1 — RAG + Multi-Agent (AutoGen): a
ResearchAgentwrites a brief from data retrieved out of a ChromaDB vector store, and aCriticAgentreviews it until it meets a quality checklist. - Lab 2 — MCP Banking Intelligence Layer: we take Lab 1’s tangled retrieval
logic and expose it as a clean MCP server of reusable “banking tools.”
A LangChain + Ollama agent then acts as the MCP client, discovering and
calling those tools at runtime to build the brief — and reuses the Lab 1
CriticAgentfor the final review.
Lab 2 reuses the Lab 1 data (chroma_db/). You do not re-run ingest.py.
1. What is MCP, and why does it matter?
MCP (Model Context Protocol) is an open standard from Anthropic that defines how an AI application talks to external tools and data. Think of it as a universal adapter — like USB-C for AI tools.
Without MCP, every agent hardcodes its own data access. In Lab 1, the agent reaches directly into ChromaDB. If a new team wants a loan advisor or a fraud analyst, they must copy and modify the whole codebase.
With MCP, the data/tool logic lives behind a standard server interface:
| Concept | What it is | In this lab |
|---|---|---|
| MCP Server | Exposes tools (typed functions) over a standard protocol | server.py — 4 banking tools + 1 bonus |
| MCP Client | Discovers and calls those tools at runtime | client.py — LangChain/Ollama agent |
| Transport | The channel between client and server | stdio (client launches server as a subprocess) |
| Tool | A typed, documented function the LLM can call | search_financials, get_company_profile, … |
Why this is powerful: the agent code never names a database. Tomorrow you can
swap ChromaDB for a live Bloomberg feed by editing only server.py — the agent
in client.py does not change. Tools become modular and shareable across any
MCP-compatible client (Claude Desktop, Cursor, your own agent, etc.).
Key idea: who thinks vs. who fetches
- The server tools are “dumb” on purpose. They only retrieve and process data and return JSON. They never call an LLM.
- The client agent does the thinking. The LLM looks at the available tools, decides which to call (this is not hardcoded), reads the JSON results, and writes the brief.
2. Architecture
Lab 1 pipeline (RAG + AutoGen)
data/financial/*.txt
│ ingest.py (run ONCE)
▼
┌──────────────┐ retriever.py ┌──────────────┐ APPROVED? ┌──────────┐
│ ChromaDB │ ───────────────────────►│ ResearchAgent│ ◄───────────► │ Critic │
│ financial_docs│ (semantic retrieval) │ (drafts) │ feedback │ Agent │
└──────────────┘ └──────────────┘ └──────────┘
インストール
This server does not publish a one-line install command.
Open the repository installation guide MCP 初心者?mcpskill.org のガイドから始めましょう →