ElevenLabs MCP Backend

Provides real-time order lookups by connecting ElevenLabs Agents to Supabase via MCP with health and testing endpoints.
  • typescript

0

GitHub Stars

typescript

Language

3 months ago

First Indexed

3 weeks ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

You run a production-grade MCP (Model Context Protocol) backend that connects ElevenLabs Agents to real-time order data stored in Supabase. This server exposes a JSON-RPC MCP endpoint for tools like lookup_order, a health check, and a REST backup path so voice agents can securely look up order details on demand.

How to use

You connect an MCP client to the server to access real-time order information. The MCP endpoint exposes a set of methods that your agent can call. Use the tools list to discover available actions, and call the lookup_order tool to retrieve order details by ID. All calls require Bearer token authentication. The REST backup endpoint provides an alternative path for testing or debugging outside of MCP.

How to install

Prerequisites you need before installation:

  • Node.js 18+ is installed on your machine

  • Supabase account and a project with an orders table

  • An ElevenLabs account with Agents feature enabled

# 1. Clone the backend repository
git clone <your-repo>
cd elevenlabs-mcp-backend

# 2. Install dependencies
npm install

# 3. Set up Supabase (schema and seed data) will be performed via SQL editor in your Supabase project

Additional setup steps

Configure environment variables to authorize the MCP server and connect to Supabase. Create a file named .env (copied from a sample) and fill in the values.

PORT=3000
MCP_SECRET=your-secure-random-string-here
SUPABASE_URL=https://your-project.supabase.co
SUPABASE_SERVICE_ROLE_KEY=your-service-role-key

Start the server

Run the server in development or production mode. The development flow enables hot reloading, while the production flow builds and starts the compiled server.

# Development with hot reload
npm run dev

# Production build and start
npm run build
npm start

Deployment notes

Deploy to a hosting provider that can expose a public URL and support environment variables. Common options include Railway, Render, Vercel, Fly.io, or similar. Ensure you set the same environment variables you use locally (MCP_SECRET, SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY) in your hosting environment.

Security and access

Only agents with the attached MCP server can call the lookup_order tool. Each agent must have the MCP server configured individually. Use Bearer token authentication for MCP calls and keep the MCP_SECRET secret.

Testing the endpoints

You can verify the service health and MCP tooling via the provided endpoints. Use the health endpoint to confirm the service is running and the MCP endpoint to list and call tools.

Available tools

lookup_order

Retrieves order details by order_id. Returns both a human-readable content block and a structured data map with order_id, status, ETA, carrier, and tracking information.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational