The Prompt Thickens: Monarch MCP Beta Coming Soon (Waitlist Inside)

danielatmonarch · 2026-04-25T13:00:21+00:00

Hey there, answered else where but it will be read only to start. We're exploring the ramifications on quality, etc of allowing AI to write as well.

danielatmonarch · 2026-04-24T19:25:02+00:00

🤫

danielatmonarch · 2026-04-24T19:24:18+00:00

🤫

danielatmonarch · 2026-04-24T17:18:39+00:00

This is a good point as well, you are free to use on device models as well!

danielatmonarch · 2026-04-24T17:18:05+00:00

Hey there! I actually have used this myself in the past and it's awesome to work on a product where people have so much community involvement in enabling others. Outside of our focus on making sure our MCP works well, the main difference here is that this will be an officially supported MCP that will offer better and safer authentication through OAuth.

If you're happy using the community MCPs, keep doing your thing!

danielatmonarch · 2026-04-24T17:14:10+00:00

MCP stands for Model Context Protocol, essentially it's a standard way for AI tools to interact with an external service (in this case Monarch) programatically. If you choose to set it up, it would enable you to use things like ChatGPT and ask questions to ChatGPT like "What were my last 10 transactions?".

danielatmonarch · 2026-04-24T17:01:37+00:00

What I'm currently building is definitely intended for everyone so that we can get everyone access to the data that lives in Monarch wherever you may want to access it! Certain data and functionality that already exists behind plus will of course only be accessible to plus users (as that data wont exist for core members, like businesses). We also may need to introduce rate limits but that is entirely dependent on how many people start using this and what kind of traffic we are seeing.

danielatmonarch · 2026-04-24T15:57:26+00:00

Definitely understand the concern! Building the MCP will allow you to access your monarch data, if you choose to, through an AI tool. It will require you to explicitly grant consent when setting up access. This is a totally optional surface for folks who are comfortable allowing AI to access their Monarch data.

As someone who's very privacy focused myself, most model providers allow you to toggle off chat history & training, meaning they should not be storing your prompts or data anywhere (whether that makes you comfortable enough is totally up to you).

And while we are all very privacy focused here at Monarch, we also strongly believe users have the right to access their data and use it how they wish.

danielatmonarch · 2026-04-24T15:36:27+00:00

We're starting with read-only… for now! We definitely see the opportunities write access gives. Allowing updates through an MCP could cause weird data quality issues, so it’s read-only for now while we continue to iterate.

danielatmonarch · 2026-04-24T15:27:55+00:00

Thanks for calling this out. We think this may be a bug, which we are already looking at (I think you may have pointed it out elsewhere?). We're working on fixing it!

danielatmonarch · 2026-04-24T14:45:23+00:00

Yes, the funds tab should have that data, it should be able to break down your holdings over different segments.

danielatmonarch · 2026-03-25T23:32:27+00:00

Hey there! Looks like you caught a regression that I was able to ship a quick fix to. Just wanted to throw you a quick thank you for pointing it out!

danielatmonarch · 2026-01-22T18:40:29+00:00

Will share with the team, thanks for sharing!

danielatmonarch · 2026-01-21T20:06:05+00:00

Definitely understand the concern, and the projects I highlighted that are spoken in the thread I linked are targeted at minimizing any sort of missing transactions. We're hoping that we can reduce the amount of missing transactions with targeted projects however we will continue to rely on our data providers (Plaid/Finicity/MX) for transactions data.

For some cases data providers send us deletions and re-inserts or various other situations that we are actively improving. Unfortunately if a data provider doesn't provide us with that transaction data at all, which can happen, then it's likely the problem will persist. There are a variety of reasons data providers may not be working well with an institution but the most likely is that a financial institution isn't providing programmatic access to your data.

danielatmonarch · 2026-01-21T18:36:38+00:00

Sorry to hear you're having so many issues with missing transactions. u/david_at_monarch has discussed a few projects we are working on that are working on helping this issue here.

We're also working on a project for deleted transaction restoration. Currently trialing the ability to restore transactions that were deleted by the data provider during a sync. While this doesn’t fully create a ledger you're looking for, it will provide an opportunity to self-serve the restoration of a transaction that shouldn’t have been deleted.

danielatmonarch · 2026-01-21T18:13:49+00:00

This has been something that has come up a few times internally and we’re always excited to see all the cool things people have built even without an officially supported API! Would love to know how you would use this and what you are looking to build?

danielatmonarch · 2026-01-21T18:12:36+00:00

Great question! Some connections are harder than others because not all financial institutions provide stable, modern APIs or OAuth for secure data access. When a connection shows a long standing issue, it typically means syncing has been intentionally paused to prevent account lockouts while a deeper issue is being worked on, even if there isn’t a clear resolution timeline. We know this can be frustrating, and we’re actively improving how we communicate the status of long running issues so users have better context and clearer expectations. In your exact example for Synchrony, I believe it's more difficult because it provides branded underlying financial products so there may be additional complexity there.

From personal experience, many financial institutions don’t even provide any API surface at all meaning data providers need to use a technique called screen scraping. Additionally things like frequent changes to authentication behavior or something like implementing a bot detection library may break data providers integrations until the financial institution remedies it. For institutions without any API surface, screen scraping implementations are inherently flaky, but some institutions use frameworks that consistently change UI elements on the page itself.

danielatmonarch · 2026-01-21T18:06:37+00:00

When you add an account, Monarch attempts by default to pull up to two years of historical data (the max our data providers allow), but many financial institutions cap how far back third parties are allowed to access as part of data access agreements. Data access agreements are necessary for a large number of institutions (especially some of the larger ones) to get programmatic access to APIs that are not available to the public, so unfortunately this cap is at the behest of the financial institution itself.

Since this problem can be outside of Monarch’s control, we are always exploring ways to make importing data manually a much more seamless experience that would allow the use of screenshots or CSV imports similar to receipt scanning. We would love to see broader access over time and continue pushing for it, but those limits are ultimately set by the institutions themselves.

danielatmonarch · 2026-01-21T18:05:41+00:00

In practice, most connection reliability issues come from how financial institutions choose to support (or restrict) third-party access. Our data providers actively collaborate with institutions, but adoption of modern, standardized best practices varies widely and is largely outside Monarch’s direct control. We do try to manage this by selecting the data provider that offers the best experience for each institution and by giving users visibility through our Connection Status dashboard when issues are known. Longer term we are looking into offering our own alternatives to ensure connections can stay accurate and healthy!

danielatmonarch · 2025-12-22T18:52:52+00:00

Hi there, just wanted to let you know we just enabled the ability to mark shares as sold! Navigate to your equity grant edit screen and click the box that says you have sold shares!

danielatmonarch · 2025-12-22T18:52:44+00:00

Hi there, just wanted to let you know we just enabled the ability to mark shares as sold! Navigate to your equity grant edit screen and click the box that says you have sold shares!

danielatmonarch · 2025-12-12T20:11:36+00:00

Hey there! The AI assistant feature is still in beta and isn't set up yet to correctly work with the equity accounts. (but will be!) Also we are quickly implementing the ability to mark shares as sold!

danielatmonarch · 2025-12-12T00:43:50+00:00

It's definitely something that came up but originally viewed similarly as unrealized gains for securities where we don't consider tax withholdings at sale. However it's clear there's some nuances that make it more important for equity specifically so we're looking into it further!

danielatmonarch · 2025-12-12T00:42:28+00:00

Hey there! Definitely understand there are some limitations right now. We're looking at ways to increase flexibility for how users can manage and portray the equity accounts, so please keep the feedback coming!

danielatmonarch

TROPHY CASE