Let your AI assistant look up NSNs for itself
Model Context Protocol (MCP) is the standard way to give an AI assistant tools. Connect ours once and your assistant can search the federal catalog, cross-reference part numbers and identify CAGE codes while it works.
What you can ask once it is connected
"What is NSN 5305-00-123-4567, and who makes it?"
"Find the NSN for part number MS35338-44 and tell me the unit of issue and government price."
"Here are 20 part numbers from an RFQ. Which have NSNs, and which CAGE codes are approved sources?"
"Which company is CAGE 1ABC2, and is the code still active?"
"What is the DEMIL code for this item and what does it mean?"
"What kinds of items are in Federal Supply Class 5305?"
The assistant answers from catalog records it fetches, and can show you the record it used.
Connect in one step
| Address | https://api.nsnlookup.com/mcp |
|---|---|
| Transport | Streamable HTTP |
| Sign-in | Header Authorization: Bearer nsn_your_key |
| Access | Read-only. Uses the same key and plan as the REST API |
Claude Code
claude mcp add --transport http nsnlookup https://api.nsnlookup.com/mcp \
--header "Authorization: Bearer nsn_your_key"VS Code (.vscode/mcp.json)
{
"servers": {
"nsnlookup": {
"type": "http",
"url": "https://api.nsnlookup.com/mcp",
"headers": { "Authorization": "Bearer nsn_your_key" }
}
}
}Cursor and other clients (mcp.json)
{
"mcpServers": {
"nsnlookup": {
"url": "https://api.nsnlookup.com/mcp",
"headers": { "Authorization": "Bearer nsn_your_key" }
}
}
}Any client that supports remote MCP servers over streamable HTTP with a custom header can connect the same way.
The tools your assistant gets
| Tool | What it does |
|---|---|
search_nsn | Search NSNs by item name, NSN or exact part number |
find_nsn_by_part_number | Find the NSNs that list a manufacturer part number, optionally for one CAGE |
lookup_nsn | Full record for one NSN, with optional sections such as prices and characteristics |
lookup_cage | Company name, address and status for a CAGE code |
search_cage | Find CAGE codes by company name |
lookup_fsc | Title and scope of a Federal Supply Class |
lookup_inc | Approved item name and definition for an Item Name Code |
Safe to hand to an agent
Every tool only reads. There is nothing an assistant can change, order or delete.
You stay in control of volume
Each tool call counts as one request against your plan. An agent that loops stops at your limit, not at your budget.
Tools do not change under you
A published tool keeps its name, inputs and output. New behaviour arrives as a new tool beside the old one.
Building your own agent?
Use the MCP server, or call the REST API directly from your tool code. Both return the same JSON.
Try it with a free key
The Free plan includes every MCP tool. Connect your assistant and ask it about a part on your desk.
Get a free API key Ask a question