MCP server for Gunsnation firearms database API
MCP server for Gunsnation firearms database API. That is what the gunsnation mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The Gunsnation MCP Server is a lightweight integration layer that exposes the Gunsnation firearms catalog to AI assistants through the Model Context Protocol (MCP). It allows compatible AI clients to search, filter, and retrieve detailed firearm information using structured tool calls instead of manual API integration.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The server publishes 2 tools. What each one is for:
search_firearms — The search_firearms tool exposed by this serverget_firearm — The get_firearm tool exposed by this serverConfiguration is passed through the environment: GUNSNATION_API_KEY, GUNSNATION_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Gunsnation's toolset — search_firearms, get_firearm — is a fair guide to whether it matches your workflow. It is maintained by dynamicdeals; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| search_firearms | The search_firearms tool exposed by this server. |
| get_firearm | The get_firearm tool exposed by this server. |
{
"mcpServers": {
"gunsnation": {
"command": "npx",
"args": ["gunsnation-mcp"],
"env": {
"GUNSNATION_API_KEY": "your_api_key_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GUNSNATION_API_KEY | Credential the server authenticates with. | Yes |
| GUNSNATION_API_URL | Endpoint or connection string the server talks to. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.