agenza-line-bot-mcp 0.0.1 → 0.0.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +12 -10
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
|
-
[
|
|
1
|
+
[README](README.ja.md)
|
|
2
2
|
|
|
3
|
-
# LINE Bot MCP Server
|
|
3
|
+
# LINE Bot MCP Server (Custom)
|
|
4
4
|
|
|
5
|
-
[
|
|
5
|
+
> **Note:** This is a customized fork from [https://github.com/line/line-bot-mcp-server](https://github.com/line/line-bot-mcp-server)
|
|
6
6
|
|
|
7
7
|
[Model Context Protocol (MCP)](https://github.com/modelcontextprotocol) server implementation that integrates the LINE Messaging API to connect an AI Agent to the LINE Official Account.
|
|
8
8
|
|
|
@@ -94,13 +94,15 @@ Set the environment variables or arguments as follows:
|
|
|
94
94
|
- `CHANNEL_ACCESS_TOKEN`: (required) Channel Access Token. You can confirm this by following [this instructions](https://developers.line.biz/en/docs/basics/channel-access-token/#long-lived-channel-access-token).
|
|
95
95
|
- `DESTINATION_USER_ID`: (optional) The default user ID of the recipient. If the Tool's input does not include `userId`, `DESTINATION_USER_ID` is required. You can confirm this by following [this instructions](https://developers.line.biz/en/docs/messaging-api/getting-user-ids/#get-own-user-id).
|
|
96
96
|
|
|
97
|
+
> **Note:** Since this is a custom fork, you'll need to clone and build locally instead of using npx with the official package.
|
|
98
|
+
|
|
97
99
|
```json
|
|
98
100
|
{
|
|
99
101
|
"mcpServers": {
|
|
100
102
|
"line-bot": {
|
|
101
|
-
"command": "
|
|
103
|
+
"command": "node",
|
|
102
104
|
"args": [
|
|
103
|
-
"
|
|
105
|
+
"YOUR_PATH/line-bot-mcp-server/dist/index.js"
|
|
104
106
|
],
|
|
105
107
|
"env": {
|
|
106
108
|
"CHANNEL_ACCESS_TOKEN" : "FILL_HERE",
|
|
@@ -122,16 +124,16 @@ If you have a LINE Official Account, enable the Messaging API for your LINE Offi
|
|
|
122
124
|
|
|
123
125
|
### Step 2: Build line-bot-mcp-server image
|
|
124
126
|
|
|
125
|
-
Clone this repository:
|
|
127
|
+
Clone this custom repository:
|
|
126
128
|
|
|
127
129
|
```
|
|
128
|
-
git clone
|
|
130
|
+
git clone https://github.com/YOUR_USERNAME/line-bot-mcp-server.git
|
|
129
131
|
```
|
|
130
132
|
|
|
131
133
|
Build the Docker image:
|
|
132
134
|
|
|
133
135
|
```
|
|
134
|
-
docker build -t
|
|
136
|
+
docker build -t custom/line-bot-mcp-server .
|
|
135
137
|
```
|
|
136
138
|
|
|
137
139
|
### Step 3: Configure AI Agent
|
|
@@ -159,7 +161,7 @@ You can confirm this by following [this instructions](https://developers.line.bi
|
|
|
159
161
|
"CHANNEL_ACCESS_TOKEN",
|
|
160
162
|
"-e",
|
|
161
163
|
"DESTINATION_USER_ID",
|
|
162
|
-
"
|
|
164
|
+
"custom/line-bot-mcp-server"
|
|
163
165
|
],
|
|
164
166
|
"env": {
|
|
165
167
|
"CHANNEL_ACCESS_TOKEN" : "FILL_HERE",
|
|
@@ -178,7 +180,7 @@ You can use the MCP Inspector to test and debug the server locally.
|
|
|
178
180
|
|
|
179
181
|
1. Clone the repository:
|
|
180
182
|
```bash
|
|
181
|
-
git clone
|
|
183
|
+
git clone https://github.com/Mbiz-consultant/line-bot-mcp
|
|
182
184
|
cd line-bot-mcp-server
|
|
183
185
|
```
|
|
184
186
|
|