SMCPHUB Server
# Welcome to @smcphub/server š
[](https://www.smcphub.com/docs)
[](#)
> MCP Server of SMCPHUB
SMCP Server is a simple and easy-to-use client for smcphub.com. It provides a simple API to interact with all the MCP Servers hosted in the smcphub.com.
SMCP hub is a platform that allows you to find the MCP servers which users published, or also publish your MCP Servers and get them listed and hosted on the website.
### š [Homepage](https://smcphub.com)
## Install
```sh
npm i @smcphub/server
```
OR
```sh
yarn add @smcphub/server
```
## Usage
Use official MCP Client to connect to the MCP Server.
```js
// import the SDK
import SmcphubClient from '@smcphub/client';
// Instantiate the client
const smcphubClient = new SmcphubClient({
api_key: 'your-api-key'
});
// Connect the MCP Server
smcphubClient
.connect()
.then(tools => {
console.log(tools);
})
.catch(err => {
console.error(err);
});
// Call the tool
smcphubClient
.callTool('get_weather', {'city': 'ęå·'})
.then(content => {
console.log(content);
})
.catch(err => {
console.error(err);
});
```
Or customize the MCP Server.
## Author
š¤ **SMCPHUB**TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'get_tool_set' retrieves details for a specific tool set by ID, while 'get_tool_sets' lists all tool sets. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on whether it needs a single item or a collection.
Both tools follow a consistent verb_noun naming pattern: 'get_tool_set' and 'get_tool_sets'. The naming is predictable and uses the same verb ('get') with singular and plural nouns to indicate the scope, ensuring clarity and uniformity.
With only 2 tools, the server feels thin for a tool management domain. A typical tool management system would require more operations, such as creating, updating, or deleting tool sets, to be considered well-scoped. This limited set may hinder agent workflows that need full lifecycle management.
The tool surface is severely incomplete for tool management. It only provides read operations (get details and list), missing essential CRUD functions like create, update, or delete tool sets. This creates significant gaps that will likely cause agent failures when trying to perform comprehensive tool management tasks.