--- title: "Simla.com MCP server for AI agents - actionlake" description: "Give Claude 189 Simla.com actions through one MCP server: orders, store, customers, users. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/simla-com updated: 2026-10-10 --- Connectors · CRM & sales # Simla.com MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Simla.com and the rest of your systems. It gives your agent 189 Simla.com actions (86 reads, 90 writes and 13 that wait for a confirmation) and holds the Simla.com credential itself, so the agent never does. It paces Simla.com's limits and records every call. [Connect Simla.com free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "simla.orders.list", intent: "check which Simla.com account is connected" } # Simla: Getting the list of orders matched the specified filter · read · 1 upstream call ``` - 189 actions in one signed file - 86 read look, never change - 90 write create and update - 13 wait for a yes destructive, confirmed first Set up ## Connect Simla.com in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect Simla.com. API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key. - `api_key` Simla API key (Settings > Integration > API keys) - `account_host` Where your Simla.com lives: your account host ``` account { op: "connections.requirements", service: "simla" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "simla.orders.list" } # simla: getting the list of orders matched the specified filter · read · 1 upstream call check { action: "simla.orders.create", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` Simla.com at a glance **Sign-in** API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. **You provide** `api_key` **Setup fields** `account_host` **Limits we pace to** 10 calls a second, per connection **API covered** Simla.com API v5, at your own simla.com address, set when you connect **Built from** Simla.com's documentation, read 21 September 2026[rest-api-docs.simla.com](https://rest-api-docs.simla.com/v5/) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 84 of 86 reads, for up to an hour; a write clears what it affects **Ready-made plans** 9 in the store **Shared entities** 7, so ask can line Simla.com up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in Simla.com. 189 actions in 1 area. Every one carries its effect, so a key can allow the reads and hold the rest. - **86** read look, never change - **90** write create and update - **13** destructive wait for a confirmation 1. ### CRM 189 86 read · 90 write · 13 destructive Simla: Getting the list of orders matched the specified filter · Simla: Getting the list of products and SKU · Simla: Getting the list of customers matched the specified filter · Simla: Getting the list of users matched the specified filter Top actions ## The Simla.com API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 126 of Simla.com's 138 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `simla.orders.list` Simla: Getting the list of orders matched the specified filter | Getting the list of orders matched the specified filter | read | `commerce.order.list` 82 connectors | | `simla.store_products.list` Simla: Getting the list of products and SKU | Getting the list of products and SKU | read | `commerce.product.list` 112 connectors | | `simla.customers.list` Simla: Getting the list of customers matched the specified filter | Getting the list of customers matched the specified filter | read | `crm.contact.list` 177 connectors | | `simla.users.list` Simla: Getting the list of users matched the specified filter | Getting the list of users matched the specified filter | read | `identity.user.list` 474 connectors | | `simla.customers_corporate.list` Simla: Getting the list of corporate customers matched the specified filter | Getting the list of corporate customers matched the specified filter | read | `crm.company.list` 162 connectors | | `simla.orders.create` Simla: Order creation | Order creation | write | `commerce.order.create` 67 connectors | | `simla.tasks.list` Simla: Getting the task list | Getting the task list | read | `work.task.list` 122 connectors | | `simla.customers.create` Simla: Customer creation | Customer creation | write | `crm.contact.create` 161 connectors | | `simla.store_products_batch.create` Simla: Batch adding of products and services | Batch adding of products and services | write | `commerce.product.create` 92 connectors | | `simla.customers_corporate.create` Simla: Corporate customer creation | Corporate customer creation | write | `crm.company.create` 142 connectors | | `simla.users.get` Simla: Getting information on user | Getting information on user | read | `identity.user.get` 399 connectors | | `simla.orders.combine` Simla: Combining of orders | Combining of orders | destructive | this connector | Try it ## Prompts to paste into Claude. Each one names the Simla.com actions it will call, so you know what it reads and what it changes before you send it. 1. Read read Which Simla.com tasks are overdue, and who owns each one? calls `simla.tasks.list` 2. Plan read Report the configured reference catalogue in Simla.com. calls `simla.settings.get` `simla.reference_sites.list` `simla.reference_statuses.list` `simla.reference_delivery_types.list` `simla.reference_payment_types.list` +1 more 3. Plan write Note every customer in a segment in Simla.com. calls `simla.customers.list` `simla.customers.get` `simla.customers_notes.create` `simla.customers_notes.list` 4. Write write Simla: Order creation in Simla.com. Show me exactly what you will send before you save it. calls `simla.orders.create` 5. Across systems read Which Simla.com companies have invoices in ConnectWise PSA, and how many each? calls `simla.customers_corporate.list` `connectwise_manage.invoices.list` Across your systems ## Simla.com, joined to the rest of your business. One `ask` fetches from Simla.com and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row. - Which Simla.com companies have invoices in ConnectWise PSA, and how many each? `simla.customers_corporate.list` + `connectwise_manage.invoices.list`, on `crm.company` · [ConnectWise PSA](https://actionlake.com/connectors/connectwise-psa) - Which Simla.com companies have invoices in NetSuite, and how many each? `simla.customers_corporate.list` + `netsuite.views.invoices`, on `crm.company` · [NetSuite](https://actionlake.com/connectors/netsuite) Also mapped by other connectors `identity.user` **517** `crm.company` **227** `crm.contact` **192** `commerce.product` **109** `work.task` **105** `commerce.order` **86** `comm.call` **33** ask ``` ask { intent: "which Simla.com companies have invoices in ConnectWise PSA, and how many each", steps: [ { action: "simla.customers_corporate.list", as: "co", input: {}, limit: 100, max_pages: 5 }, { action: "connectwise_manage.invoices.list", as: "inv", input: {}, limit: 100, max_pages: 5 }, { join: { left: "co", right: "inv", on: "crm.company", group_by: "co.name", select: ["co.name", "count(inv.id) as invoices"] } } ] } ``` Example. Run it through check first: it validates the steps and prices them, and it is free. The plan store ## Ready-made plans for Simla.com. 9 plans in the store. Install one and your agent runs it by name; the reply says which connections are still missing. A schedule can run a plan on a timetable. There are no triggers or webhooks, by design. 1. ### Report the configured reference catalogue Use it when Someone asks which sites, statuses, delivery types, payment types or stores this account actually has. **Effect** read **Steps** 7 **Install** `simla-reference-catalogue-report` 2. ### Review new orders and open a follow-up task for each Use it when A manager wants recent orders triaged into follow-up tasks. **Effect** write **Steps** 2 · loops **Needs** task text **Install** `simla-order-intake-review` 3. ### Note every customer in a segment Use it when A campaign or incident needs the same note recorded against a group of customers. **Effect** write **Steps** 3 · loops **Needs** note text **Install** `simla-customer-note-sweep` 4. ### Turn missed calls into callback tasks Use it when Missed or unanswered calls from a period need chasing up as callback tasks. **Effect** write **Steps** 3 · loops **Needs** date from and date to **Install** `simla-missed-call-callbacks` 5. ### Upload stock and prices, then verify the offers Use it when Stock levels and prices have changed externally and need pushing into the store with proof they landed. **Effect** write **Steps** 5 **Needs** site, offers and prices **Install** `simla-inventory-price-sync` 6. ### Raise a payment invoice and watch until it is paid Use it when An invoice must be issued and the plan should keep watching until payment arrives. **Effect** write **Steps** 5 **Needs** create invoice and payment **Install** `simla-invoice-payment-watch` 7. ### Credit bonuses to a loyalty account after sign-off Use it when A customer is owed goodwill bonuses and a human must sign off before they are credited. A person decides Credit _amount_ bonuses to loyalty account _account id_. **Effect** write **Steps** 5 **Needs** account id and amount **Install** `simla-loyalty-bonus-credit` 8. ### Create a delivery shipment and confirm it registered Use it when An order is ready to ship and a shipment must be booked with the courier and verified. A person decides Book this shipment with the courier at the quoted delivery cost. **Effect** write **Steps** 5 **Needs** order, delivery type codes and shipment **Install** `simla-shipment-dispatch` 9. ### Delete a batch of cost records after approval Use it when Duplicate or mistaken cost records need removing in bulk and a human must approve the deletion. A person decides Permanently delete _number of delete ids_ cost records from the ledger. This cannot be undone. **Effect** destructive **Steps** 5 **Needs** delete ids **Install** `simla-cost-cleanup` install a plan ``` account { op: "plans.install", slug: "simla-reference-catalogue-report" } # then ask for it by name; a schedule can run it on a timetable ``` Governance for Simla.com ## Destructive actions wait for a yes. 13 Simla.com actions are destructive. These are all of them: - Simla: Combining of orders `simla.orders.combine` - Simla: Combining of corporate customers `simla.customers_corporate.combine` - Simla: Deleting the file `simla.files.delete` - Simla: Cancellation of the integrated delivery `simla.orders_delivery.cancel` - Simla: Note removing `simla.customers_notes.delete` - Simla: Cost removing `simla.costs.delete` - Simla: Batch removing of costs `simla.costs.delete_many` - Simla: Cleaning the current cart of the customer `simla.customer_interaction_cart.clear` - Simla: Payment removing `simla.orders_payments.delete` - Simla: Note removing `simla.customers_corporate_notes.delete` - Simla: Combining of customers `simla.customers.combine` - Simla: Pack removing `simla.orders_packs.delete` - Simla: Deleting a product offer from the customer's list of favorites `simla.customer_interaction_favorites.remove` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do simla.files.delete confirm_policy: **human** Simla: Deleting the file? **intent:** the user asked me to simla: Deleting the file run suspended · waiting for a named person · key _simla-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "simla-agent", allowed_actions: ["simla.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "simla.orders.combine", approver: "lead@example.com" }, { match: "simla.customers_corporate.combine", approver: "lead@example.com" }, { match: "simla.files.delete", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to Simla.com only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What Simla.com costs on actionlake. Every Simla.com action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Simla.com refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 189 Simla.com actions - 33 actions page each page of a long list is one call - 84 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Simla.com action. 189 actions by area: the id your agent calls, what it does, and its effect. **CRM 189** - `simla.api_versions.list` Simla: Getting the list of available api versions read - `simla.costs.create` Simla: Creation of the cost write - `simla.costs.delete` Simla: Cost removing destructive - `simla.costs.delete_many` Simla: Batch removing of costs destructive - `simla.costs.get` Simla: Getting of cost information read - `simla.costs.list` Simla: Getting of the cost list, adequate for the given filter read - `simla.costs.update` Simla: Cost editing write - `simla.costs.upload` Simla: Batch loading of costs write - `simla.credentials.get` Simla: Getting the list of available api methods and stores for current key read - `simla.custom_fields.create` Simla: Custom fields creation write - `simla.custom_fields.get` Simla: Getting information on custom fields read - `simla.custom_fields.list` Simla: Getting the list of custom fields read - `simla.custom_fields.update` Simla: Custom fields editing write - `simla.custom_fields_dictionaries.create` Simla: Directory fields creation write - `simla.custom_fields_dictionaries.get` Simla: Getting information on directory read - `simla.custom_fields_dictionaries.list` Simla: Getting the list of custom directory read - `simla.custom_fields_dictionaries.update` Simla: Directory fields editing write - `simla.customer_interaction_cart.clear` Simla: Cleaning the current cart of the customer destructive - `simla.customer_interaction_cart.get` Simla: Getting the current cart of the customer read - `simla.customer_interaction_cart.set` Simla: Creating or overwriting cart data write - `simla.customer_interaction_favorites.add` Simla: Adding a product offer to the customer's list of favorites write - `simla.customer_interaction_favorites.list` Simla: Getting a list of favorites for the customer read - `simla.customer_interaction_favorites.remove` Simla: Deleting a product offer from the customer's list of favorites destructive - `simla.customers.combine` Simla: Combining of customers destructive - `simla.customers.create` Simla: Customer creation write - `simla.customers.fix_external_ids` Simla: The mass recording of customers external ID write - `simla.customers.get` Simla: Getting information on customer read - `simla.customers.list` Simla: Getting the list of customers matched the specified filter read - `simla.customers.update` Simla: Customer editing write - `simla.customers.upload` Simla: Packet customers uploading write - `simla.customers_corporate.combine` Simla: Combining of corporate customers destructive - `simla.customers_corporate.create` Simla: Corporate customer creation write - `simla.customers_corporate.fix_external_ids` Simla: The mass recording of corporate customers external ID write - `simla.customers_corporate.get` Simla: Getting information on corporate customer read - `simla.customers_corporate.list` Simla: Getting the list of corporate customers matched the specified filter read - `simla.customers_corporate.update` Simla: Corporate customer editing write - `simla.customers_corporate.upload` Simla: Packet corporate customers uploading write - `simla.customers_corporate_addresses.create` Simla: Creating an address for a corporate customer write - `simla.customers_corporate_addresses.list` Simla: List of addresses for a corporate customer read - `simla.customers_corporate_addresses.update` Simla: Editing the address of the corporate customer write - `simla.customers_corporate_companies.create` Simla: Creating a company for a corporate customer write - `simla.customers_corporate_companies.list` Simla: List of companies of a contact person read - `simla.customers_corporate_companies.update` Simla: Editing the company of the corporate customer write - `simla.customers_corporate_contacts.create` Simla: Creating a link between a corporate customer and a contact person write - `simla.customers_corporate_contacts.list` Simla: List of contact persons of the corporate customer read - `simla.customers_corporate_contacts.update` Simla: Editing the link between the corporate customer and the contact person write - `simla.customers_corporate_history.list` Simla: Getting the corporate customer change history read - `simla.customers_corporate_notes.create` Simla: Note creation write - `simla.customers_corporate_notes.delete` Simla: Note removing destructive - `simla.customers_corporate_notes.list` Simla: Getting the notes read - `simla.customers_history.list` Simla: Getting the customer change history read - `simla.customers_notes.create` Simla: Note creation write - `simla.customers_notes.delete` Simla: Note removing destructive - `simla.customers_notes.list` Simla: Getting the notes read - `simla.customers_push_tokens.batch_upsert` Simla: Batch create/edit customer mobile app push tokens write - `simla.customers_push_tokens.list` Simla: Get customer mobile app push token data read - `simla.customers_subscriptions.update` Simla: Subscribe/unsubscribe customer to mailings write - `simla.delivery.calculate` Simla: Calculation of the delivery cost read - `simla.delivery_generic.tracking_update` Simla: Updating of delivery statuses write - `simla.delivery_shipments.create` Simla: Shipment creation write - `simla.delivery_shipments.get` Simla: Getting information on shipment read - `simla.delivery_shipments.list` Simla: Getting the list of shipments to delivery services read - `simla.delivery_shipments.update` Simla: Shipment editing write - `simla.files.delete` Simla: Deleting the file destructive - `simla.files.get` Simla: Getting information about the file read - `simla.files.list` Simla: Getting the list of files according to the selected filter read - `simla.files.update` Simla: Editing the file write - `simla.integration_modules.get` Simla: Getting the integration module read - `simla.integration_modules.update` Simla: Integration module creation/editing write - `simla.integration_modules.update_scopes` Simla: Updating permissions for the API key write - `simla.loyalty.calculate` Simla: Calculation of a maximum discount read - `simla.loyalty_account.activate` Simla: Activation of participation in the loyalty program write - `simla.loyalty_account.create` Simla: Adding a customer to the loyalty program write - `simla.loyalty_account.get` Simla: Getting information about participation in the loyalty program read - `simla.loyalty_account.update` Simla: Editing participation in the loyalty program write - `simla.loyalty_account_bonus.charge` Simla: Charging off bonuses to a loyalty program participant write - `simla.loyalty_account_bonus.credit` Simla: Accrual of bonuses for participation in the loyalty program write - `simla.loyalty_account_bonus_details.list` Simla: Getting details on the bonus account read - `simla.loyalty_account_bonus_operations.list` Simla: History of the bonus account for a specific participation read - `simla.loyalty_accounts.list` Simla: List participation in the loyalty program read - `simla.loyalty_bonus_operations.list` Simla: History of the bonus account for all participations read - `simla.loyalty_loyalties.get` Simla: Getting information about the loyalty program read - `simla.loyalty_loyalties.list` Simla: List of loyalty programs read - `simla.notifications.send` Simla: Sending notification write - `simla.orders.combine` Simla: Combining of orders destructive - `simla.orders.create` Simla: Order creation write - `simla.orders.fix_external_ids` Simla: The mass recording of orders external ID write - `simla.orders.get` Simla: Getting information on order read - `simla.orders.list` Simla: Getting the list of orders matched the specified filter read - `simla.orders.update` Simla: Order editing write - `simla.orders.upload` Simla: Packet orders uploading write - `simla.orders_delivery.cancel` Simla: Cancellation of the integrated delivery destructive - `simla.orders_history.list` Simla: Getting the order change history read - `simla.orders_links.create` Simla: Creating a link between orders write - `simla.orders_loyalty.apply` Simla: Applying bonuses according to the loyalty program write - `simla.orders_loyalty.cancel_bonus_operations` Simla: Cancellation of bonus operations on the Loyalty Program write - `simla.orders_packs.create` Simla: Pack creation write - `simla.orders_packs.delete` Simla: Pack removing destructive - `simla.orders_packs.get` Simla: Getting information on pack read - `simla.orders_packs.list` Simla: Getting the list of packs matched the specified filter read - `simla.orders_packs.update` Simla: Pack editing write - `simla.orders_packs_history.list` Simla: Getting the history of order packing read - `simla.orders_payments.create` Simla: Payment creation write - `simla.orders_payments.delete` Simla: Payment removing destructive - `simla.orders_payments.update` Simla: Payment editing write - `simla.orders_statuses.list` Simla: Getting the list of order statuses read - `simla.payment_invoices.check` Simla: Checking the invoice read - `simla.payment_invoices.create` Simla: Creating an invoice write - `simla.payment_invoices.get` Simla: Get the invoice read - `simla.payment_invoices.import` Simla: Import the invoice write - `simla.payment_invoices.update` Simla: Changing the invoice write - `simla.reference_cost_groups.list` Simla: Getting of the costs groups list read - `simla.reference_cost_groups.update` Simla: Editing costs groups write - `simla.reference_cost_items.list` Simla: Getting of the costs items list read - `simla.reference_cost_items.update` Simla: Editing costs items write - `simla.reference_countries.list` Simla: Getting the list of available country codes read - `simla.reference_couriers.create` Simla: Courier creation write - `simla.reference_couriers.list` Simla: Getting the list of couriers read - `simla.reference_couriers.update` Simla: Courier editing write - `simla.reference_currencies.create` Simla: Currency creation write - `simla.reference_currencies.list` Simla: Getting the list of currencies read - `simla.reference_currencies.update` Simla: Currency editing write - `simla.reference_delivery_services.list` Simla: Getting the list of delivery services read - `simla.reference_delivery_services.update` Simla: Delivery service creation/editing write - `simla.reference_delivery_types.list` Simla: Getting the list of delivery types read - `simla.reference_delivery_types.update` Simla: Delivery type creation/editing write - `simla.reference_legal_entities.list` Simla: Getting the list of legal entities read - `simla.reference_legal_entities.update` Simla: Editing of information on legal entity write - `simla.reference_mg_channels.list` Simla: Getting a list of MessageGateway channels read - `simla.reference_order_methods.list` Simla: Getting the list of order methods read - `simla.reference_order_methods.update` Simla: Order method creation/editing write - `simla.reference_order_types.list` Simla: Getting the list of order types read - `simla.reference_order_types.update` Simla: Order type creation/editing write - `simla.reference_payment_statuses.list` Simla: Getting the list of payment statuses read - `simla.reference_payment_statuses.update` Simla: Payment status creation/editing write - `simla.reference_payment_types.list` Simla: Getting the list of payment types read - `simla.reference_payment_types.update` Simla: Payment type creation/editing write - `simla.reference_price_types.list` Simla: Getting the list of price types read - `simla.reference_price_types.update` Simla: Price type creation/editing write - `simla.reference_product_statuses.list` Simla: Getting the list of item statuses in order read - `simla.reference_product_statuses.update` Simla: Item status creation/editing write - `simla.reference_push_categories.list` Simla: Get customer mobile push notification categories read - `simla.reference_push_categories.update` Simla: Create/edit customer mobile push notification category write - `simla.reference_sites.list` Simla: Getting the stores list read - `simla.reference_sites.update` Simla: Store creation/editing write - `simla.reference_sites_tracker.list` Simla: Getting store tracker settings read - `simla.reference_status_groups.list` Simla: Getting the list of order status groups read - `simla.reference_statuses.list` Simla: Getting the list of order statuses read - `simla.reference_statuses.update` Simla: Order status creation/editing write - `simla.reference_stores.list` Simla: Getting the list of warehouses read - `simla.reference_stores.update` Simla: Creation/editing of information on warehouse write - `simla.reference_subscriptions.list` Simla: Subscription categories list read - `simla.reference_subscriptions.update` Simla: Create/edit subscription category write - `simla.reference_units.list` Simla: Getting the list of units read - `simla.reference_units.update` Simla: Unit creation/edition write - `simla.segments.list` Simla: Getting the list of customer segments read - `simla.settings.get` Simla: Getting system settings read - `simla.statistic.update` Simla: Statistics updating write - `simla.store_inventories.list` Simla: Getting the leftover stocks and purchasing prices read - `simla.store_inventories.upload` Simla: Updating the leftover stocks and purchasing prices write - `simla.store_offers.list` Simla: Getting a list of offers that meet the specified filter read - `simla.store_prices.upload` Simla: SKU prices updating write - `simla.store_product_groups.create` Simla: Adding a product group write - `simla.store_product_groups.list` Simla: Getting the list of product groups read - `simla.store_product_groups.update` Simla: Editing a product group write - `simla.store_products.list` Simla: Getting the list of products and SKU read - `simla.store_products_batch.create` Simla: Batch adding of products and services write - `simla.store_products_batch.update` Simla: Batch editing of products and services write - `simla.store_products_properties.list` Simla: Getting the list of item properties, matching the specified filter read - `simla.store_products_properties_values.list` Simla: Getting a list of property values for products or services that match the specified filters read - `simla.tasks.create` Simla: Task creation write - `simla.tasks.get` Simla: Getting information on task read - `simla.tasks.list` Simla: Getting the task list read - `simla.tasks.update` Simla: Task editing write - `simla.tasks_comments.list` Simla: Receiving comments on the task read - `simla.tasks_history.list` Simla: Getting the task change history read - `simla.telephony_calls.event` Simla: Call events write - `simla.telephony_calls.list` Simla: Getting a call list read - `simla.telephony_calls.upload` Simla: Calls uploading write - `simla.telephony_manager.get` Simla: Getting the responsible manager read - `simla.user_groups.list` Simla: Getting the list of user groups read - `simla.users.get` Simla: Getting information on user read - `simla.users.list` Simla: Getting the list of users matched the specified filter read - `simla.users.status_update` Simla: Change user status write - `simla.verification_sms.confirm` Simla: Confirmation of verification write - `simla.verification_sms.get` Simla: Checking the verification status read - `simla.web_analytics_client_ids.upload` Simla: Batch uploading of web analytics clientId write - `simla.web_analytics_sources.upload` Simla: Batch uploading of sources write - `simla.web_analytics_visits.upload` Simla: Batch uploading of visits write Questions ## The Simla.com MCP server, answered. **Is there a Simla.com MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 189 Simla.com actions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Simla.com. **What do I need to connect Simla.com?** Simla API key (Settings > Integration > API keys). Plus your account host. The free call account { op: "connections.requirements", service: "simla" } lists exactly what to paste. **Can an AI agent delete or change things in Simla.com?** Only if its key allows it, and only with an explicit confirmation. 13 Simla.com actions are destructive, including simla: Combining of orders, simla: Combining of corporate customers and simla: Deleting the file. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my Simla.com API limit?** actionlake paces every call to the limits in the Simla.com service file: 10 calls a second per connection. Repeated reads are answered from cache (84 Simla.com actions can be), which never reaches Simla.com. **What does a Simla.com action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (33 Simla.com actions page). Cache hits, searches, dry runs and calls Simla.com refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which Simla.com API does it cover?** The Simla.com API v5 at your own simla.com address, set when you connect. It is built from Simla.com's documentation as read on 21 September 2026. 189 actions in 1 area, each one in the signed service file (version 1.0.0). **Can I combine Simla.com with my other systems?** Yes. ask joins Simla.com to ConnectWise PSA or NetSuite on the same customer and returns the answer rather than every row. Simla.com maps crm.company, which 227 other connectors also map. **Does actionlake keep my Simla.com data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Simla.com credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like Simla.com Shares the most action names with - [HubSpot CRM 41](https://actionlake.com/connectors/hubspot-crm) - [Pipedrive 37](https://actionlake.com/connectors/pipedrive) - [Zoho CRM 36](https://actionlake.com/connectors/zoho-crm) - [Outreach 24](https://actionlake.com/connectors/outreach) - [Salesloft 21](https://actionlake.com/connectors/salesloft) - [Keap (Infusionsoft) 19](https://actionlake.com/connectors/keap-infusionsoft) Joins with, on shared entities - [Odoo 6](https://actionlake.com/connectors/odoo) - [ERPNext (Frappe) 6](https://actionlake.com/connectors/erpnext-frappe) - [HaloPSA 5](https://actionlake.com/connectors/halopsa) - [Acumatica Cloud ERP 5](https://actionlake.com/connectors/acumatica-cloud-erp) - [Zoho Desk 5](https://actionlake.com/connectors/zoho-desk) - [Microsoft Dynamics 365 Business Central 5](https://actionlake.com/connectors/microsoft-dynamics-365-business-central) Browse - [All CRM & sales connectors](https://actionlake.com/connectors/category/crm-and-sales) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by Simla.com; the name is the vendor's own. Counts are from the Simla.com service file, version 1.0.0. ## Give your agent Simla.com today. [Connect Simla.com free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/simla-com More: https://actionlake.com/llms.txt