@daylight-labs/sharedb-mcp 0.1.5 → 0.1.6

package/dist/tools/auth.js

@@ -23,13 +23,13 @@ async function getEmailIntegrationInfo(appId) {
 export const authTools = [
     {
         name: 'get_api_endpoints',
-        description: 'Get all ShareDB API endpoints (Auth, PostgREST, Admin). Use this to get the correct URLs for implementing API calls in your app. Pass a database_id to see endpoints for specific tables.',
+        description: 'Get all ShareDB API endpoints (Auth, PostgREST, Admin, Email). IMPORTANT: Always pass database_id when working with an existing app - use the staging database ID. This returns table-specific endpoints and integration info (like email). Without database_id, only generic auth endpoints are shown.',
         inputSchema: {
             type: 'object',
             properties: {
                 database_id: {
                     type: 'string',
-                    description: 'Optional database ID to list specific table endpoints',
+                    description: 'The staging database ID for the app. Always pass this when working with an existing app to get table endpoints and integration info.',
                 },
             },
             required: [],
@@ -100,30 +100,32 @@ export async function handleAuthTool(name, args) {
                         emailSection = {
                             description: 'Send transactional emails via AWS SES',
                             status: enabled ? 'enabled' : 'disabled',
-                            endpoint: `POST ${config.adminApiUrl}/admin/apps/${appId}/integrations/email/send`,
+                            endpoint: `POST <API_BASE_URL>/admin/apps/<app_id>/integrations/email/send`,
                             authentication: 'Include admin API token: Authorization: Bearer <token>',
                             fromAddress: emailInfo.fromAddress,
                             rateLimit: `1 email per ${emailInfo.rateLimitSeconds} seconds per app`,
+                            currentAppId: appId,
                             requestBody: {
                                 to: 'string (required) - recipient email address',
                                 subject: 'string (required) - email subject line',
                                 body: 'string (required) - plain text email body',
                                 html: 'string (optional) - HTML email body',
                             },
-                            example: `fetch('${config.adminApiUrl}/admin/apps/${appId}/integrations/email/send', {
+                            example: `fetch(\`\${API_BASE_URL}/admin/apps/\${APP_ID}/integrations/email/send\`, {
   method: 'POST',
   headers: {
     'Content-Type': 'application/json',
-    'Authorization': 'Bearer <your-api-token>'
+    'Authorization': \`Bearer \${API_TOKEN}\`
   },
   body: JSON.stringify({
     to: 'user@example.com',
-    subject: 'Welcome to ${appName}!',
+    subject: 'Welcome!',
     body: 'Thanks for signing up.',
     html: '<h1>Welcome!</h1><p>Thanks for signing up.</p>'
   })
 })`,
                             importantNotes: [
+                                'Store API_BASE_URL, APP_ID, and API_TOKEN in environment variables or config - never hardcode',
                                 enabled
                                     ? 'Email integration is ENABLED for this app'
                                     : 'Email integration is DISABLED - enable it in the Admin UI before sending',

package/dist/tools/schema.js

@@ -227,12 +227,17 @@ fetch(\`\${API_URL}/todos\`, { headers: { Authorization: \`Bearer \${token}\` }
 5. When ready, use the Admin UI to promote schema to production
 6. Use preview_promotion to see what will be promoted
 
+## Available Integrations
+
+- **Email** - Send transactional emails via AWS SES (supports custom domains)
+
 ## Next steps
 1. Use stage_change to add tables
 2. Use apply_changes to create them
 3. Use start_postgrest to start the REST API
 4. Implement auth in your app using the Auth API
 5. Query data using the REST API
+6. Enable integrations as needed (email, etc.)
 
 ---
 **NOTE FOR ASSISTANT:** ShareDB users are often non-technical builders who need guidance through technical steps. When helping them:
@@ -292,6 +297,10 @@ ${standaloneDbList ? `### Standalone Databases\n${standaloneDbList}` : ''}
 
 Use get_api_endpoints with database_id for full endpoint documentation.
 
+## Available Integrations
+
+- **Email** - Send transactional emails via AWS SES (supports custom domains)
+
 ---
 **NOTE FOR ASSISTANT:** ShareDB users are often non-technical builders. Proactively help them with technical tasks like running commands, starting dev servers, and debugging. Explain things in simple terms.`,
                         },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@daylight-labs/sharedb-mcp",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "description": "MCP server for ShareDB schema management and development",
   "type": "module",
   "main": "./dist/index.js",