MCP App Store
by KeenEthics
Cake Equity icon

Cake Equity MCP Server for ChatGPT

By Cake Equity

Overview

Connect Cake and ChatGPT can read your cap table: shareholders and holdings, share classes, plans and grants, and convertibles. Board prep, pool checks and vesting questions get answered without an export. Read-only. Issuing, editing and deleting stay in the Cake app behind the usual approvals. The server resolves the company from your sign-in, one organization per connection. Cake returns the figures and ChatGPT reports them. The plugin does not model a fundraise, convert a SAFE, price a share, or give tax, legal or accounting advice.

How to connect

  1. ChatGPT: Open the Cake Equity listing in the ChatGPT app directory and choose Connect. ChatGPT listing Cake Equity exposes 5 tools here.

Tools

get_captable_summary

ChatGPT
Totals for the cap table of the company this credential belongs to: shares outstanding, fully diluted total, the breakdown by share class, incentive plans, warrant books, outstanding note principal, reporting currency and the as-of date. Start here before listing shareholders or securities - this returns aggregates, not rows. Takes no arguments: the company is fixed by the credential and cannot be chosen. "Fully diluted shares", "outstanding" and "fully diluted" each mean something specific here that differs from common usage: outstanding is a raw issued-share count, fully diluted shares applies the share class conversion ratio and NEVER convertible note conversion (and for a plan is its WHOLE authorized pool, granted or not), and total fully diluted is the only valid ownership denominator. The plans listed include ESS, whose individual grants cannot be listed; founder vesting is not represented at all, though the shares it vests over are counted as outstanding. Warrant books are returned in their own warrants[] list rather than inside plans[], because a warrant book has no ungranted pool - but their live grants are still part of total_fully_diluted. Returns fully_diluted_breakdown: total_fully_diluted split into issued shares, live plan grants and unissued plan pool, which sum to it exactly. Quote the breakdown before quoting the total - on most cap tables the unissued pool is the largest part, so the total reads as far more shares than the company has issued and the difference is pool nobody holds. Also returns latest_409a: the most recent 409A valuation and the date it is as at, or null when none is recorded. That is the ONLY fair market value per share any tool here returns - list_securities carries strike_price and option_price, but an exercise price and the price paid for an option are not valuations of a share. There is no current price and no company valuation, so do not construct one, and never divide invested by outstanding to manufacture one. It does not say whether that valuation is still current, and it is not a basis for calling a grant underwater: strike prices carry the grant's own currency, which need not be the reporting currency the valuation is in. Three rules hold across every tool here: ownership figures are fractions of 1, never percentages, so multiply by 100 before presenting one as a percentage; total_fully_diluted is the ONLY valid denominator for an ownership percentage, and total_shares_outstanding is the share count, which is neither of those two; and monetary amounts are exact decimal strings, so parse them as numbers rather than reading them as text.

get_vesting_schedule

ChatGPT
The vesting calendar for ONE grant of the company this credential belongs to: the dated tranches Cake computes, in order, with the quantity vesting on each date and the running total. It is a MERGED timeline: every row is a tranche the vesting rule produced, and vested on each row says whether a recorded vesting transaction backs it or it is projection only. The projection does not stop when vesting does - a paused or cancelled grant keeps a calendar that marches on with vested false on every past row, and cumulative climbing regardless. Quote amount_vested for what a holder has, vested for which dates are real, and cumulative for neither. Use this to answer what vests when, and never rebuild a schedule from the cliff, time_based_vesting or milestones strings on list_securities - those are human-readable prose, and a schedule rebuilt from them will not match what Cake computes. security_type must be one of option, rsu, warrant and security_id is the id of a row returned by list_securities; a note carries no vesting schedule. Takes no company argument: the company is fixed by the credential, and a grant belonging to another company does not exist here. Paginated: at most 200 tranches per call (50 by default), and total_entries is the full length of the schedule - if it exceeds the rows you received, follow next_cursor until it is null rather than reporting a partial schedule as the whole one. Dates are the dates Cake holds; they are not adjusted for anything. Milestone-based vesting has no date and cannot appear here: excluded_milestone_events counts what was left out, and a grant with milestones vests more than this calendar shows. Each tranche says whether it actually vested or is only projected; where one is marked tampered the schedule STOPS there, so total_entries counts a calendar that was cut short rather than the whole one.

list_securities

ChatGPT
List securities of the company this credential belongs to, one type per call. security_type is required: "option", "rsu", "warrant" or "note". The types carry different fields - a strike price is meaningless for an RSU, a valuation cap exists only on a note - so ask for the type you want rather than expecting a mixed list. Call get_captable_summary first to see which types this company actually has. Paginated: at most 200 rows per call (50 by default). If next_cursor is not null there are more rows; pass it back as cursor and continue until it is null. A cursor is only valid for the security_type it came from. Takes no company argument: the company is fixed by the credential. ESS grants and founder vesting are NOT listable here: an empty result means they cannot be retrieved, not that the company has none. Every row carries holder_id, the same id list_shareholders returns for that person: join a holder's grants to their shares on it, never on holder_name or holder_email, because a name is not unique and both emails are often empty. Prices, amounts and rates are exact decimal strings; parse them as numbers. Rates and discounts are fractions of 1, not percentages. Never sum these rows to obtain a company total - use get_captable_summary, because a partially paged result silently understates it.

list_shareholders

ChatGPT
List shareholders of the company this credential belongs to, largest holding first, with their holdings broken down by share class. Returns rows, not totals - call get_captable_summary for aggregates. Paginated: at most 200 rows per call (50 by default). If next_cursor is not null there are more rows: pass it back as cursor to continue, and keep going until next_cursor is null. Do not attempt to request every row at once. Takes no company argument: the company is fixed by the credential and cannot be chosen. undiluted_ownership is a fraction of 1: this holder's issued shares over total issued shares, both at face count, and it matches the Undiluted Ownership column of the Cake XLSX export exactly. It is NOT the undiluted column shown in the Cake web app, which divides by the as-converted class total, so those two report different figures for the same holder - if a customer is comparing against the app, say which denominator you used. It is not comparable with fully diluted percentages either. total_invested is an exact decimal string; parse it as a number. Never sum these rows to obtain an company total: a partially paged result silently understates it. COVERAGE: these rows are holders of ISSUED SHARES, not every stakeholder. Someone holding only options, RSUs or warrants and no shares has no row here at all, so a per-holder table built from this tool alone omits them silently - call list_securities for grant holders. fully_diluted_ownership on a row counts that holder's issued shares AND their live grants, so it matches total_fully_diluted_ownership in list_stakeholders for the same holder.

list_stakeholders

ChatGPT
List stakeholders of the company this credential belongs to, largest position first: one row per holder, carrying their issued shares and their live grants as a single fully diluted position. This is the tool to answer "what does this person own" and the only one that returns that figure. list_shareholders covers holders of issued shares and list_securities covers grants; a holder appears in both with a percentage in each, and those two percentages must never be added together - this row is the addition, done where the bases can be reconciled. Returns rows, not totals: call get_captable_summary for aggregates. Paginated: at most 200 rows per call (50 by default). If next_cursor is not null there are more rows: pass it back as cursor and keep going until it is null. Never sum these rows to obtain a company total, because a partially paged result silently understates it. total_fully_diluted_ownership is a fraction of 1, never a percentage: multiply by 100 before presenting one. Takes no company argument: the company is fixed by the credential. COVERAGE: this is not every stakeholder. ESS grants cannot be listed and their granted units are counted in no component of the fully diluted total, so an company with an ESS plan has holders that do not appear here and units that are in no row - say so when its summary shows an ESS plan. Holders of convertible notes and SAFEs are not represented either, because an unconverted note contributes nothing to fully diluted; call list_securities with note for those. An empty result means the data is not available through these tools, never that the company has no stakeholders.

Capabilities

Read Cap TableRead Vesting Schedules

Example Prompts

Click any prompt to copy it.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/cake-equity"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/cake-equity)