Freshsales API vs Twenty API + MCP

Freshsales API

Contact upsert and bulk upsert of up to 100 records make creates safe to retry. No MCP server for Freshsales.

Twenty API + MCP

Six MCP meta-tools by default with schemas loaded on demand, and ?mode=direct for clients that load lazily. No status page found.

Freshsales API

1. Build the base URL from the bundle alias shown under the API key, https://<alias>.myfreshworks.com/crm/sales/api/
2. Use /api/contacts/upsert rather than create, so a retry updates instead of duplicating
3. Budget calls, since 1,000 an hour covers the whole account and 429s carry no Retry-After
4. Add include=owner,sales_accounts to pull related records in one call
5. Expect to see only what the key owner's role can see

Twenty API + MCP

1. Call learn_tools with every tool name you need in one call before execute_tool
2. Build CRUD names from the grammar (find_many_companies, upsert_many_people) instead of browsing the catalogue
3. Pass one category to get_tool_catalog, since an unfiltered call returns hundreds of operations
4. Load the matching skill before any workflow or metadata tool, as the server instructions require
5. Batch up to 60 records a call to stay inside 100 requests a minute