mcp-quickbase 2.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.
Files changed (135) hide show
  1. package/CHANGELOG.md +82 -0
  2. package/LICENSE +21 -0
  3. package/README.md +301 -0
  4. package/dist/client/quickbase.d.ts +28 -0
  5. package/dist/client/quickbase.js +235 -0
  6. package/dist/client/quickbase.js.map +1 -0
  7. package/dist/mcp/index.d.ts +4 -0
  8. package/dist/mcp/index.js +21 -0
  9. package/dist/mcp/index.js.map +1 -0
  10. package/dist/mcp/server.d.ts +19 -0
  11. package/dist/mcp/server.js +102 -0
  12. package/dist/mcp/server.js.map +1 -0
  13. package/dist/mcp-stdio-server.d.ts +2 -0
  14. package/dist/mcp-stdio-server.js +168 -0
  15. package/dist/mcp-stdio-server.js.map +1 -0
  16. package/dist/server.d.ts +2 -0
  17. package/dist/server.js +318 -0
  18. package/dist/server.js.map +1 -0
  19. package/dist/tools/apps/create_app.d.ts +87 -0
  20. package/dist/tools/apps/create_app.js +87 -0
  21. package/dist/tools/apps/create_app.js.map +1 -0
  22. package/dist/tools/apps/index.d.ts +9 -0
  23. package/dist/tools/apps/index.js +40 -0
  24. package/dist/tools/apps/index.js.map +1 -0
  25. package/dist/tools/apps/list_tables.d.ts +108 -0
  26. package/dist/tools/apps/list_tables.js +100 -0
  27. package/dist/tools/apps/list_tables.js.map +1 -0
  28. package/dist/tools/apps/update_app.d.ts +91 -0
  29. package/dist/tools/apps/update_app.js +99 -0
  30. package/dist/tools/apps/update_app.js.map +1 -0
  31. package/dist/tools/base.d.ts +47 -0
  32. package/dist/tools/base.js +63 -0
  33. package/dist/tools/base.js.map +1 -0
  34. package/dist/tools/configure_cache.d.ts +81 -0
  35. package/dist/tools/configure_cache.js +77 -0
  36. package/dist/tools/configure_cache.js.map +1 -0
  37. package/dist/tools/fields/create_field.d.ts +121 -0
  38. package/dist/tools/fields/create_field.js +102 -0
  39. package/dist/tools/fields/create_field.js.map +1 -0
  40. package/dist/tools/fields/index.d.ts +8 -0
  41. package/dist/tools/fields/index.js +37 -0
  42. package/dist/tools/fields/index.js.map +1 -0
  43. package/dist/tools/fields/update_field.d.ts +112 -0
  44. package/dist/tools/fields/update_field.js +114 -0
  45. package/dist/tools/fields/update_field.js.map +1 -0
  46. package/dist/tools/files/download_file.d.ts +111 -0
  47. package/dist/tools/files/download_file.js +173 -0
  48. package/dist/tools/files/download_file.js.map +1 -0
  49. package/dist/tools/files/index.d.ts +8 -0
  50. package/dist/tools/files/index.js +37 -0
  51. package/dist/tools/files/index.js.map +1 -0
  52. package/dist/tools/files/upload_file.d.ts +107 -0
  53. package/dist/tools/files/upload_file.js +211 -0
  54. package/dist/tools/files/upload_file.js.map +1 -0
  55. package/dist/tools/index.d.ts +18 -0
  56. package/dist/tools/index.js +65 -0
  57. package/dist/tools/index.js.map +1 -0
  58. package/dist/tools/records/bulk_create_records.d.ts +75 -0
  59. package/dist/tools/records/bulk_create_records.js +104 -0
  60. package/dist/tools/records/bulk_create_records.js.map +1 -0
  61. package/dist/tools/records/bulk_update_records.d.ts +77 -0
  62. package/dist/tools/records/bulk_update_records.js +102 -0
  63. package/dist/tools/records/bulk_update_records.js.map +1 -0
  64. package/dist/tools/records/create_record.d.ts +68 -0
  65. package/dist/tools/records/create_record.js +123 -0
  66. package/dist/tools/records/create_record.js.map +1 -0
  67. package/dist/tools/records/index.d.ts +11 -0
  68. package/dist/tools/records/index.js +46 -0
  69. package/dist/tools/records/index.js.map +1 -0
  70. package/dist/tools/records/query_records.d.ts +164 -0
  71. package/dist/tools/records/query_records.js +261 -0
  72. package/dist/tools/records/query_records.js.map +1 -0
  73. package/dist/tools/records/update_record.d.ts +81 -0
  74. package/dist/tools/records/update_record.js +99 -0
  75. package/dist/tools/records/update_record.js.map +1 -0
  76. package/dist/tools/registry.d.ts +41 -0
  77. package/dist/tools/registry.js +66 -0
  78. package/dist/tools/registry.js.map +1 -0
  79. package/dist/tools/reports/index.d.ts +6 -0
  80. package/dist/tools/reports/index.js +31 -0
  81. package/dist/tools/reports/index.js.map +1 -0
  82. package/dist/tools/reports/run_report.d.ts +70 -0
  83. package/dist/tools/reports/run_report.js +72 -0
  84. package/dist/tools/reports/run_report.js.map +1 -0
  85. package/dist/tools/tables/create_table.d.ts +142 -0
  86. package/dist/tools/tables/create_table.js +119 -0
  87. package/dist/tools/tables/create_table.js.map +1 -0
  88. package/dist/tools/tables/get_table_fields.d.ts +108 -0
  89. package/dist/tools/tables/get_table_fields.js +96 -0
  90. package/dist/tools/tables/get_table_fields.js.map +1 -0
  91. package/dist/tools/tables/index.d.ts +9 -0
  92. package/dist/tools/tables/index.js +40 -0
  93. package/dist/tools/tables/index.js.map +1 -0
  94. package/dist/tools/tables/update_table.d.ts +91 -0
  95. package/dist/tools/tables/update_table.js +99 -0
  96. package/dist/tools/tables/update_table.js.map +1 -0
  97. package/dist/tools/test_connection.d.ts +51 -0
  98. package/dist/tools/test_connection.js +101 -0
  99. package/dist/tools/test_connection.js.map +1 -0
  100. package/dist/types/api.d.ts +70 -0
  101. package/dist/types/api.js +6 -0
  102. package/dist/types/api.js.map +1 -0
  103. package/dist/types/config.d.ts +49 -0
  104. package/dist/types/config.js +3 -0
  105. package/dist/types/config.js.map +1 -0
  106. package/dist/types/mcp.d.ts +55 -0
  107. package/dist/types/mcp.js +3 -0
  108. package/dist/types/mcp.js.map +1 -0
  109. package/dist/utils/cache.d.ts +87 -0
  110. package/dist/utils/cache.js +211 -0
  111. package/dist/utils/cache.js.map +1 -0
  112. package/dist/utils/file.d.ts +40 -0
  113. package/dist/utils/file.js +167 -0
  114. package/dist/utils/file.js.map +1 -0
  115. package/dist/utils/logger.d.ts +37 -0
  116. package/dist/utils/logger.js +144 -0
  117. package/dist/utils/logger.js.map +1 -0
  118. package/dist/utils/retry.d.ts +39 -0
  119. package/dist/utils/retry.js +88 -0
  120. package/dist/utils/retry.js.map +1 -0
  121. package/dist/utils/validation.d.ts +32 -0
  122. package/dist/utils/validation.js +227 -0
  123. package/dist/utils/validation.js.map +1 -0
  124. package/docs/README.md +41 -0
  125. package/docs/architecture.md +94 -0
  126. package/docs/claude-prompts.md +218 -0
  127. package/docs/deployment.md +244 -0
  128. package/docs/developer-guide.md +537 -0
  129. package/docs/final-qa-report.md +243 -0
  130. package/docs/performance-benchmarks.md +306 -0
  131. package/docs/quick-reference.md +109 -0
  132. package/docs/quickstart.md +183 -0
  133. package/docs/security-review.md +263 -0
  134. package/docs/tools.md +269 -0
  135. package/package.json +68 -0
@@ -0,0 +1,218 @@
1
+ # Claude Desktop Prompts for Quickbase Construction Management
2
+
3
+ This document provides natural language prompts you can use directly in Claude Desktop to manage your construction projects through Quickbase MCP Server. Simply copy and paste these prompts, then modify the details as needed.
4
+
5
+ ## Table of Contents
6
+ 1. [Daily Operations](#daily-operations)
7
+ 2. [Project Management](#project-management)
8
+ 3. [Workforce & Crew Management](#workforce--crew-management)
9
+ 4. [Materials & Inventory](#materials--inventory)
10
+ 5. [Safety & Incident Management](#safety--incident-management)
11
+ 6. [Reporting & Analytics](#reporting--analytics)
12
+
13
+ ## Daily Operations
14
+
15
+ ### Morning Crew Check-in
16
+ ```
17
+ Check our Quickbase system and show me which crews are working today, what projects they're assigned to, and who's leading each crew. Also tell me if any crews don't have active assignments.
18
+ ```
19
+
20
+ ### Log Daily Work Progress
21
+ ```
22
+ Add a work log entry to Quickbase: The Concrete Crew worked 8.5 hours today on the Commercial Building project, completing the foundation pour for section C. Quality inspection passed and we're on schedule for the next phase.
23
+ ```
24
+
25
+ ### End-of-Day Summary
26
+ ```
27
+ Generate an end-of-day report from Quickbase showing: 1) All work logged today with hours and crews, 2) Any safety incidents reported, 3) Materials that are running low, and 4) tasks that were completed or updated today.
28
+ ```
29
+
30
+ ### Quick Status Check
31
+ ```
32
+ Give me a quick status update from Quickbase on our top 3 active projects - show me the project names, current status, percentage complete, and any recent work activity.
33
+ ```
34
+
35
+ ## Project Management
36
+
37
+ ### Weekly Project Dashboard
38
+ ```
39
+ Create a comprehensive weekly project report from Quickbase showing all active projects with their status, budget, timeline, assigned crews, total hours worked this week, and any tasks that are behind schedule.
40
+ ```
41
+
42
+ ### Update Task Progress
43
+ ```
44
+ In Quickbase, update the "Steel Frame Installation" task on the Commercial Building project to 75% complete. Also log that we installed beams on floors 4-5 today and the structural engineer approved all connections.
45
+ ```
46
+
47
+ ### Project Timeline Analysis
48
+ ```
49
+ Analyze our Quickbase project data and identify which projects are running behind schedule, which are ahead, and provide recommendations for resource reallocation to get back on track.
50
+ ```
51
+
52
+ ### Add New Project Task
53
+ ```
54
+ Add a new task to Quickbase for the Residential Apartments project: "HVAC Rough-in Building B" scheduled from June 1-15, 2025, assigned to the HVAC Crew, with 0% completion status.
55
+ ```
56
+
57
+ ### Project Budget Tracking
58
+ ```
59
+ Calculate the current labor costs for each active project in Quickbase by looking at total hours worked and crew rates. Compare this to the project budgets and show which projects are over/under budget.
60
+ ```
61
+
62
+ ## Workforce & Crew Management
63
+
64
+ ### Employee Productivity Report
65
+ ```
66
+ Generate an employee productivity report from Quickbase showing each worker's total hours in the last 30 days, their hourly rate, crew assignment, and calculate their contribution to project progress.
67
+ ```
68
+
69
+ ### Crew Assignment Optimization
70
+ ```
71
+ Analyze our Quickbase crew data and suggest optimal crew assignments based on current project needs, crew specializations, and workload distribution. Show which crews are overloaded or underutilized.
72
+ ```
73
+
74
+ ### Add New Employee
75
+ ```
76
+ Add a new employee to Quickbase: Sarah Martinez, HVAC Technician, $31.50/hour, assign her to the HVAC Crew, email: smartinez@construction.com.
77
+ ```
78
+
79
+ ### Crew Performance Analysis
80
+ ```
81
+ Compare the performance of all our crews in Quickbase by analyzing their total hours worked, number of tasks completed, and projects they've contributed to. Rank them by productivity.
82
+ ```
83
+
84
+ ### Training Needs Assessment
85
+ ```
86
+ Review our Quickbase employee data and identify who needs safety training based on their job roles. Show required certifications for each position and current training status.
87
+ ```
88
+
89
+ ## Materials & Inventory
90
+
91
+ ### Inventory Status Check
92
+ ```
93
+ Check our Quickbase materials inventory and show me everything that's below the reorder threshold. Group the results by supplier and include contact information so I can place orders.
94
+ ```
95
+
96
+ ### Material Usage Tracking
97
+ ```
98
+ Analyze material consumption from our Quickbase work logs for the Commercial Building project. Look for mentions of concrete, steel, electrical materials, and lumber in the work notes and summarize usage patterns.
99
+ ```
100
+
101
+ ### Automated Reorder Report
102
+ ```
103
+ Generate purchase orders from Quickbase for all materials below reorder levels. Group by supplier, calculate recommended order quantities (2x the reorder threshold), and format as a professional purchase order request.
104
+ ```
105
+
106
+ ### Material Cost Analysis
107
+ ```
108
+ Calculate the total material costs per project in Quickbase by analyzing inventory usage and current material quantities. Estimate the remaining material budget for each active project.
109
+ ```
110
+
111
+ ### Supplier Performance Review
112
+ ```
113
+ Evaluate our suppliers in Quickbase by looking at which materials we order most frequently, delivery reliability (based on when materials were restocked), and identify our most critical supplier relationships.
114
+ ```
115
+
116
+ ## Safety & Incident Management
117
+
118
+ ### Safety Dashboard
119
+ ```
120
+ Create a comprehensive safety dashboard from Quickbase showing: incident counts by type and location, recent safety events, crews with the most incidents, and overall safety trends for the last 90 days.
121
+ ```
122
+
123
+ ### Report New Safety Incident
124
+ ```
125
+ Log a new safety incident in Quickbase: Today a painter slipped on a wet floor in the Commercial Building. No injury occurred, but we've added additional warning signs and non-slip mats. Assign to Painting Crew and Safety Coordinator for follow-up.
126
+ ```
127
+
128
+ ### Safety Training Compliance
129
+ ```
130
+ Check our Quickbase system and identify which employees need safety training renewals based on their job roles. Show required certifications for electricians, equipment operators, and crew leaders.
131
+ ```
132
+
133
+ ### Incident Trend Analysis
134
+ ```
135
+ Analyze safety incident patterns in Quickbase over the last 6 months. Identify which types of incidents are most common, which projects or locations have the most issues, and recommend prevention strategies.
136
+ ```
137
+
138
+ ### Safety Performance by Location
139
+ ```
140
+ Compare safety performance across all our Quickbase project locations. Show incident rates, types of incidents, and identify which sites need additional safety measures or training.
141
+ ```
142
+
143
+ ## Reporting & Analytics
144
+
145
+ ### Executive Summary Report
146
+ ```
147
+ Generate an executive summary from Quickbase for our construction operations including: total active projects, workforce size, budget status, safety metrics, material costs, and key performance indicators for the current month.
148
+ ```
149
+
150
+ ### Resource Utilization Analysis
151
+ ```
152
+ Analyze our Quickbase data to show how efficiently we're using our resources. Calculate crew utilization rates, equipment usage, material turnover, and identify areas for improvement.
153
+ ```
154
+
155
+ ### Project Profitability Analysis
156
+ ```
157
+ Calculate project profitability from Quickbase by comparing budgets to actual costs (labor hours × rates + estimated materials). Rank projects by profit margin and identify the most/least profitable.
158
+ ```
159
+
160
+ ### Predictive Timeline Analysis
161
+ ```
162
+ Based on current progress rates in Quickbase, predict completion dates for all active projects. Identify projects that may miss their deadlines and suggest corrective actions.
163
+ ```
164
+
165
+ ### Client Project Portfolio
166
+ ```
167
+ Show me a client-focused view from Quickbase - for each client, list their projects, current status, total contract value, and any issues or concerns that need attention.
168
+ ```
169
+
170
+ ### Custom KPI Dashboard
171
+ ```
172
+ Create a custom KPI dashboard from Quickbase showing: projects on time vs. delayed, total labor hours this month vs. last month, safety incident rate, inventory turnover, and crew productivity metrics.
173
+ ```
174
+
175
+ ## Advanced Queries
176
+
177
+ ### Cross-Project Resource Analysis
178
+ ```
179
+ Analyze our Quickbase data to show which crews are working on multiple projects simultaneously. Identify potential scheduling conflicts and recommend optimizations for better project focus.
180
+ ```
181
+
182
+ ### Quality Control Tracking
183
+ ```
184
+ Track quality metrics across our Quickbase projects by analyzing work log notes for mentions of inspections, rework, quality issues, and approvals. Summarize quality performance by crew and project.
185
+ ```
186
+
187
+ ### Weather Impact Analysis
188
+ ```
189
+ Review our Quickbase work logs for weather-related delays or notes. Calculate lost productivity due to weather and identify which projects and crews are most affected by weather conditions.
190
+ ```
191
+
192
+ ### Supply Chain Risk Assessment
193
+ ```
194
+ Analyze our Quickbase supplier and material data to identify supply chain risks. Show which materials have single suppliers, long lead times, or frequent stockouts that could impact projects.
195
+ ```
196
+
197
+ ### Seasonal Workforce Planning
198
+ ```
199
+ Based on historical Quickbase data, analyze seasonal patterns in our workforce needs, project types, and resource requirements. Predict staffing needs for the next quarter.
200
+ ```
201
+
202
+ ## Tips for Using These Prompts
203
+
204
+ 1. **Be Specific**: Include project names, employee names, or specific dates when relevant
205
+ 2. **Ask for Follow-ups**: Add "and suggest next steps" or "and recommend actions" to get actionable insights
206
+ 3. **Combine Requests**: You can combine multiple queries, like "Show me safety incidents AND material usage for the Commercial Building project"
207
+ 4. **Request Formatting**: Specify how you want results displayed: "format as a table," "create a bulleted list," or "generate a professional report"
208
+ 5. **Set Time Ranges**: Use phrases like "in the last 30 days," "this quarter," or "since January 1st" to focus on specific periods
209
+
210
+ ## Sample Conversation Starters
211
+
212
+ - "I need to prepare for our Monday morning project meeting. Can you pull together a comprehensive status report from Quickbase?"
213
+ - "We're having safety issues on the Downtown site. Help me analyze what's happening and what we can do about it."
214
+ - "The client is asking about budget status. Can you calculate our current costs vs. budget for the Residential Apartments project?"
215
+ - "I need to optimize our crew assignments for next week. Show me who's available and what needs to be done."
216
+ - "Help me identify which materials we need to reorder urgently and which suppliers to contact."
217
+
218
+ Remember: Claude can access your Quickbase data in real-time through the MCP connector, so you'll get current information for all your queries!
@@ -0,0 +1,244 @@
1
+ # Deploying Quickbase MCP Server
2
+
3
+ This guide walks you through deploying Quickbase MCP Server for remote access and discovery through various platforms including Glama.ai.
4
+
5
+ ## Prerequisites
6
+
7
+ 1. **NPM Account**: For publishing to npm registry
8
+ 2. **Quickbase Credentials**: Your realm, user token, and app ID
9
+ 3. **Node.js & npm**: For building and publishing
10
+ 4. **Docker** (optional): For containerized deployment
11
+
12
+ ## Deployment Options
13
+
14
+ ### Option 1: NPM Package (Recommended for Glama.ai Discovery)
15
+
16
+ Glama.ai automatically indexes MCP servers published to NPM.
17
+
18
+ #### 1. Prepare for Publication
19
+
20
+ ```bash
21
+ # Clone this repository (if not already done)
22
+ git clone <repository-url>
23
+ cd MCP-Quickbase
24
+
25
+ # Build the project
26
+ npm install
27
+ npm run build
28
+ ```
29
+
30
+ #### 2. Update Package Information
31
+
32
+ Edit `package.json` to update:
33
+ - Version number
34
+ - Author information
35
+ - Repository URL
36
+ - Keywords for discovery
37
+
38
+ #### 3. Publish to NPM
39
+
40
+ ```bash
41
+ # Login to NPM (first time only)
42
+ npm login
43
+
44
+ # Publish the package
45
+ npm publish
46
+
47
+ # Glama.ai will automatically discover and index your package
48
+ ```
49
+
50
+ ### Option 2: Docker Deployment
51
+
52
+ For custom cloud deployments using the provided Docker configuration.
53
+
54
+ #### Build and Deploy
55
+
56
+ ```bash
57
+ # Build the Docker image
58
+ docker build -f Dockerfile.glama -t quickbase-mcp .
59
+
60
+ # Deploy to your preferred cloud platform
61
+ # (AWS, Google Cloud, Azure, etc.)
62
+ ```
63
+
64
+ ### Option 3: GitHub Integration
65
+
66
+ Submit to community MCP server registries for broader discovery.
67
+
68
+ ```bash
69
+ # Push to GitHub
70
+ git push origin main
71
+
72
+ # Submit to awesome-mcp-servers
73
+ # Fork https://github.com/punkpeye/awesome-mcp-servers
74
+ # Add your server following their contribution guidelines
75
+ ```
76
+
77
+ ## Getting Your Quickbase Credentials
78
+
79
+ ### Quickbase Realm Host
80
+ Your realm host is the domain you use to access Quickbase:
81
+ - Example: If you access Quickbase at `https://mycompany.quickbase.com`, your realm host is `mycompany.quickbase.com`
82
+
83
+ ### User Token
84
+ 1. Log into your Quickbase account
85
+ 2. Go to **My Preferences** → **My User Information**
86
+ 3. Click **Manage User Tokens**
87
+ 4. Create a new token with appropriate permissions
88
+ 5. Copy the token value
89
+
90
+ ### Application ID
91
+ 1. Open your Quickbase application
92
+ 2. Look at the URL: `https://mycompany.quickbase.com/db/bxxxxxxx`
93
+ 3. The application ID is the `bxxxxxxx` part (starts with 'b')
94
+
95
+ ## Configuration for Claude Desktop
96
+
97
+ After deployment, configure the MCP server in Claude Desktop:
98
+
99
+ ### NPM Package Installation
100
+ ```json
101
+ {
102
+ "mcpServers": {
103
+ "quickbase": {
104
+ "command": "npm",
105
+ "args": ["exec", "mcp-quickbase"],
106
+ "env": {
107
+ "QUICKBASE_REALM_HOST": "your-realm.quickbase.com",
108
+ "QUICKBASE_USER_TOKEN": "your-token",
109
+ "QUICKBASE_APP_ID": "your-app-id"
110
+ }
111
+ }
112
+ }
113
+ }
114
+ ```
115
+
116
+ ### Local Development
117
+ ```json
118
+ {
119
+ "mcpServers": {
120
+ "quickbase": {
121
+ "command": "node",
122
+ "args": ["path/to/MCP-Quickbase/dist/mcp-stdio-server.js"],
123
+ "env": {
124
+ "QUICKBASE_REALM_HOST": "your-realm.quickbase.com",
125
+ "QUICKBASE_USER_TOKEN": "your-token",
126
+ "QUICKBASE_APP_ID": "your-app-id"
127
+ }
128
+ }
129
+ }
130
+ }
131
+ ```
132
+
133
+ ## Environment Variables
134
+
135
+ ### Required
136
+ - `QUICKBASE_REALM_HOST`: Your Quickbase realm (e.g., `mycompany.quickbase.com`)
137
+ - `QUICKBASE_USER_TOKEN`: Your Quickbase user token
138
+ - `QUICKBASE_APP_ID`: Your Quickbase application ID
139
+
140
+ ### Optional
141
+ - `QUICKBASE_CACHE_ENABLED`: `true` (default) - Enable caching for better performance
142
+ - `QUICKBASE_CACHE_TTL`: `3600` (1 hour, default) - Cache time-to-live in seconds
143
+ - `DEBUG`: `false` (default) - Enable debug logging
144
+ - `LOG_LEVEL`: `INFO` (default) - Logging level (ERROR, WARN, INFO, DEBUG)
145
+
146
+ ## Local Testing
147
+
148
+ Before deploying, test the MCP server locally:
149
+
150
+ ```bash
151
+ # Build and test
152
+ ./deploy.sh
153
+
154
+ # Or manually:
155
+ npm install
156
+ npm run build
157
+ node dist/mcp-stdio-server.js
158
+ ```
159
+
160
+ ## Usage Examples
161
+
162
+ Once deployed and configured, you can use these natural language prompts in Claude:
163
+
164
+ ### Daily Operations
165
+ ```
166
+ "Check our Quickbase system and show me which crews are working today"
167
+ ```
168
+
169
+ ### Project Management
170
+ ```
171
+ "Give me a status update on all active projects with budget and timeline"
172
+ ```
173
+
174
+ ### Safety Reporting
175
+ ```
176
+ "Generate a safety dashboard showing incidents by type and location"
177
+ ```
178
+
179
+ ### Inventory Management
180
+ ```
181
+ "Show me materials below reorder threshold and create purchase orders"
182
+ ```
183
+
184
+ ## How Glama.ai Discovery Works
185
+
186
+ Glama.ai automatically indexes MCP servers through several methods:
187
+
188
+ 1. **NPM Registry**: Automatically discovers packages with MCP-related keywords
189
+ 2. **GitHub Repositories**: Indexes repositories tagged with MCP-related topics
190
+ 3. **Community Submissions**: Accepts submissions through awesome-mcp-servers
191
+
192
+ Your package will appear on Glama.ai within 24-48 hours of publication to NPM.
193
+
194
+ ## Monitoring and Troubleshooting
195
+
196
+ ### Common Issues
197
+
198
+ **Connection Errors**: Verify your Quickbase credentials and network connectivity
199
+ **Permission Errors**: Ensure your user token has appropriate permissions
200
+ **Package Not Found**: Check that your NPM package is public and properly tagged
201
+
202
+ ### Debug Mode
203
+ Enable verbose logging by setting:
204
+ ```bash
205
+ DEBUG=true
206
+ LOG_LEVEL=DEBUG
207
+ ```
208
+
209
+ ## Security Best Practices
210
+
211
+ 1. **User Token**: Never commit tokens to version control
212
+ 2. **Permissions**: Use minimum required Quickbase permissions
213
+ 3. **Network**: All connections use HTTPS/TLS
214
+ 4. **Dependencies**: Keep dependencies updated for security patches
215
+
216
+ ## Performance Optimization
217
+
218
+ - **Caching**: Enabled by default to reduce API calls and improve response times
219
+ - **Pagination**: Handles large datasets efficiently
220
+ - **Retry Logic**: Automatic retry with exponential backoff for transient failures
221
+
222
+ ## Support and Community
223
+
224
+ ### Getting Help
225
+ 1. Check the [Claude Prompts documentation](claude-prompts.md)
226
+ 2. Review [Quick Reference guide](quick-reference.md)
227
+ 3. File issues in this repository
228
+ 4. Join the MCP community discussions
229
+
230
+ ### Contributing
231
+ 1. Fork the repository
232
+ 2. Create a feature branch
233
+ 3. Add tests for new functionality
234
+ 4. Submit a pull request
235
+
236
+ ## Next Steps
237
+
238
+ 1. **Choose Deployment Option**: NPM publication recommended for ease of discovery
239
+ 2. **Configure Credentials**: Set up your Quickbase connection
240
+ 3. **Test Integration**: Verify MCP server works with Claude Desktop
241
+ 4. **Explore Examples**: Try prompts from the documentation
242
+ 5. **Customize for Your Needs**: Adapt the schema and prompts to your use case
243
+
244
+ For detailed usage examples, see [claude-prompts.md](claude-prompts.md) and [quick-reference.md](quick-reference.md).