fellow-mcp 1.0.0 → 1.0.1

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 CHANGED
@@ -10,21 +10,10 @@ A local MCP (Model Context Protocol) server that wraps the Fellow.ai API, provid
10
10
 
11
11
  ## Installation
12
12
 
13
- ### Option 1: Install from npm (Recommended)
14
-
15
13
  ```bash
16
14
  npm install -g fellow-mcp
17
15
  ```
18
16
 
19
- ### Option 2: Install from source
20
-
21
- ```bash
22
- git clone https://github.com/liba2k/fellow-mcp.git
23
- cd fellow-mcp
24
- npm install
25
- npm run build
26
- ```
27
-
28
17
  ## Setup
29
18
 
30
19
  ### 1. Get your Fellow API credentials
@@ -36,8 +25,6 @@ npm run build
36
25
 
37
26
  ### 2. Configure your MCP client
38
27
 
39
- #### If installed via npm:
40
-
41
28
  Add the following to your MCP client configuration (e.g., `~/.config/opencode/opencode.json`):
42
29
 
43
30
  ```json
@@ -45,55 +32,10 @@ Add the following to your MCP client configuration (e.g., `~/.config/opencode/op
45
32
  "mcp": {
46
33
  "fellow": {
47
34
  "type": "local",
48
- "command": ["fellow-mcp"],
49
- "env": {
50
- "FELLOW_API_KEY": "your-api-key-here",
51
- "FELLOW_SUBDOMAIN": "your-subdomain"
52
- },
53
- "enabled": true
54
- }
55
- }
56
- }
57
- ```
58
-
59
- #### If installed from source:
60
-
61
- Option A: Use the run.sh script with .env file:
62
-
63
- 1. Copy the example env file and fill in your credentials:
64
- ```bash
65
- cp .env.example .env
66
- ```
67
-
68
- 2. Edit `.env` with your credentials:
69
- ```
70
- FELLOW_API_KEY=your-api-key-here
71
- FELLOW_SUBDOMAIN=your-subdomain
72
- ```
73
-
74
- 3. Configure your MCP client:
75
- ```json
76
- {
77
- "mcp": {
78
- "fellow": {
79
- "type": "local",
80
- "command": ["/path/to/fellow-mcp/run.sh"],
81
- "enabled": true
82
- }
83
- }
84
- }
85
- ```
86
-
87
- Option B: Pass environment variables directly:
88
- ```json
89
- {
90
- "mcp": {
91
- "fellow": {
92
- "type": "local",
93
- "command": ["node", "/path/to/fellow-mcp/dist/index.js"],
94
- "env": {
95
- "FELLOW_API_KEY": "your-api-key-here",
96
- "FELLOW_SUBDOMAIN": "your-subdomain"
35
+ "command": ["npx", "-y", "fellow-mcp"],
36
+ "environment": {
37
+ "FELLOW_API_KEY": "YOUR_FELLOW_API_KEY_HERE",
38
+ "FELLOW_SUBDOMAIN": "YOUR_SUBDOMAIN"
97
39
  },
98
40
  "enabled": true
99
41
  }
@@ -207,8 +149,8 @@ npm run dev
207
149
  # Build
208
150
  npm run build
209
151
 
210
- # Test the server
211
- node dist/index.js --test
152
+ # Test API connection
153
+ node --env-file=.env test-api.js
212
154
  ```
213
155
 
214
156
  ## Requirements
package/dist/index.js CHANGED
File without changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "fellow-mcp",
3
- "version": "1.0.0",
3
+ "version": "1.0.1",
4
4
  "description": "MCP server for Fellow.ai API - access meeting data, transcripts, summaries, and action items",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",