mcporter-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCORTER_BRIDGE_MCPORTER_BIN | No | Override the mcporter binary path | |
| MCORTER_BRIDGE_MAX_OUTPUT_CHARS | No | Cap captured stdout/stderr length |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcporter_list_serversA | 【MCP 全景】列出所有已加载和可激活的 MCP 服务器。 返回分区:
工具分类概览:
注:实际可用 MCP 以调用结果为准,本列表仅为示例 ⚠️ 大型 MCP 占用大量上下文,请遵循:按需激活 → 用完即释放 使用流程:
|
| mcporter_helpA | 探索 MCP 服务器的工具和参数。 渐进式查询(推荐):
完整技术定义(需要原始 JSON):
示例: mcporter_help(server="xiaohongshu") # 看工具有哪些 mcporter_help(server="xiaohongshu", tool="search_feeds") # 看参数格式 mcporter_help(server="xiaohongshu", raw=true) # 看原始定义 |
| mcporter_call_toolB | 调用指定服务器的工具。 参数:
示例: ⚠️ 先用 mcporter_help 查询参数格式 |
| mcporter_statusA | 检查 mcporter 状态和配置。 action 参数:
示例: mcporter_status() # 验证配置 mcporter_status(action="version") # 查看版本 |
| mcporter_activate_mcpA | 激活一个大型 MCP。激活后需重新调用 mcporter_list_servers 确认。 参数:name - 从 mcporter_list_servers().available 中获取的名称 示例:mcporter_activate_mcp(name="playwright") |
| mcporter_deactivate_mcpC | 停用大型 MCP 释放上下文。 参数:name - 要停用的 MCP 名称 示例:mcporter_deactivate_mcp(name="playwright") |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool maps to a distinct phase of the MCP lifecycle: listing, exploring, calling, status checking, and activation/deactivation. There is no functional overlap between them, making selection unambiguous.
All tools share the mcporter_ prefix and most follow a verb_noun pattern (list_servers, call_tool, activate_mcp, deactivate_mcp). However, 'help' and 'status' are single verbs/nouns that deviate slightly from the pattern.
Six tools is an ideal number for a bridge server, covering the full management lifecycle without unnecessary bloat. Each tool has a clear and necessary role.
The tool set provides a complete workflow: discover available MCPs, activate large ones on demand, inspect tool schemas, call tools, and deactivate to free context. Status diagnostics round out the surface, so no critical operations are missing.