AI Portfolio Tracker: Why Portico’s MCP Bet Matters for Investors

An AI portfolio tracker becomes genuinely useful when it does more than display a chart: it should answer questions grounded in the investor’s own transaction history. That is the promise behind Portico, an early-stage portfolio product whose creator says it combines portfolio accounting with a Model Context Protocol (MCP) server so people can ask AI assistants questions about holdings, realized gains, and dividend income.

The idea surfaced in a post on Reddit’s r/SaaS community, where the builder described frustration with Yahoo Finance’s portfolio-tracking experience and the inability to connect an LLM directly to personal portfolio data. Portico is still in an allowlist phase rather than broadly open for signups, but its product direction is worth watching because it illustrates where AI-native personal-finance software may be headed. (reddit.com)

What Portico is trying to build

Portico is being positioned as a portfolio tracker for people who want both conventional investment reporting and an AI interface over their own data. According to the founder’s Reddit post, the product is being built around a few practical capabilities: CSV imports, FIFO cost-basis calculations, realized profit-and-loss reporting, and multi-currency handling.

The attention-grabbing feature is an MCP server. Instead of forcing an investor to manually filter transactions, calculate a period, and inspect an asset page, Portico’s concept is to let a connected assistant such as Claude or a development environment such as Cursor call tools against the portfolio dataset. The example questions are specific and grounded in records: what were the realized gains on a given ticker this year, or how much dividend income arrived in the last quarter?

That distinction matters. Plenty of financial apps can place a chatbot beside market commentary. An AI portfolio tracker with transaction-level access aims to let the model retrieve and reason over the investor’s actual positions, lots, sales, currencies, and distributions. The model is not valuable because it can predict the market; it is valuable because it can make a complicated personal ledger easier to interrogate.

Portico’s public pitch should still be treated as an early product claim, not as proof that every listed import, calculation, or integration is already production-ready. The founder explicitly characterized the project as rough and said access would be opened in small batches to handle feedback and bug reports. (reddit.com)

Why an AI portfolio tracker is different from a portfolio dashboard

Traditional portfolio dashboards answer a predictable set of questions: current value, daily movement, allocation, benchmark performance, dividends, and perhaps unrealized gains. Those are important, but they require the product team to anticipate every useful view in advance.

A conversational layer changes the interface from predefined dashboard navigation to intent-based analysis. An investor may want to ask:

• “How much of my gain this year came from realized sales rather than price appreciation?”
• “Show the purchases that created my remaining cost basis in this ETF.”
• “What dividends did I receive in Canadian dollars, and what were they worth in U.S. dollars on payment dates?”
• “Which sales were short-term versus long-term under my selected accounting assumptions?”
• “Compare my portfolio’s cash income in the last two quarters.”

These are not exotic data-science tasks. They are questions that people already ask while preparing taxes, rebalancing, reviewing a strategy, or reconciling accounts. But getting reliable answers usually means exporting broker data into spreadsheets, checking lot history, and manually applying filters.

The best version of an AI portfolio tracker does not replace the underlying ledger. It makes the ledger more accessible. In practical terms, that means a response should be traceable back to transactions and calculation rules rather than delivered as an opaque paragraph from a model.

The real interface shift: from screens to questions

Dashboards force users to learn the product’s taxonomy. They ask, “Which screen contains the answer?” Conversational systems invite users to state the business question directly.

This is a familiar shift in other software categories. Analysts use natural-language interfaces to query data warehouses; support teams search knowledge bases through assistants; developers ask coding agents to inspect a repository. Personal investing is a logical next candidate because portfolio records contain structured data but are often difficult for an individual to query across brokers and currencies.

The catch is that finance has a much lower tolerance for a plausible but wrong answer. A conversational response that incorrectly summarizes a movie plot is inconvenient. A response that mistakes unrealized appreciation for realized gain, or uses the wrong exchange-rate convention, can mislead an investor’s decisions or tax preparation.

Why MCP is the strategic feature, not a novelty checkbox

MCP is an open standard for connecting AI applications to external data sources, tools, and workflows. In the protocol’s client-server architecture, an AI host connects to an MCP server, which can expose tools and resources the host can use. The official MCP documentation describes this as a standardized way for AI applications to access external systems rather than requiring a bespoke integration for each assistant. (modelcontextprotocol.io)

For Portico, that means the portfolio product could become a data-and-tools layer that works across compatible AI clients. The founder specifically mentioned Claude and Cursor, but the broader design principle is more important than any one client: build the portfolio connection once, then make it available wherever a user already works with an MCP-capable assistant. (reddit.com)

Why this approach is more durable than adding a generic chat box

A generic in-app chat feature typically has a narrow role. It may answer support questions, summarize a dashboard, or send prompts to one chosen model provider. An MCP server potentially creates a more modular arrangement:

1. The portfolio app owns data normalization and calculation logic. It knows transactions, holdings, lots, currencies, and import mappings.
2. The MCP layer exposes constrained capabilities. For example, a tool might return realized gains for a date range, list taxable events, or calculate dividend income by currency.
3. The AI client interprets the user’s request. It decides which permitted tools to call and how to explain the resulting data.
4. The user works in a familiar interface. The question can be asked in an assistant or development environment they already use.

This separation is appealing for builders. The portfolio company does not need to become the world’s best model vendor, and the AI client does not need to understand every broker export format or cost-basis edge case.

MCP’s expanding ecosystem reinforces why a small product might choose this architecture. The protocol’s official documentation says it is supported by a broad range of AI assistants and developer tools, while the project also maintains an official registry for discovering MCP servers. (modelcontextprotocol.io)

MCP does not automatically make answers trustworthy

The protocol is an integration mechanism, not an accuracy guarantee. An MCP-enabled portfolio assistant can still produce a weak answer if the source records are incomplete, the tool definition is vague, the model misunderstands the question, or the app’s calculations do not reflect an investor’s chosen tax-lot method.

That is why the best finance-focused MCP tools should return structured evidence along with prose: the date range used, accounts included, currencies, lots sold, calculation methodology, transaction count, and any exclusions. If the assistant says realized gain was $4,200, a user should be able to inspect how that number was derived.

FIFO cost basis is more consequential than it sounds

One of Portico’s stated differentiators is FIFO cost basis for realized P&L rather than average cost. That sounds like an accounting implementation detail, but it is central to whether performance and tax-oriented reports match the user’s expectations.

FIFO, or first in, first out, treats the earliest acquired shares as the shares sold when specific lots cannot be adequately identified. In the United States, the IRS explains that when an investor cannot adequately identify shares purchased at different times and prices, the basis of the earliest acquired shares is used first; it also notes that average-basis treatment is generally not available for stocks and bonds outside certain mutual-fund and dividend-reinvestment-plan situations. (irs.gov)

A simple example of why average cost can mislead

Imagine an investor buys 10 shares at $50 and later buys 10 more at $100. The total holding is 20 shares with a $75 average cost.

If the investor sells 10 shares at $120, average cost would report a $450 gain: 10 × ($120 − $75). Under FIFO, however, the sale is associated with the first 10 shares purchased at $50, producing a $700 gain. The gap is large, and it can affect both reported realized performance and potential tax analysis.

An app that only shows average cost can still be useful for a high-level portfolio snapshot. But it may not answer the question an investor is really asking after a sale: which lots were disposed of, what was their adjusted basis, and how did the result split between short-term and long-term treatment?

The IRS also emphasizes that basis can require adjustments, including for corporate actions such as stock splits. Investors who bought shares in separate lots must track those lots through a split, preserving total basis while changing per-share basis. (irs.gov)

What a serious lot engine needs beyond FIFO

FIFO is a solid baseline, but robust portfolio accounting is full of exceptions. A mature AI portfolio tracker eventually needs clear behavior around:

• Specific-lot identification where the investor and broker have properly selected specific shares.
• Stock splits, reverse splits, mergers, spin-offs, and cash-in-lieu events.
• Dividend reinvestment, where each reinvested amount can create a new lot.
• Fees, commissions, and other basis adjustments where applicable.
• Partial fills, fractional shares, and transfers between accounts.
• Wash sales and other jurisdiction-specific tax rules.
• Mutual funds and securities for which average-basis elections may apply.

This is not a criticism unique to Portico. It is the standard every product in the category eventually faces. The value of Portico’s early emphasis on FIFO is that it begins with transaction history and realized events instead of treating portfolio value as the only important number.

Multi-currency support is a test of whether the product understands real portfolios

Multi-currency investing creates an especially revealing product challenge. A user may hold U.S. stocks in a Canadian account, receive dividends in a different currency, make contributions from another currency, and want performance reported in a home currency.

A simple dashboard can convert today’s account value using a current foreign-exchange rate. That may be appropriate for a current-value view, but it is not enough for historical analysis. Realized gain, dividend income, return calculations, and cash-flow reporting can depend on which date’s exchange rate is used and whether the user wants native-currency, reporting-currency, or tax-reporting-currency results.

Portico’s founder says the product handles multi-currency accounts with currency conversions. That is promising, but users should evaluate the exact conventions before relying on the outputs: source of exchange rates, timestamp, treatment of fees, handling of currency cash balances, and whether reports preserve both the local amount and converted amount. (reddit.com)

Questions an investor should ask a multi-currency tracker

Before importing data into any tool, users should be able to get direct answers to the following:

1. What is my portfolio’s base or reporting currency?
2. Which exchange rate is used for each transaction and income event?
3. Does the app preserve original transaction currency alongside converted values?
4. How are transfers, deposits, withdrawals, and FX conversions represented?
5. Can reports distinguish security performance from currency movement?
6. Are tax-oriented reports designed for my jurisdiction, or only for general portfolio visibility?

For globally diversified investors, this is not merely a feature-comparison checkbox. Currency treatment can materially change the narrative. A stock may have risen in its local market while the investor’s home-currency return was weaker because of foreign-exchange movement—or vice versa.

CSV import is the unglamorous feature that determines adoption

The founder says Portico currently supports CSV imports from Yahoo Finance and Wealthsimple, with Robinhood and other imports planned. That is strategically sensible because portfolio tracking products rarely win by asking users to rebuild years of history manually. (reddit.com)

Import is not simply a file-upload feature. It is a data-normalization problem. Broker CSVs differ in column names, date formats, transaction labels, treatment of cash, signs for buys and sells, fee reporting, symbols, currencies, and corporate actions. A tool that handles a clean U.S. equity export may fail on options, fractional shares, international tickers, transferred positions, or reinvested distributions.

What makes an import workflow trustworthy

An AI-native tracker should not hide import logic behind a single “success” message. It should make reconciliation visible. A strong workflow includes:

• A preview of mapped columns and detected transaction types.
• Explicit warnings for rows that could not be classified.
• Duplicate detection and a clear import history.
• A before-and-after reconciliation of holdings and cash.
• The ability to correct a transaction without re-uploading an entire file.
• A record of any normalization or conversion performed by the app.

For founders, this is a useful product lesson: automation is valuable only when users can audit it. The more consequential the data, the more important it is to show the intermediate steps.

Portico’s staged rollout is arguably the right response to this complexity. Broker imports produce edge cases that no internal test set fully captures. Limiting initial access lets a small team collect real-world files, improve parsers, and learn which brokers matter most to prospective users—provided it communicates clearly about what is supported and what is not. (reddit.com)

The Reddit response reveals an early validation opportunity, not product-market fit

The visible community reaction provided with the original post is limited: a top comment points people to the waitlist signup page. That is not enough evidence to conclude there is broad demand, nor does it tell us whether readers have tested the calculation quality or MCP integration. (reddit.com)

Still, the post identifies a recognizable pain point: investors often accept clunky tools because moving financial history is difficult, while existing tools tend to treat AI access as secondary or absent. The question is whether that pain is sharp enough to overcome the friction of uploading sensitive transaction data to a new service.

For a startup like Portico, meaningful validation will come from behavioral signals rather than waitlist count alone:

• How many approved users finish a clean import?
• How many reconcile their holdings successfully?
• Which natural-language questions do they ask repeatedly?
• Do users return around dividends, earnings, tax season, or rebalancing?
• Are they willing to connect an AI client after learning the security model?
• Do they trust results enough to replace a spreadsheet or incumbent tracker?

The most important metric may be the ratio of questions asked to answers verified. If users ask assistants about their portfolio but routinely check the math elsewhere, the product has convenience but not trust. If they can inspect the cited transactions and confidently act on the answer, it begins to become workflow infrastructure.

Security and privacy are the make-or-break issues for MCP finance tools

The appeal of an AI portfolio tracker is direct access to personal data. That same feature creates the largest risk surface.

Portfolio records can reveal account balances, investing habits, compensation-related equity, employer ties, tax-sensitive events, and geographic or currency exposure. When an AI assistant is allowed to query this information through MCP, users need a precise explanation of what data is shared, with which client, under what authorization, and for how long.

MCP’s architecture involves a host application, client connections, and servers that expose tools and resources. That flexibility is powerful, but it also means users should understand each component in the chain instead of assuming that “MCP-enabled” is a security label. (modelcontextprotocol.io)

A practical trust checklist for users

Before connecting a financial MCP server to an AI client, users should look for these safeguards:

• Least-privilege tool scopes: Can the connection be limited to read-only portfolio queries?
• Explicit consent: Does the user approve the server and understand what each tool can access?
• Clear data boundaries: Are portfolio details sent to the model provider, retained by the tracker, or both?
• Auditability: Is there a history of tool calls, queries, and returned data?
• Revocation: Can access be disconnected immediately, with credentials invalidated?
• Secure authentication: Are tokens encrypted, rotated, and protected from accidental exposure?
• Prompt-injection defenses: Can untrusted content trick an assistant into requesting or disclosing information outside the intended scope?

The product should also distinguish between reading portfolio information and taking actions. A read-only tool that calculates dividend income presents a very different risk profile from one that can place trades, move money, or alter account data. Early products should earn trust with explainable read access before attempting any higher-stakes automation.

Financial answers need provenance, not just confidence

LLMs are effective at translating a human request into a sequence of calculations and explaining results in plain English. They are not inherently reliable accounting engines. That makes the division of labor crucial.

The calculation itself should happen deterministically in Portico’s portfolio engine, not inside the language model’s reasoning. The model should formulate a request such as “calculate realized gain for ticker X from January 1 through December 31 under FIFO,” call a constrained tool, then explain the returned result.

A good answer would include a compact audit trail:

Realized gain for the selected period: $X. This result uses FIFO, includes Y sale transactions, excludes open positions, and is reported in your selected base currency.

It should then offer links or references inside the product to individual lots and transactions. The exact interface can vary, but the principle cannot: every meaningful figure needs a path back to source data.

Tax language needs unusually careful boundaries

A portfolio tracker may help users organize data, but it should not imply that an AI-generated summary is a filed tax return or personalized tax advice. U.S. tax treatment can depend on holding period, basis adjustments, wash-sale rules, account type, specific-lot identification, and other facts not captured by a superficial prompt.

The IRS describes capital gain or loss as the difference between adjusted basis and amount realized, and generally distinguishes short-term from long-term treatment based on whether the asset was held more than one year. Those rules are a reminder that a simple “profit” number may not answer the tax question a user actually has. (irs.gov)

For Portico and similar products, the right product copy is careful: “Here is your estimated calculation based on imported records and selected assumptions,” followed by transparent methodology and an invitation to verify against broker documents or a qualified professional where needed.

Where Portico fits among existing investing tools

Portico is not competing only with Yahoo Finance. It is competing with a mix of spreadsheets, broker dashboards, dedicated performance trackers, tax software, and personal-finance apps.

Each alternative has a different strength:

Portico’s wedge is the combination of transaction-aware accounting and portable AI access. If it executes well, it could become the layer between raw broker exports and the user’s preferred assistant.

That is also a difficult category to win. Users may reasonably prefer established providers for security, broker connections, and historical data reliability. Portico therefore needs to make its advantage tangible: faster answers to real questions, better multi-currency handling, clear reconciliation, and a security posture worthy of sensitive financial information.

What founders can learn from the Portico launch

The broader story is not simply “add MCP to your SaaS.” Portico points to a better product pattern: find a structured dataset users already struggle to interrogate, create reliable domain tools around it, then make those tools available to AI clients.

Start with a narrow, high-value question set

The best first questions are concrete and verifiable. For a portfolio product, that could include realized gains by ticker, dividend income by period, holdings by account, exposure by currency, or a list of lots contributing to a sale.

Avoid starting with vague prompts such as “How should I invest?” That drifts from retrieval and calculation into personalized financial guidance, where model confidence can exceed evidence. A focused product earns trust through accurate answers to questions that have objective, inspectable outputs.

Make the domain model the moat

MCP itself is increasingly standardized and broadly supported. The official MCP project continues to develop the protocol, SDKs, registry, and future security and transport priorities. That means the protocol is unlikely to be a lasting moat on its own. (blog.modelcontextprotocol.io)

The defensible work is the domain model: transaction normalization, lot accounting, currency treatment, reconciliations, permissions, user experience, and trust. In Portico’s case, clean answers depend much more on the quality of its underlying portfolio ledger than on the fact that it can expose a tool to Claude or Cursor.

Treat AI as an interface layer, not a substitute for product design

A chat interface cannot rescue unclear data. It can only make unclear data feel smoother for a moment. Product teams should build standard reports and transparent drill-downs first, then let AI help users reach those views and ask questions the dashboard did not anticipate.

That balance is particularly important when a mobile app enters the roadmap, as Portico’s founder has indicated. Mobile users may want quick answers, but they also need compact proof: a summary, the assumptions, and a route to the source transactions. (reddit.com)

What to watch next from Portico

Portico’s early launch is compelling because it targets a practical problem rather than a speculative one. Investors do not need another generic market chatbot. They need a trustworthy way to ask their own records questions that are currently trapped in broker portals, CSV files, and spreadsheets.

The next milestones worth watching are straightforward:

1. Availability: Whether the waitlist becomes a broadly accessible product and how onboarding works.
2. Import coverage: Which brokers and account types are supported, and how reliably imports reconcile.
3. MCP implementation: Which tools are exposed, whether they are read-only, and what AI clients are supported.
4. Calculation transparency: Whether users can inspect lot-level and currency-level provenance for every answer.
5. Security disclosures: How credentials, data retention, permissions, and client connections are managed.
6. Mobile execution: Whether the planned mobile experience preserves the auditability of desktop analysis.

The original Reddit post has already done one useful thing: it frames a portfolio tracker as a queryable personal data system, not just a graphing utility. That framing is likely to spread across financial software as MCP and other tool-connection patterns mature.

The bigger opportunity: personal finance software as an AI-readable ledger

Portico’s concept hints at a broader shift. The next generation of personal software may be organized less around a collection of screens and more around secure, structured ledgers that an assistant can query with permission.

In that future, the portfolio app is responsible for the truth layer: imports, calculations, rules, data quality, and permissions. The AI assistant is responsible for helping the person ask good questions, navigate complexity, and turn results into understandable summaries.

That division is healthy. It gives users more flexibility without asking them to trust a language model as the system of record. It also gives builders a clear standard: if the assistant disappeared tomorrow, would the underlying application still contain a rigorous, useful, auditable financial ledger? If the answer is yes, AI becomes leverage rather than theater.

Portico is too early to know whether it will become the preferred AI portfolio tracker for investors. But its MCP-first approach captures a genuine opening: people increasingly expect software to answer questions, not merely present menus. In financial products, the winners will be the teams that combine that convenience with careful accounting, transparent evidence, and security practices users can actually trust.

FAQ

What is an AI portfolio tracker?

An AI portfolio tracker combines conventional investment tracking—holdings, transactions, gains, income, and allocation—with an AI interface that can answer questions using the user’s own portfolio data. The reliable version uses deterministic portfolio calculations and lets the AI explain or retrieve the results.

What makes Portico different from a standard portfolio tracker?

Portico’s stated differentiator is an MCP server that can let compatible AI clients query a user’s portfolio data. Its founder also highlights FIFO realized P&L, multi-currency support, and CSV imports from Yahoo Finance and Wealthsimple, with more broker support planned. (reddit.com)

Is FIFO cost basis the same as average cost?

No. FIFO generally treats the earliest shares acquired as the first shares sold when specific lots are not adequately identified. Average cost divides total basis by total shares and can produce a different realized gain or loss; U.S. tax rules limit where average-basis methods may be used. (irs.gov)

Can an AI portfolio tracker provide tax advice?

It can help organize transactions and estimate figures based on imported data, but it should not be treated as personalized tax advice or a substitute for reviewing broker forms and consulting a qualified tax professional. Tax outcomes can depend on facts such as lot selection, holding period, basis adjustments, and jurisdiction-specific rules. (irs.gov)

Is it safe to connect portfolio data to an MCP server?

Safety depends on the implementation and the connected AI client. Look for read-only permissions, clear data-sharing disclosures, secure authentication, revocable access, audit logs, and transaction-level provenance before granting an assistant access to sensitive financial data.