Fillfolio MCP server
{
"mcpServers": {
"fillfolio": {
"type": "http",
"url": "https://fillfolio.com/api/mcp"
}
}
}{
"mcpServers": {
"fillfolio": {
"type": "http",
"url": "https://fillfolio.com/api/mcp"
}
}
}{
"mcpServers": {
"fillfolio": {
"type": "http",
"url": "https://fillfolio.com/api/mcp"
}
}
}{
"servers": {
"fillfolio": {
"type": "http",
"url": "https://fillfolio.com/api/mcp"
}
}
}{
"mcpServers": {
"fillfolio": {
"type": "http",
"url": "https://fillfolio.com/api/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
This server provides read-only access to Fillfolio, a portfolio net worth tracker. It allows AI assistants to query holdings, cost basis, cash, liabilities, and activity across stocks, ETFs, funds, crypto, and other assets held in a Fillfolio account. It is for developers building AI agents that need to reference portfolio data.
- Query your current net worth, total holdings value, cash balance, and liabilities in one call.
- List all holdings across accounts with cost basis and source (brokerage, wallet, or manual entry).
- Retrieve buy/sell activity and other transactions within a specified date range to analyze investment behavior.
Tools this server exposes
| Tool | Does |
|---|---|
| get_portfolio_summary | Returns net worth, total holdings value, cash, debt, and return availability for a portfolio. |
| list_portfolios | Lists all portfolios associated with the authenticated user. |
| list_holdings | Returns all holdings including stocks, ETFs, funds, crypto, and currency with cost-basis information. |
| list_cash_and_liabilities | Lists cash accounts and liabilities without exposing account numbers. |
| list_activity | Returns buy, sell, and other activity transactions within a specified date range up to 366 days. |
| get_asset | Returns details for a single canonical asset and shows all its holdings across portfolios. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.