Nerve MCP Server

What is Nerve MCP Server about?

Provides an MCP server implementation that bridges AI assistants with the Nerve API, allowing natural‑language instructions to be translated into concrete API requests.

How to use Nerve MCP Server?

1. Create a Nerve account and generate an API key in the Settings page.
2. Add the server definition to your .cursor/mcp.json (or claude_desktop_config.json on macOS) with the command, arguments, and environment variables shown below.
3. Run the server using the provided command (e.g., uv run nerve-mcp).
4. Enable third‑party integrations on the Nerve dashboard to expose the desired SaaS tools.
5. Issue natural‑language prompts to your AI assistant; the server will translate them to Nerve API calls (e.g., /search).

Key Features

• Simple configuration via a JSON snippet in the MCP client config file.
• Secure authentication through NERVE_API_KEY environment variable.
• Supports environment selection (prod, staging, etc.) via NERVE_ENVIRONMENT.
• Leverages the Model Context Protocol to let AI plan and execute API calls automatically.
• Extensible: add any Nerve endpoint and the AI can invoke it without code changes.

Use Cases

• Email triage: Ask the assistant, “What emails have I gotten with customer feedback?” and receive a filtered list via the /search endpoint.
• CRM data lookup: Retrieve contact details or recent interactions directly from Nerve.
• Task automation: Trigger creation of tickets, calendar events, or Slack messages based on conversational commands.
• Reporting: Generate on‑demand analytics by calling Nerve’s reporting APIs through natural language.

FAQ

Q: Which command runs the server? A: The example uses uv run nerve-mcp; replace with the appropriate command for your environment if needed.

Q: Where do I place the configuration? A: In .cursor/mcp.json for most MCP clients, or claude_desktop_config.json on macOS.

Q: How do I secure the API key? A: Store it only in the env section of the config and avoid committing the file to version control.

Q: Can I change the environment? A: Yes, set NERVE_ENVIRONMENT to prod, staging, or any custom environment supported by Nerve.

Q: What if I need additional Nerve endpoints? A: Once the server is running, any endpoint documented in the Nerve API can be called via MCP prompts; no code changes are required.

Nerve MCP Server

This project implements an MCP server for the Nerve API.

Installation

1. Setting up Integration in Nerve:

Go to https://usenerve.com/ and create an account.

Continue to your Settings page to create an API key to use for the client.

2. Adding MCP config to your client:

Add the following to your .cursor/mcp.json or claude_desktop_config.json (MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json)

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

Don't forget to replace API_KEY with your own key. Find it from your Settings tab:

3. Enable third party integrations:

Navigate to your integrations page on Nerve to conenct to the various SaaS tools you use.

Examples

1. Using the following instruction

What emails have I gotten with customer feedback?

AI will plan one API calls, /search

(more examples coming soon)

Development

Execute

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