Eka Care MCP documentation with integration steps

docs.json

@@ -923,6 +923,27 @@
                             }
                         ]
                     },
+                    {
+                        "tab": "Eka MCP",
+                        "groups": [
+                            {
+                                "group": "Get Started",
+                                "icon": "rocket",
+                                "pages": [
+                                    "mcp/introduction",
+                                    "mcp/supported-tools",
+                                    "mcp/authentication"
+                                ]
+                            },
+                            {
+                                "group": "Integrations",
+                                "icon": "plug",
+                                "pages": [
+                                    "mcp/integrations/custom-client"
+                                ]
+                            }
+                        ]
+                    },
                     {
                         "tab": "CookBook",
                         "groups": [

mcp/authentication.mdx

@@ -0,0 +1,195 @@
+---
+title: Authentication
+description: Securely connect your AI assistant to Eka.care
+---
+
+## Overview
+
+Eka.care MCP supports two authentication methods to fit different integration needs:
+
+<CardGroup cols={2}>
+  <Card title="🔐 OIDC Flow (Recommended)" icon="shield-check">
+    **Best for:** Healthcare providers and clinics
+
+    Auto-authenticate with your Eka.care account. No manual credential management needed.
+  </Card>
+  <Card title="🔑 Client Credentials" icon="key">
+    **Best for:** Third-party integrations
+
+    Use API credentials (Client ID, Secret, API Key) for programmatic access.
+  </Card>
+</CardGroup>
+
+---
+
+## Method 1: OIDC Flow (Auto-Authentication)
+
+This is the **easiest and most secure** method. Your AI assistant authenticates using your Eka.care login, just like logging into the dashboard.
+
+### How It Works
+
+<Steps>
+  <Step title="You start your MCP client">
+    Claude Desktop or any MCP-compatible client
+  </Step>
+  <Step title="MCP initiates OIDC flow">
+    Opens a secure browser window
+  </Step>
+  <Step title="You log in to Eka.care">
+    Use your existing Eka.care credentials
+  </Step>
+  <Step title="Connection established">
+    Your AI assistant now has secure access
+  </Step>
+</Steps>
+
+<Frame>
+  <img src="/images/OIDC.png" alt="OIDC Authentication Flow" />
+  {/* Screenshot placeholder: Diagram showing OIDC flow steps */}
+</Frame>
+
+## Method 2: Client Credentials
+
+Use this method if you have API credentials (Client ID, Client Secret, API Key) from the Eka.care team.
+
+### How It Works
+
+Your MCP server authenticates directly with Eka.care APIs using:
+- **Client ID**: Your application identifier
+- **Client Secret**: Secret key for authentication
+- **API Key**: Additional security layer (optional but recommended)
+
+### Setup Client Credentials
+
+**1. Get your credentials:**
+
+Contact **ekaconnect@eka.care** and request:
+- Client ID
+- Client Secret  
+- API Key
+
+**2. Configure your `.env` file:**
+
+```bash .env
+# API Configuration
+EKA_API_BASE_URL=https://api.eka.care
+
+# Client Credentials
+EKA_CLIENT_ID=your_client_id_here
+EKA_CLIENT_SECRET=your_client_secret_here
+EKA_API_KEY=your_api_key_here
+
+# Server Settings (optional)
+EKA_MCP_SERVER_HOST=localhost
+EKA_MCP_SERVER_PORT=8000
+EKA_LOG_LEVEL=INFO
+```
+
+<Warning>
+**Security Best Practices:**
+- Never commit credentials to version control
+- Use `.gitignore` to exclude `.env` file
+- Rotate credentials periodically
+- Use different credentials for development and production
+</Warning>
+
+**3. Update Claude Desktop config:**
+
+```json claude_desktop_config.json
+{
+  "mcpServers": {
+    "eka-care": {
+      "command": "/full/path/to/.venv/bin/python",
+      "args": ["-m", "eka_mcp_sdk.server"],
+      "env": {
+        "EKA_CLIENT_ID": "your_client_id_here",
+        "EKA_CLIENT_SECRET": "your_client_secret_here",
+        "EKA_API_KEY": "your_api_key_here",
+        "EKA_API_BASE_URL": "https://api.eka.care"
+      }
+    }
+  }
+}
+```
+
+**4. Test your connection:**
+
+```bash
+# Start the MCP server
+eka-mcp-server
+```
+
+You should see:
+```
+INFO: Authentication successful
+INFO: MCP Server running on http://localhost:8000
+```
+
+### Credential Management Tips
+
+<AccordionGroup>
+  <Accordion title="How to test credentials">
+    **Quick test with curl:**
+    ```bash
+    curl -X POST https://api.eka.care/api/v1/auth/token \
+      -H "Content-Type: application/json" \
+      -H "X-API-KEY: your_api_key" \
+      -d '{
+        "client_id": "your_client_id",
+        "client_secret": "your_client_secret",
+        "grant_type": "client_credentials"
+      }'
+    ```
+
+    Should return an access token if credentials are valid.
+  </Accordion>
+
+  <Accordion title="Token expiration">
+    **Automatic refresh:** The MCP server automatically refreshes tokens before they expire.
+
+    **Default expiration:** Tokens typically last 1 hour and are refreshed automatically.
+
+    **No action needed:** You don't need to manually manage token lifecycle.
+  </Accordion>
+
+  <Accordion title="Multiple environments">
+    **Development:**
+    ```bash .env.development
+    EKA_CLIENT_ID=dev_client_id
+    EKA_CLIENT_SECRET=dev_client_secret
+    EKA_API_KEY=dev_api_key
+    EKA_API_BASE_URL=https://api-dev.eka.care
+    ```
+
+    **Production:**
+    ```bash .env.production
+    EKA_CLIENT_ID=prod_client_id
+    EKA_CLIENT_SECRET=prod_client_secret
+    EKA_API_KEY=prod_api_key
+    EKA_API_BASE_URL=https://api.eka.care
+    ```
+  </Accordion>
+
+  <Accordion title="Credential rotation">
+    **When to rotate:**
+    - Every 90 days (recommended)
+    - If credentials may be compromised
+    - When team members leave
+
+    **How to rotate:**
+    1. Contact ekaconnect@eka.care for new credentials
+    2. Update your `.env` file
+    3. Restart the MCP server
+    4. Update Claude Desktop config if needed
+  </Accordion>
+</AccordionGroup>
+
+---
+
+<Note>
+**Need Credentials?** Contact **ekaconnect@eka.care** with:
+- Your organization name
+- Integration type (OIDC or Client Credentials)
+- Use case description
+- Expected API usage volume
+</Note>