list_chatbotsLABSCO SUMMARY
A separate read-only URL is a cruder control than scopes and a more reliable one.
Scopes depend on the server enforcing them correctly on every call. A different endpoint that simply does not have the write tools cannot be tricked into writing, whatever the token says. If you are connecting an assistant that only needs to look, use the read-only address even though the scopes would also cover you — one is a policy, the other is an absence. Worth noting on privacy: the vendor states Gemini free-tier conversations may be used differently from paid API traffic.
What it is
Chaterimo publishes its MCP surface twice. The full endpoint carries all 19 tools including the writes; a separate read-only address exposes 12 and cannot write at all.
What you get
The read tools on either endpoint; the write tools only on the full one. Which endpoint you configure is the permission decision.
Requirements
OAuth 2.0 with PKCE, refresh tokens and dynamic client registration, scoped mcp:read and mcp:write. Two pricing schemes: bring your own OpenAI, Anthropic or Gemini key, or use managed keys; there is a free Learner tier.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Giving an assistant a look but no touch
Point it at the read-only endpoint, where the write tools do not exist.
02
Keeping model traffic on your own keys
Bring your own OpenAI, Anthropic or Gemini key rather than using managed ones.
19 tools
Listed in project docs. Your client may show a different list.
get_chatbotlist_conversationsget_conversationsearch_productslist_productslist_ticketsget_ticketlist_leadsget_analyticslist_sales_rulesget_dashboardupdate_chatbot_instructionsupdate_chatbot_modelupdate_chatbot_languageupdate_chatbot_settingsupdate_widget_appearanceupdate_widget_messagesretrain_chatbotBEFORE YOU INSTALL
What to know first
Tools you get
19 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- OAuth 2.0 authorization_code + PKCE(S256) + refresh_token, dynamic client registration, scopes mcp:read mcp:write; Bearer header
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://www.chaterimo.com/mcp/Requirements
- OAuth 2.0 authorization_code + PKCE(S256) + refresh_token, dynamic client registration, scopes mcp:read mcp:write; Bearer header
