Skip to main content
Glama
Sign In
SMCPHUB Server

SMCPHUB Server

by PA-LuffyYu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Welcome to @smcphub/server πŸ‘‹

Version Documentation License: MIT

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

Install

npm i @smcphub/server

OR

yarn add @smcphub/server

Related MCP server: ai-mcp-toolkit

Usage

Use official MCP Client to connect to the MCP Server.


// 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

Available Tools

2 tools
get_tool_setC

Get the tool set detail by specific tool set id

Inputs: tool_set_id (required).

get_tool_setsC

Include all tools sets, every tool set has multiple tools

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers