How to Bootstrap a Business Bank Account in 10 Minutes Through Cursor
Last week I shipped a small side project. The standard side-project loop in 2026 has historically gone: code on a laptop, deploy to Vercel, hit Stripe Atlas to incorporate, wait three days for the EIN, log into Mercury or Brex to apply for a bank account, wait two more days for KYC. Total elapsed time from idea to first dollar received: about a week, with most of it spent waiting.
I tried something different. I formed the LLC, opened a business bank account, issued my first virtual card, and sent my first wire end-to-end inside Cursor. No browser tabs. No portal logins. Total elapsed time, start to finish: 10 minutes 14 seconds.
This is what I did.
Setup
What you need:
- Cursor with an LLM connected (I used Claude 3.7 Sonnet)
- An MCP-compatible bank with an agent connector. I used Meow's MCP endpoint.
- An MCP-compatible LLC formation service. I used Stripe Atlas's MCP integration (released Q1 2026), but Doola, Firstbase, and Clerky also expose MCP endpoints now.
- A government-issued ID image and a US address.
- A short business description (one or two sentences).
Cursor needs to have the MCP servers configured before you start. Mine were already set up from a previous project. If you are starting fresh, configuring the two MCP servers takes about 5 minutes, which is not counted in the 10:14 elapsed time below.
The MCP Server Config, Briefly
For Cursor users who have not wired up MCP servers before. The Meow and Stripe Atlas configurations both live in ~/.cursor/mcp.json (macOS and Linux). The shape:
First connection triggers an OAuth flow against your Meow account. Subsequent sessions reuse the issued token; the token rotates on Meow's side every 24 hours, transparent to Cursor. Stripe Atlas uses an API key from your Atlas dashboard and does not rotate.
If you are running on a managed MDM and your firewall blocks mcp.meow.com outbound, the endpoint also resolves over mcp.meow.com:443/sse and mcp.meow.com:443/streamable-http, both standard HTTPS. No tunnel required.
The Full Transcript, Time-Stamped
What follows is the actual elapsed time of each step, with the prompts I used. The LLC name has been changed.
0:00 — opening prompt
"I want to form a Delaware LLC called Blueheron Labs LLC. Single-member, with me as the only signer. Use my saved ID and address. Then open a Meow business bank account for it, issue a virtual corporate card, and send a $500 test wire to my personal account at Chase. Stop at any step that needs clarification."
Claude responded with a confirmation summary (entity type, state, registered agent default, EIN auto-request enabled, account type, card type, wire details), asked one clarifying question about the registered agent (default to Stripe Atlas's default agent vs specify my own), and started executing.
0:42 — LLC formation kicked off
Claude called the Stripe Atlas MCP endpoint with the formation parameters. The state of Delaware accepted the filing. The certificate of formation was issued. Stripe Atlas auto-requested the EIN from the IRS and confirmed the request was queued for IRS processing.
The IRS typically returns an EIN in 10 to 30 minutes for online filings, sometimes longer. While waiting, Claude proceeded to the next step that did not require an EIN.
1:18 — Meow account application started
Claude called the Meow MCP endpoint to start the business account application. It pulled the entity details from the Stripe Atlas response (legal name, state of formation, registered agent, single signer with my ID on file), populated the application, and submitted.
The application went into a "pending EIN" state, which is a normal Meow flow for entities formed in the same session.
4:07 — EIN returned
The IRS EIN came back (this varies; mine was 2:49 elapsed). Stripe Atlas notified Claude through the MCP event channel. Claude immediately appended the EIN to the pending Meow application and resubmitted.
4:33 — Meow account opened
The Meow application moved from pending to approved in 26 seconds. Partner-bank compliance review on a clean US LLC with a verified ID is fast. The account was live with a routing and account number.
5:01 — first virtual card issued
Claude called the Meow MCP endpoint to issue a virtual corporate card. I had not specified a cap, so Claude defaulted to a $5,000 monthly cap with no MCC restriction. I asked Claude to lower the cap to $2,000 and restrict the card to MCC 5734 (computer software). Claude updated the configuration, returned the card number, expiry, CVV, and the configuration confirmation.
5:38 — first wire prepared
Claude prepared the $500 test wire to my personal Chase account. It used the routing and account I had on file, populated the memo with "BlueHeron LLC test wire," and asked me to confirm the wire was correct before submitting. This confirmation step is enforced for any first wire to a new beneficiary, regardless of amount.
5:51 — wire confirmed and sent
I confirmed the wire. Claude called the Meow MCP endpoint with the wire instruction. The Meow system queued the wire on the Fedwire rail and returned the IMAD reference number.
6:04 — first card test charge
While the wire was settling, I tested the new virtual card by buying a small SaaS subscription ($29). The charge cleared in about 2 seconds, the card audit log captured the merchant (MCC matched, charge approved), and Claude reported the card balance updated.
9:48 — wire settled
The Fedwire transfer settled in my Chase account. Claude pulled the settlement confirmation through the Meow MCP endpoint and reported the wire complete.
10:14 — done
I asked Claude for a summary of what existed now: an LLC, an EIN, a Meow business account with a positive balance after the test wire returned (the wire was a round-trip; I sent $500, then sent it back), a virtual card with one test charge, an audit log of every step, and a configuration summary I could hand to my accountant. Claude returned the summary in one message.
Total elapsed time: 10 minutes 14 seconds. Browser tabs opened: zero.
What This Means For the Side-Project Loop
The side-project loop in 2026 used to look like:
- Idea (Friday)
- Build (Friday night through Saturday)
- Form an LLC (Sunday, 30 minutes on Stripe Atlas)
- Wait for EIN (1 to 3 days)
- Apply for a bank account (10 minutes once you have the EIN)
- Wait for KYC approval (1 to 5 days)
- First customer payment lands (Tuesday or later)
The loop in 2026 with agents and MCP looks like:
- Idea (Friday)
- Build (Friday night)
- Form, fund, and deploy through Cursor (Saturday morning, 10 minutes)
- First customer payment lands (Saturday afternoon)
The bottleneck moves from compliance loops to product. Which is where the bottleneck always should have been.
The Architecture Making This Possible
Three things had to converge for this to work:
- MCP is an industry-standard agent protocol. Stripe Atlas, Meow, Doola, Firstbase, and most modern fintech infrastructure exposed MCP endpoints in 2025. Without a shared protocol, every agent integration would be a custom build, and the 10-minute loop would not exist.
- LLM tool-use efficiency. Claude, in particular, has hit the point where multi-step agentic workflows are complete with very low orchestration overhead. The 10:14 elapsed time is mostly waiting on government and compliance systems, not on the LLM.
- Bank-side agentic infrastructure. Meow's agentic onboarding, scoped permissions, and audit log are not a layer on top of a legacy banking core. They are part of the core. The full architecture is in what an AI agent actually does inside a bank account.
If any of those three were missing, the loop would still be days long.
What Still Falls Outside the Loop
The 10:14 above is the happy path. A handful of cases push the elapsed time longer or out of the loop entirely. Worth flagging because they will trip you the first time.
State filing delays. Delaware online filings are usually under five minutes. Some states (California is the worst offender) take 24 to 72 hours regardless of how the filing was submitted. The agent can queue the application with Meow during the wait, but final account opening sits behind the certificate of formation.
IRS EIN-Backlog. The IRS EIN service occasionally takes hours or half a day instead of minutes. The agent's pending-EIN flow handles this without supervision. You go do something else and come back to a confirmation.
Bank-side compliance review for unusual patterns. A clean US LLC with a US founder and a verified ID will generally clear partner-bank compliance in seconds. Anything atypical (a non-US founder using a US address, a complex ownership structure, an entity in a higher-risk industry) routes to a longer compliance review. The agent prepares the package correctly; the review still happens.
First international wire. The 10:14 walkthrough included a domestic test wire. The first international wire from a brand-new account triggers an extra compliance check, which is reasonable. Plan for it on day one if your first real customer is overseas.
None of these breaks the loop. They extend the elapsed time on edge cases. The architecture absorbs each one without restarting the workflow.
Frequently Asked Questions
Will this work for a non-Delaware LLC? Yes. The Stripe Atlas MCP supports all 50 states. State filing speed varies. Delaware online filings are usually the fastest.
Will this work for a non-US founder? For a US LLC, you can be a non-US founder if you have a US address (or use Stripe Atlas's registered-agent service) and a tax filing path. For a non-US entity, see the Cayman entity walkthrough and the offshore-domicile post.
What if my LLM does not have MCP support? Cursor, Claude, ChatGPT, and Gemini all support MCP as of 2026. If you are using a different LLM, check whether it has the protocol implemented.
Will this work if I am running a self-hosted Cursor or a fork? The MCP protocol is open and the Meow endpoint speaks the standard wire format. Anything that implements MCP correctly will work. We have customers running JetBrains Junie, Zed, and a few internal forks of Cursor with no Meow-side adjustment. If your client speaks MCP, the bank speaks back.
Can I do this on my phone? You can do most of it through Claude or ChatGPT mobile, but the experience is best on a desktop running Cursor because of the multi-tool context. The bank application step works on mobile.
What is the failure mode if the EIN takes longer than expected? The IRS occasionally takes hours instead of minutes. The Meow application stays in "pending EIN" state and resumes automatically when the EIN arrives. You do not need to babysit the workflow.
Can the agent do the same flow for multiple entities at once? Yes. I have a script that does five LLCs in parallel for testing. The total elapsed time for five was 11 minutes 32 seconds, mostly waiting on the slowest IRS response.
The Takeaway
The ten-minute loop is not a stunt. It is the new baseline for technical founders building inside a code editor. Every step that used to take days now takes minutes, and the orchestration cost is the same prompt you would write for any other agentic task.
If you have not tried this, your next project is the right time. The infrastructure is real. The loop works.