
Lockspec
io.github.LockSpecPublished by GitHub account LockSpecv1.0.1Updated Oct 24, 2026
MCP server giving AI coding agents version-pinned API context from your OpenAPI specs.
Overview
Gives coding agents version-pinned API contract details from your OpenAPI specs, so generated calls match the real endpoints and types.
- What you can do
- Loads an OpenAPI 3.0 or 3.1 spec from a file, URL, or text, normalizes and indexes it, and pins it as a versioned snapshot. Tools let an agent find operations by intent or path, look up named schemas, read exact request and response signatures, and structurally validate a draft request against the pinned spec. It can also list loaded specs, switch the active version, remove a spec or version, and diff two versions as breaking or non-breaking.
- When to use it
- Useful when an agent writes code against an API whose spec is private, internal, third-party, too large for context, or not in the repository. Also helpful when several API versions are live at once and you want the agent pinned to a chosen version rather than the latest one it saw.
- Requirements
- Local process run through npx (npm package lockspec) or from a built source checkout; requires Node 22 or newer. No accounts, API keys, or environment variables are declared. Specs are fetched once and then served offline from ~/.lockspec/.
Installation
In SourceWeft
- Open Lockspec in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.