Can AI agents automate Carta?

Carta is automatable today through a vendor-hosted MCP server and a scoped OAuth API. This record is the Carta private-capital platform covering cap table, fund administration, and Carta CRM. It is not a separate equity-admin vendor. The API uses OAuth 2.0. A playground app is created in the developer portal and receives a client_id and client_secret. The authorization-code flow redirects the user to https://login.app.carta.com/o/authorize/ and exchanges the code at POST https://login.app.carta.com/o/access_token/ with HTTP Basic client credentials and grant_type AUTHORIZATION_CODE. The code expires after 60 seconds. Access tokens are bearer tokens sent to https://api.carta.com/. The endpoints page says an access token lasts one hour and a refresh token lasts 14 days. Scopes are chosen when the app is registered. Carta also documents plugins for Claude and other MCP clients. The remote server is https://mcp.app.carta.com/mcp over HTTP. Carta Cap Table and Carta Investors are query plugins. Carta CRM supports search, create, and update. All three authenticate with the user's Carta OAuth login, and data access follows that user's permissions. The public github.com/carta/plugins repository is a read-only mirror of those plugins, not the server implementation. Plugin support on the setup page is plugins@carta.com. iPaaS catalogs were not opened. Computer-use viability is unassessed. MCP scores 7 and is the best path because the hosted server and named plugins are the documented agent interface. The API scores 6 because the OAuth flow is documented while this pass did not open the resource catalog behind the scopes.

Best path today: mcp · Overall automatability: 7/10