Install

Install the MCP server

No download is required. Sign in from your client, or configure it with the server URL and an API key.

Let your assistant set it up

Paste this prompt into Claude Code, Cursor or any assistant that can read a URL and run commands. The assistant follows the install guide, asks for your key and installs the skill.

1Read https://docs.gunspec.io/mcp/install.md2and set up the GunSpec MCP server for me.3Ask me for my API key.

File	What it is
`install.md`	The install guide the assistant follows.
`SKILL.md`	An Agent Skill that tells an assistant which tool to use and how to interpret the results.
`tools.md`	Every tool with its arguments.
`tools.json`	Every tool with its plan, API operation and example arguments, in JSON format.

1. Choose how to connect

Both reach the same tools on the same plan. Sign in when your client supports it; use a key for scripts and for clients that cannot open a browser.

1https://mcp.gunspec.io/mcp-oauth

Your client opens a browser, you approve it in your account, and it is connected. There is no key to create, copy or rotate, and you can disconnect it from your account at any time. How signing in works.

2. Add the server to your client

Select your client. Each adds the server by its URL alone, and asks you to sign in the first time it connects.

Claude Code

1claude mcp add --transport http gunspec https://mcp.gunspec.io/mcp-oauth2claude mcp login gunspec

claude mcp login opens the browser; inside a session, /mcp does the same. Add --scope user to the first command to make the server available in every project.

Install from the MCP Registry

The server is listed in the official MCP Registry as io.gunspec/mcp. Clients that browse the registry can add it from there: the listing gives the server URL, the transport, and a required X-API-Key header marked secret, so the client asks for your API key rather than storing it in the listing. Only the owner of the gunspec.io domain can publish under this name, so an entry with this name is the official server.

1curl -s "https://registry.modelcontextprotocol.io/v0/servers/io.gunspec%2Fmcp/versions"

The listing is discovery only. It grants no access: every call still needs a valid API key, and your plan, rate limit and MCP allowance still apply. Each release of the server is listed after it is deployed.

Reading the listing from the registry…

For MCP directories and catalogs

Listing this server is welcome. Every request needs a key, including tools/list, so a health check or tool discovery run without one is answered 401 and the listing will report the server as unavailable.

We issue keys for that, restricted to this server. Listing this server explains what such a key can do and shows the nightly checks that prove it.

Read the guide for directories

3. Verify the connection

Ask your assistant a question that only the catalog can answer. For example:

1Use GunSpec to find the Glock 19 and tell me its barrel length and weight.

The assistant should call gunspec_identify_firearm, which resolves the name and reads the record in a single call. Looking a firearm up by name needs the Builder plan. On Explorer, ask instead: "Use GunSpec to list pistols made by Glock", which calls gunspec_list_firearms. If the assistant reports that a tool requires a higher plan, the connection is working but your plan does not include that tool. See Usage and limits.