Connectors / Product Development
Product Development MCP connectors for Claude, ChatGPT and Cursor
5+ Product Development connectors in the catalog, each behind the same governed MCP endpoint as everything else in Elaichi.
https://api.elaichi.ai/mcp
The same for every user.
-
Their own access. An agent never gets more than the person it acts for.
-
One connection, every client. Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.
The connectors
Product Development connectors in the catalog
Connect one and your whole team reaches it, each inside the access they already have, without anyone handling a credential.
5 connectors
-
AppFollow API key 43 tools
-
Chameleon API key 97 tools
-
Cortex API key 494 tools
-
Forecast API key 324 tools
-
Procore Bring your own OAuth app 125 tools
No Product Development connector by that name
It may sit under another category, or not be in the catalog yet — any documented API can become a connector.
In practice
What teams do with Product Development connectors
Drawn from the connector pages in this category, so every line describes something one of these connectors actually does.
Finance
-
Keep exchange rates current every month
Update the exchange rates Forecast uses for multi-currency projects when the month closes, and check which rates exist without opening the settings pages.
-
Add budget line items from an estimate
Paste the lines from an approved estimate and have them created as budget line items on the right Procore project, then check the budget totals.
-
Lock a budget once it is approved
When the owner signs off, lock the Procore budget so nobody adjusts it, and unlock it later when a change order comes through.
Engineering
-
Catch the catalog up after a migration
When a system is retired or split, archive the old Cortex entities and unarchive the ones coming back, in one plain request rather than a dozen clicks.
-
Link crash complaints to the bug tracker
Find reviews that mention a crash or a broken screen, attach a bug tracker reference to each one in AppFollow, and add a note so the next person knows it is already being looked at.
Operations
-
Clean up company contacts in bulk
Fix titles, emails and ownership across dozens of Forecast company contacts at once, and remove the ones that have gone stale.
-
Check reply speed across apps
Ask how many reviews got a reply last month and how long it took, per app, then set up new apps, collections, and user accounts in AppFollow as the team grows.
Product
-
See how a product tour is performing
Ask which steps of your onboarding tour people finish and where they stop, pulled straight from Chameleon tour interactions without opening the Chameleon dashboard.
-
Read the week's review themes
Ask for the AI summary of reviews on a given app and see which complaints and requests are growing. Check the semantic tags to find out whether sign-in, crashes, or pricing is driving the noise.
Once it is connected
Things to ask
Each of these is answered against the access the person asking already has, in the Product Development account you connected.
-
Summarize this week's one-star reviews for our iOS app
-
Which steps of the onboarding tour do people drop off at?
-
Which Cortex catalog entities have no owner set?
-
Create a client called Northwind and add its two contacts
-
List open projects under Acme Builders in Procore
The tools
What an agent can call in Product Development
- Connectors
- 5+
- Tools
- 1,083
- Hosted sign-in
- 0
in the Product Development catalog
callable the moment you connect
connect with nothing to register
Of those 1,083 tools, 8% delete something. Restricting an agent to reads is not a promise here, it is 333 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.
- Read 31%
- 333 tools · list, get, search
- Write 19%
- 204 tools · create, update, send
- Delete 8%
- 82 tools · delete, remove, archive
- Other 43%
- 464 tools · vendor-specific verbs
One endpoint
https://api.elaichi.ai/mcp
Every connector above answers here.
Every Product Development connector, by depth
Tool counts are what the connector exposes today; the split is what those tools do.
Hosted sign-in takes a partnership with each vendor, and more are in progress. Until one lands, Your own app means the connector works today — you register an OAuth app once and connect. API key and App credentials mean an admin pastes them once, with nothing to register.
FAQ
Frequently asked questions
How many Product Development connectors does Elaichi have?
5+ Product Development connectors are in the catalog today, and the list grows as connectors are added. Each one arrives as a set of MCP tools an agent can call through https://api.elaichi.ai/mcp.
Can Claude, ChatGPT and Cursor all use Product Development connectors?
Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent all connect to that same address with OAuth. Connecting a Product Development account once makes it reachable from every one of them.
Do Product Development connectors work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Product Development connectors are reached over the same MCP endpoint every client uses, so anything that speaks MCP can call them — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor and the Elaichi Agent. There is no per-client setup beyond pointing the client at https://api.elaichi.ai/mcp.
Do Product Development connectors need me to bring my own OAuth app?
Most do not. 4 of the Product Development connectors connect with an API key or app credentials that an admin pastes once, with no app to register. 1 asks you to bring your own OAuth app: you register it once with the vendor and connect. Hosted sign-in for those is in progress, a vendor partnership at a time, and when one lands the only thing that changes is that the registration step goes away. Each connector's page says which it is before you start.
Can I stop an agent from writing to Product Development tools?
Yes. Tool restrictions apply at role and individual level, and a restricted tool is never advertised to the model, so it cannot be called or guessed at from the tool list. Read-only access to a Product Development connector is a matter of allowing the reads and leaving the writes out.
Put Product Development connectors in front of your team
14 days on Gold, no credit card. Connect one and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.