Skip to main content
NexusFeed ships as a Model Context Protocol (MCP) server that exposes the same LTL and ABC endpoints as tools any MCP-compatible agent can call. Install it with pip, set your API key as an environment variable, and add it to your client’s MCP config.

​
Install

pip install nexusfeed-mcp
This installs two entry points:
  • nexusfeed-ltl — LTL fuel surcharge tools (3 tools: list_carriers, get_fuel_surcharge, get_accessorials)
  • nexusfeed-abc — ABC license compliance tools (2 tools: search_licenses, get_license)
You can run either or both. The LTL and ABC products bill separately, so install only what you have an API key for.
Already have an agent running? The same MCP server is auto-discoverable from the Official MCP Registry, Smithery, Glama, PulseMCP, and the Cline Marketplace. If your client supports one-click install from a directory, you don’t need to edit config files at all.

​
Get an API key

See Quickstart for the RapidAPI subscription flow. You need one key per product — or a single dual-scoped key if you subscribe to both listings with the same RapidAPI account.

​
Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows) and add: 
{
  "mcpServers": {
    "nexusfeed-ltl": {
      "command": "nexusfeed-ltl",
      "env": {
        "MCP_API_KEY": "<your-api-key>"
      }
    },
    "nexusfeed-abc": {
      "command": "nexusfeed-abc",
      "env": {
        "MCP_API_KEY": "<your-api-key>"
      }
    }
  }
}
Restart Claude Desktop. The tools appear under the plug icon in the chat input.

​
Cursor

Edit ~/.cursor/mcp.json (or the IDE setting pane) and add the same mcpServers block as Claude Desktop. Cursor supports MCP via the same configuration schema.

​
Cline (VS Code)

Open the Cline extension’s MCP settings panel and add a new server pointing to nexusfeed-ltl or nexusfeed-abc. Pass MCP_API_KEY via the env vars field. Cline is also listed in the Cline Marketplace for one-click install — submission at issue #1276.

​
Windsurf

Windsurf’s MCP config file is at ~/.codeium/windsurf/mcp_config.json. Use the same schema as Claude Desktop.

​
Zed

Edit ~/.config/zed/settings.json: 
{
  "context_servers": {
    "nexusfeed-ltl": {
      "command": {
        "path": "nexusfeed-ltl",
        "env": {"MCP_API_KEY": "<your-api-key>"}
      }
    }
  }
}

​
Transport options

nexusfeed-mcp defaults to stdio transport, which is what all the clients above use. It also supports Streamable HTTP at https://api.nexusfeed.dev/mcp-ltl/ and https://api.nexusfeed.dev/mcp-abc/ if you want to point an HTTP-capable MCP client directly at the hosted server without running a local process.

​
Verify

Once configured, in your agent ask: “List all LTL carriers NexusFeed supports.” A correctly-installed server will respond with a call to the list_carriers tool and show ten carriers. If it doesn’t, check the MCP tools reference for debugging tips.