@withone/mcp 2.1.1 → 2.2.1

package/README.md

@@ -20,7 +20,7 @@
   <a href="https://npmjs.com/package/@withone/mcp"><img src="https://img.shields.io/npm/v/%40withone%2Fmcp" alt="npm version"></a>
 </p>
 
-Connect your AI agents to 700+ apps through a single [MCP](https://modelcontextprotocol.io) server. Find the actions a task needs with their documentation, and execute API calls across platforms, without having to manage OAuth tokens or API keys.
+Connect your AI agents to 1000+ apps through a single [MCP](https://modelcontextprotocol.io) server. Find the actions a task needs with their documentation, and execute API calls across platforms, without having to manage OAuth tokens or API keys.
 
 ```bash
 npm install -g @withone/cli
@@ -31,7 +31,7 @@ That's it. The [One CLI](https://www.npmjs.com/package/@withone/cli) will prompt
 
 ## Capabilities
 
-- **700+ platforms.** Gmail, Slack, Shopify, HubSpot, Stripe, Linear, QuickBooks, and [more](https://app.withone.ai/tools).
+- **1000+ platforms.** Gmail, Slack, Shopify, HubSpot, Stripe, Linear, QuickBooks, and [more](https://app.withone.ai/tools).
 - **Natural language execution.** "read my last gmail email", "send a message to #general on Slack"
 - **Code generation.** "build a form to send emails using Gmail", "create a dashboard that lists my Linear projects"
 - **No tool bloat.** Only 3 tools exposed regardless of how many platforms or actions you connect. One call finds every action a task needs, across platforms, with its documentation, so your agent's context window stays clean.
@@ -66,7 +66,7 @@ The server exposes three MCP tools:
 
 ### Finding actions
 
-`find_one_actions` takes one `requests` entry per operation, each a kebab-case `platform` and a short `intent` naming the operation alone (`"send a message to a channel"`, not the message). A `task` describes the whole job in general terms, and an `ai_model` names the model asking; agents are asked to send both with every find, since the task helps tell similar actions apart. For each intent, One's decision model picks the action to use; the answer documents it, sets apart a substitute when the model was unsure, and lists a few alternatives. Large documents come back as a digest; call `find_one_actions` again with `load: [{ action_id, section }]` for a section it left out, `full: true` for the whole document, or `toc: true` for its table of contents. `ONE_ACTION_IDS`, `ONE_PERMISSIONS` and `ONE_CONNECTION_KEYS` apply to every answer: an action they refuse is never offered, and when they refuse the model's pick, the next allowed candidate takes its place.
+`find_one_actions` takes one `requests` entry per operation, each a kebab-case `platform` and a short `intent` naming the operation alone (`"send a message to a channel"`, not the message). A `task` describes the whole job in general terms, and an `ai_model` names the model asking; agents are asked to send both with every find, since the task helps tell similar actions apart. For each intent, One's decision model picks the action to use; the answer documents it, sets apart a substitute when the model was unsure, and lists a few alternatives. A `platform` no active platform has (`clickup` for `click-up`) is not searched: the answer names the platforms it may have meant, closest first, so the agent can ask again with the right one. Large documents come back as a digest; call `find_one_actions` again with `load: [{ action_id, section }]` for a section it left out, `full: true` for the whole document, or `toc: true` for its table of contents. `ONE_ACTION_IDS`, `ONE_PERMISSIONS` and `ONE_CONNECTION_KEYS` apply to every answer: an action they refuse is never offered, and when they refuse the model's pick, the next allowed candidate takes its place.
 
 Upgrading from 1.x: `search_one_platform_actions` and `get_one_action_knowledge` are removed. `find_one_actions` replaces both.
 

package/build/find.js

@@ -93,6 +93,13 @@ function status(answer, narrowed) {
     if (narrowed.replaced) {
         return 'The chosen action is not allowed on this server, so this is the next allowed candidate: check it fits before using it.';
     }
+    if (answer.selector === 'unknown_platform') {
+        const opening = `No active platform is named \`${answer.platform}\`.`;
+        const suggestions = answer.suggestions ?? [];
+        return suggestions.length === 0
+            ? `${opening} Check the platform name: \`list_one_integrations\` gives the exact name of each connected integration.`
+            : `${opening} Did you mean ${suggestions.map((s) => `\`${s}\``).join(', ')}? Ask again with the platform you meant.`;
+    }
     if (answer.selector === 'none_fit' || answer.selected.length === 0) {
         return answer.alternatives.length === 0
             ? 'No action fits this intent, and nothing close was found. Rephrase it, or check the platform name.'

package/build/find.test.js

@@ -131,6 +131,18 @@ describe('find_one_actions', () => {
         assert.ok(text.includes('No action fits this intent, and nothing close was found.'));
         assert.ok(!text.includes(FIND_EXECUTE_HINT));
     });
+    it('names the platforms core suggests for a name no active platform has', async () => {
+        const unknown = (suggestions) => answer({ platform: 'clickup', intent: 'create a task', selected: [], alternatives: [], selector: 'unknown_platform', confidence: undefined, suggestions });
+        const asked = [
+            { platform: 'clickup', intent: 'create a task' },
+            { platform: 'clickup', intent: 'create a task' },
+        ];
+        const text = await findOneActions({ requests: asked }, deps([unknown(['click-up', 'click-house']), unknown()]), settings());
+        assert.ok(text.includes('No active platform is named `clickup`. Did you mean `click-up`, `click-house`? Ask again with the platform you meant.'), text);
+        assert.ok(text.includes('Check the platform name: `list_one_integrations` gives the exact name'), text);
+        assert.ok(!text.includes('No action fits'), 'an unknown platform is not read as a platform with no fitting action');
+        assert.ok(!text.includes(FIND_EXECUTE_HINT), 'nothing was documented');
+    });
     it('loads what each entry asked for, refusing one this server may not use in the words for a missing one', async () => {
         const text = await findOneActions({ load: [{ action_id: 'a', section: 'Response Fields' }, { action_id: 'missing' }, { action_id: 'b' }] }, deps([], { a: LARGE }), settings({ actionIds: ['a', 'missing'] }));
         assert.ok(text.includes('### Action a'));

package/build/index.js

@@ -93,7 +93,7 @@ async function handleGetIntegrations(args) {
         const resolvedAllowed = (await oneClient.resolveAllowedActions(ONE_ACTION_IDS))
             .filter(action => isMethodAllowed(action.method, ONE_PERMISSIONS));
         // Execute mode lists only connections: every connection carries its
-        // access, and the full catalog (800+ platforms) would sit in the agent's
+        // access, and the full catalog (1000+ platforms) would sit in the agent's
         // context for the rest of the session. Knowledge/code-gen mode also lists
         // available platforms so code can target one that is not connected yet,
         // unless connection keys are scoped.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@withone/mcp",
-  "version": "2.1.1",
+  "version": "2.2.1",
   "description": "A Model Context Protocol Server for One",
   "type": "module",
   "bin": {