Skip to main content
The Nash documentation is available as a Model Context Protocol (MCP) server. Connect it to your AI assistant and the assistant can search this site and read any page while it helps you build — instead of guessing from training data or a stale web search. This server is read-only and reaches nothing but the documentation. To let an agent act on your deliveries — create orders, check live status, request refunds — connect the Nash MCP server instead. The two are complementary, and a coding agent doing a Nash integration benefits from both.

​
What the server exposes

The server gives an agent three tools, and the agent decides when to reach for each one based on the conversation:
  • Search — find pages relevant to a query, returned as snippets with titles and links.
  • Read — retrieve full pages as Markdown, navigate the site, and pull specific sections, including several pages in one call.
  • Submit feedback — report a page that’s wrong, outdated, or confusing. The report lands with the Nash docs team.
Everything in the site navigation is indexed, including the API reference, so an agent can look up a request body or a webhook payload the same way it looks up a concept page. Agents and tools that support discovery can locate the server without being told where it is: https://docs.usenash.com/.well-known/mcp returns a JSON document with the server URL, and https://docs.usenash.com/.well-known/mcp/server-card.json adds the advertised tools and their schemas.

​
Connect a client

The fastest route is the menu at the top of any docs page: Connect to Cursor and Connect to VS Code install the server in one click, and Copy MCP server URL puts the address on your clipboard for everything else.
1

Add the connector

  1. Open Connectors in the Claude settings.
  2. Click Add custom connector.
  3. Name it Nash Docs and set the URL to https://docs.usenash.com/mcp.
  4. Click Add.
2

Use it in a chat

Click the attachments button (the plus icon), select Nash Docs, and ask your question.

​
Try it

Once connected, ask something the assistant would otherwise have to guess at:
A well-behaved agent searches the docs, reads the Create Order and Select Quote pages, and answers from what’s there. If it reports a page as wrong along the way, that feedback reaches us.

​
Limits and scope

  • The server searches the current published documentation. Anything not on this site — your organization’s configuration, your orders, Portal-only settings — is out of its reach. Use the Nash MCP server for live data.
  • Requests are rate limited per client and per site. A client that hits the limit gets an HTTP 429 and should back off; limits reset on a rolling hourly window.
  • Connecting several documentation servers to one assistant makes every search more expensive. Keep only the ones relevant to what you’re building connected.

Nash MCP server

Let an agent operate deliveries — create, track, refund — with your API key.

Using LLMs with the Nash API

Paste-able references for assistants that can’t connect to MCP.