Nerve

Implements an MCP server for the Nerve API to enable programmatic access and management through MCP clients.

javascript

1

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months 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

{
  "mcpServers": {
    "nerve-hq-nerve-mcp-server": {
      "command": "uv",
      "args": [
        "--directory",
        "/<ABSOLUTE_PATH>/nerve-mcp-server",
        "run",
        "nerve-mcp"
      ],
      "env": {
        "NERVE_API_KEY": "<API_KEY>",
        "NERVE_ENVIRONMENT": "prod"
      }
    }
  }
}

You run an MCP server that connects your client to the Nerve API, enabling seamless, programmatic access to Nerve data and actions. This server handles the MCP protocol locally so your client can request information and perform operations through a consistent interface.

How to use

To use the Nerve MCP Server with your MCP client, provide the server configuration to your client so it can launch and communicate with the Nerve backend. You will supply an API key tied to your Nerve account and specify the environment you are targeting (prod in the example). Enable the MCP integration on your Nerve integrations page to connect to your preferred SaaS tools.

Use the runtime command shown in the configuration to start the local MCP service. When you start the server, your MCP client can send requests that the Nerve MCP Server will translate into Nerve API calls.

How to install

Prerequisites you need before installing include a runtime capable of executing the MCP server process (the example uses a universal runner) and access to the Nerve API key for authentication.

Prepare your MCP config on the client side. Create or edit your MCP configuration file to include the Nerve MCP server. The snippet below shows the exact MCP server entry you should place in your client configuration.

{
  "mcpServers": {
    "nerve": {
      "command": "uv",
      "args": [
        "--directory",
        "/<ABSOLUTE_PATH>/nerve-mcp-server",
        "run",
        "nerve-mcp"
      ],
      "env": {
      	"NERVE_API_KEY": "<API_KEY>",
      	"NERVE_ENVIRONMENT": "prod"
      }
    }
  }
}

Additional setup steps

Enable third party integrations on the Nerve platform to connect to the various SaaS tools you use. This enables the MCP server to route actions and data to the appropriate services.

Development

To run the MCP server during development, use the development command shown in the example. This starts the local MCP process with the necessary API key.

NERVE_API_KEY='<API_KEY>' uv run nerve-mcp

Available tools

search

Executes a planned API call to retrieve data matching criteria from KNERVE services, such as emails with customer feedback using a /search endpoint.