NerveSparks MCP Server

MCP server for creating Twilio calls via NerveSparks CI API.

Using in Cursor

To use this MCP server in Cursor, you need to configure it in Cursor's MCP settings.

Prerequisites

1. Build the Docker image (if you haven't already):

   docker build -t nervesparks-mcp:latest .

   Or if using a published image from Docker Hub:

   docker pull YOUR_DOCKERHUB_USERNAME/nervesparks-mcp:latest
   docker tag YOUR_DOCKERHUB_USERNAME/nervesparks-mcp:latest nervesparks-mcp:latest

2. Ensure Docker Desktop is running on your machine.

Configuration Steps

1. Open Cursor's MCP configuration file:

   • The configuration file is located at: ~/.cursor/mcp.json (or %APPDATA%\Cursor\mcp.json on Windows)
   • If the file doesn't exist, create it.

2. Add the MCP server configuration:

   Add the following configuration to your mcp.json file:

   {
     "mcpServers": {
       "nervesparks-python-mcp": {
         "command": "docker",
         "args": [
           "run",
           "-i",
           "--rm",
           "nervesparks-mcp:latest"
         ]
       }
     }
   }

   Note: If you already have other MCP servers configured, add the nervesparks-python-mcp entry to the existing mcpServers object.

3. Restart Cursor to load the new MCP server configuration.

4. Verify the connection:

   • The MCP server should now be available in Cursor
   • You can test it by asking Cursor to use the ping tool or createCall tool
   • Check Cursor's MCP status/connection indicators to confirm it's connected

Example Configuration File

If this is your first MCP server, your ~/.cursor/mcp.json should look like:

{
  "mcpServers": {
    "nervesparks-python-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "nervesparks-mcp:latest"
      ]
    }
  }
}

Troubleshooting

• MCP server not appearing in Cursor:

  • Verify the Docker image exists: docker images | grep nervesparks-mcp
  • Check that Docker Desktop is running
  • Ensure the JSON syntax in mcp.json is valid
  • Restart Cursor after making configuration changes

• Connection errors:

  • Check Docker logs if the container fails to start
  • Verify the image name matches exactly: nervesparks-mcp:latest

Publishing to Docker Hub

To make your image available for others to use, publish it to Docker Hub:

Prerequisites

• Docker Hub account (create one at https://hub.docker.com)
• Docker Desktop installed and running

Publishing Steps

1. Login to Docker Hub:

   docker login

2. Tag your image with your Docker Hub username:

   docker build -t YOUR_DOCKERHUB_USERNAME/nervesparks-mcp:latest .
   docker tag nervesparks-mcp:latest YOUR_DOCKERHUB_USERNAME/nervesparks-mcp:latest

3. Push to Docker Hub:

   docker push YOUR_DOCKERHUB_USERNAME/nervesparks-mcp:latest

   Or use the provided script:

   chmod +x publish.sh
   ./publish.sh YOUR_DOCKERHUB_USERNAME

4. Make it public (optional):

   • Go to https://hub.docker.com
   • Find your repository: YOUR_DOCKERHUB_USERNAME/nervesparks-mcp
   • Go to Settings → Visibility → Make it public

Using the Published Image

Once published, anyone can pull and use your image:

docker pull YOUR_DOCKERHUB_USERNAME/nervesparks-mcp:latest
docker run -it --name nervesparks-mcp-server YOUR_DOCKERHUB_USERNAME/nervesparks-mcp:latest

Or update docker-compose.yml to use the published image:

services:
  mcp-server:
    image: YOUR_DOCKERHUB_USERNAME/nervesparks-mcp:latest
    # ... rest of config

Docker Deployment

Prerequisites

• Docker Desktop installed and running
• Docker Compose (included with Docker Desktop)

Quick Start

1. Build and run with Docker Compose:

   docker-compose up --build

2. Run in detached mode (background):

   docker-compose up -d --build

3. View logs:

   docker-compose logs -f

4. Stop the container:

   docker-compose down

Using Docker directly

1. Build the image:

   docker build -t nervesparks-mcp:latest .

2. Run the container:

   docker run -it --name nervesparks-mcp-server nervesparks-mcp:latest

3. Run in detached mode:

   docker run -d --name nervesparks-mcp-server nervesparks-mcp:latest

Connecting to MCP Server

Since this MCP server uses stdio, you'll need to configure your MCP client to connect to the Docker container's stdio. The exact configuration depends on your MCP client setup.

Troubleshooting

• Check if container is running:

  docker ps

• View container logs:

  docker logs nervesparks-mcp-server

• Restart container:

  docker restart nervesparks-mcp-server

• Remove container:

  docker rm -f nervesparks-mcp-server