chore: rename org to toolbox-sdk (#61)

Author: twishabansal

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -73,7 +73,7 @@ body:
       value: |
         1. Client: <name and link to the SDK are you using>.
         2. Version: <what exact version of the SDK are you using> (`npm list <package-name>`)? e.g.
-          - @mcp-toolbox/core version 0.1.0
+          - @toolbox-sdk/core version 0.1.0
         3. Example: If possible, please include your code of configuration:
         
         ```js

CHANGELOG.md

@@ -5,4 +5,4 @@ Changelogs
 #### TODO: Add Toolbox-core version image
 | Package    | Version |
 | -------- | ------- |
-| [@mcp-toolbox/core](https://github.com/googleapis/mcp-toolbox-sdk-js/tree/main/packages/toolbox-core/CHANGELOG.md)  | ![@mcp-toolbox/core version]()    |
+| [@toolbox-sdk/core](https://github.com/googleapis/mcp-toolbox-sdk-js/tree/main/packages/toolbox-core/CHANGELOG.md)  | ![@toolbox-sdk/core version]()    |

README.md

@@ -47,7 +47,7 @@ within your JS applications or AI orchestration frameworks.
 
 Choosing the right package depends on how you are building your application:
 
-- [`@mcp-toolbox/core`](https://github.com/googleapis/mcp-toolbox-sdk-js/tree/main/packages/toolbox-core):
+- [`@toolbox-sdk/core`](https://github.com/googleapis/mcp-toolbox-sdk-js/tree/main/packages/toolbox-core):
   This is a framework agnostic way to connect the tools to popular frameworks
   like Langchain, LlamaIndex and Genkit.
 
@@ -76,7 +76,7 @@ To get started using Toolbox tools with an application, follow these general ste
 
     ```bash
     # For the core, framework-agnostic SDK
-    npm install @mcp-toolbox/core
+    npm install @toolbox-sdk/core
     ```
 
 3. **Use the SDK:**

packages/toolbox-core/DEVELOPER.md

@@ -1,7 +1,7 @@
 # Development
 
 This guide provides instructions for setting up your development environment to
-contribute to the `@mcp-toolbox/core` package, which is part of the
+contribute to the `@toolbox-sdk/core` package, which is part of the
 `mcp-toolbox-sdk-js` monorepo.
 
 ## Prerequisites
@@ -33,8 +33,8 @@ These steps will guide you through setting up the monorepo and this specific pac
     ```
 
 4. Local Testing
-    If you need to test changes in `@mcp-toolbox/core` against another local project
-    or another package that consumes `@mcp-toolbox/core`, you can use npm link
+    If you need to test changes in `@toolbox-sdk/core` against another local project
+    or another package that consumes `@toolbox-sdk/core`, you can use npm link
 
     * In packages/toolbox-core
 
@@ -45,10 +45,10 @@ These steps will guide you through setting up the monorepo and this specific pac
     * In your consuming project
 
         ```bash
-        npm link @mcp-toolbox/core
+        npm link @toolbox-sdk/core
         ```  
 
-    This creates a symbolic link, allowing changes in `@mcp-toolbox/core` to be
+    This creates a symbolic link, allowing changes in `@toolbox-sdk/core` to be
     immediately reflected in the consuming project without reinstallation.
 
     Don't forget to npm unlink / yarn unlink when done!

packages/toolbox-core/README.md

@@ -65,7 +65,7 @@ compatibility with the modern JavaScript ecosystem.
 ## Installation
 
 ```bash
-npm install @mcp-toolbox/core
+npm install @toolbox-sdk/core
 ```
 
 ## Quickstart
@@ -74,7 +74,7 @@ Here's a minimal example to get you started. Ensure your Toolbox service is runn
 
 ```javascript
 
-import { ToolboxClient } from '@mcp-toolbox/core';  
+import { ToolboxClient } from '@toolbox-sdk/core';  
 const client = new ToolboxClient(URL);  
 
 async function quickstart() {  
@@ -91,15 +91,15 @@ quickstart();
 > [!NOTE]
 > This guide uses modern ES Module (`import`) syntax. If your project uses
 > CommonJS, you can import the library using require: `const { ToolboxClient }
-> = require('@mcp-toolbox/core')`;.
+> = require('@toolbox-sdk/core')`;.
 
 ## Usage
 
 Import and initialize a Toolbox client, pointing it to the URL of your running
 Toolbox service.
 
 ```javascript
-import { ToolboxClient } from '@mcp-toolbox/core';
+import { ToolboxClient } from '@toolbox-sdk/core';
 
 // Replace with the actual URL where your Toolbox service is running
 const URL = 'http://127.0.0.1:5000';
@@ -207,8 +207,8 @@ that fresh credentials or header values can be used.
 You can configure these dynamic headers as seen below:
 
 ```javascript
-import { ToolboxClient } from '@mcp-toolbox/core';
-import {getGoogleIdToken} from '@mcp-toolbox/core/auth'
+import { ToolboxClient } from '@toolbox-sdk/core';
+import {getGoogleIdToken} from '@toolbox-sdk/core/auth'
 
 const URL = 'http://127.0.0.1:5000';
 const getGoogleIdTokenGetter = () => getGoogleIdToken(URL);
@@ -237,8 +237,8 @@ For Toolbox servers hosted on Google Cloud (e.g., Cloud Run) and requiring
 3. **Connect to the Toolbox Server**
 
     ```javascript
-    import { ToolboxClient } from '@mcp-toolbox/core';
-    import {getGoogleIdToken} from '@mcp-toolbox/core/auth'
+    import { ToolboxClient } from '@toolbox-sdk/core';
+    import {getGoogleIdToken} from '@toolbox-sdk/core/auth'
 
     const URL = 'http://127.0.0.1:5000';
     const getGoogleIdTokenGetter = () => getGoogleIdToken(URL);
@@ -355,7 +355,7 @@ const authTools = await toolbox.loadToolset({"myAuth": getAuthToken})
 ### Complete Authentication Example
 
 ```javascript
-import { ToolboxClient } from '@mcp-toolbox/core';
+import { ToolboxClient } from '@toolbox-sdk/core';
 
 async function getAuthToken() {
     // ... Logic to retrieve ID token (e.g., from local storage, OAuth flow)
@@ -399,7 +399,7 @@ specific tool instance.
 
 ```javascript
 
-import { ToolboxClient } from '@mcp-toolbox/core';
+import { ToolboxClient } from '@toolbox-sdk/core';
 
 const URL = 'http://127.0.0.1:5000';
 let client = new ToolboxClient(URL);
@@ -456,7 +456,7 @@ const dynamicBoundTool = tool.bindParam("param", getDynamicValue)
 [LangchainJS](https://js.langchain.com/docs/introduction/)
 
 ```javascript
-import {ToolboxClient} from "@mcp-toolbox/core"
+import {ToolboxClient} from "@toolbox-sdk/core"
 import { tool } from "@langchain/core/tools";
 
 let client = ToolboxClient(URL)
@@ -485,7 +485,7 @@ Agents](https://langchain-ai.github.io/langgraphjs/reference/functions/langgraph
 [LlamaindexTS](https://ts.llamaindex.ai/)
 
 ```javascript
-import {ToolboxClient} from "@mcp-toolbox/core"
+import {ToolboxClient} from "@toolbox-sdk/core"
 import { tool } from "llamaindex";
 
 let client = ToolboxClient(URL)
@@ -514,7 +514,7 @@ workflows](https://ts.llamaindex.ai/docs/llamaindex/modules/agents/agent_workflo
 
 [GenkitJS](https://genkit.dev/docs/get-started/#_top)
 ```javascript
-import {ToolboxClient} from "@mcp-toolbox/core"
+import {ToolboxClient} from "@toolbox-sdk/core"
 import { genkit, z } from 'genkit';
 import { googleAI } from '@genkit-ai/googleai';
 

packages/toolbox-core/package-lock.json

@@ -1,5 +1,5 @@
 {
-    "name": "@mcp-toolbox/core",
+    "name": "@toolbox-sdk/core",
     "version": "0.1.0",
     "type": "module",
     "description": "JavaScript Base SDK for interacting with the Toolbox service",

packages/toolbox-core/package.json

@@ -17,8 +17,8 @@ This module provides functions to obtain Google ID tokens, formatted as "Bearer"
 for use in the "Authorization" header of HTTP requests.
 
 Example User Experience:
-import { ToolboxClient } from '@toolbox/core';
-import { getGoogleIdToken } from '@toolbox/core/auth'
+import { ToolboxClient } from '@toolbox-sdk/core';
+import { getGoogleIdToken } from '@toolbox-sdk/core/auth'
 
 const URL = 'http://some-url'
 const getGoogleIdTokenGetter = () => getGoogleIdToken(URL);