CRM

You run a local and remote MCP server for Medicus CRM to access a shared set of 18 CRM tools. You can develop and test locally via STDIO and expose a remote HTTP endpoint for production-style access, with token-based authentication to keep data secure.

How to use

You can interact with the Medicus CRM MCP server using either the local STDIO mode or the remote HTTP mode. Use STDIO when you want full, local tool execution from MCP clients running on the same machine. Use HTTP mode to test remote access patterns and to expose the MCP endpoint to other services or dashboards. When testing remotely, secure access with your MCP token.

How to install

Prerequisites include Node.js 18+ and a Supabase project with a service role key. You also need to prepare environment variables for the MCP token and Supabase credentials.

npm install
cp env.example .env.local

Configure your environment variables in `.env.local`:

SUPABASE_URL=your_supabase_url_here
SUPABASE_SERVICE_ROLE_KEY=your_supabase_service_role_key_here
MCP_TOKEN=your_long_random_token_here

Additional setup steps

The server supports both local development via STDIO and remote testing via HTTP. The STDIO mode provides full MCP tool execution, while the HTTP mode offers tool listing and basic protocol for remote access.

To start in STDIO mode for local MCP clients, run the following command from your project root.

npm run mcp:stdio

Running in HTTP mode for testing remote access

To run the HTTP server for testing remote access, use the HTTP start script.

npm run dev

Test your HTTP MCP endpoint with the inspector

Verify the HTTP endpoint by connecting with the MCP Inspector, using your token.

npx @modelcontextprotocol/inspector http://localhost:3000/api/mcp?token=your_token