shield_lock
JinDaGe
← Back to MCP directory
publicPublicdnsLocal runtime

mcp-server-twse

TWSE MCP服务器配置项目，支持从GitHub克隆或本地运行

article

README

🚀 项目配置说明

本项目提供了两种配置方式，分别是从 GitHub 拉取代码的配置和本地运行的配置。以下为您详细介绍这两种配置方式。

🚀 快速开始

💻 使用示例

GitHub 配置

{
  "mcpServers": {
    "twsemcp": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/narumiruna/twse-mcp",
        "twsemcp"
      ]
    }
  }
}
  • 基础用法 此配置用于从 GitHub 仓库拉取代码并运行服务。具体详情如下： | 属性 | 详情 | |------|------| | 命令 | uvx | | 参数 | 1. --from
    2. 使用 Git 协议从 GitHub 仓库 拉取代码
    3. 服务名称：twsemcp |

本地配置

{
  "mcpServers": {
    "twsemcp": {
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "/home/<user>/workspace/twse-mcp",
        "twsemcp"
      ]
    }
  }
}
  • 基础用法 此配置用于在本地指定目录下运行服务。具体详情如下： | 属性 | 详情 | |------|------| | 命令 | uv | | 参数 | 1. run
    2. 使用指定的 目录 /home/<用户>/workspace/twse-mcp
    3. 服务名称：twsemcp |
help

Runtime guide

cloud

Hosted runtime

Hosted servers run from a provider-managed environment. You usually connect the MCP client to the hosted endpoint or follow the provider's authorization flow, without keeping a local process alive

  1. Open provider connection page
  2. Authorize or copy endpoint
  3. Connect from your MCP client
terminal

Local runtime / other methods

Local servers run on your own machine or infrastructure. You normally copy the server_config into your MCP client, install the required package, and provide env variables from env_schema when needed

  1. Copy server_config
  2. Install required package
  3. Fill env variables and restart client