mcpField
S
specwise-mcp

specwise-mcp

Local
specwise.hybridforgelab.comDeveloper Tools0Updated 5d ago

About specwise-mcp

specwise-mcp is a legacy package for OpenAPI and JSON Schema validation and OpenAPI breaking-change diffs. It now installs and forwards to bytestay-specwise-mcp and receives no further updates.

Key features

  1. 01Forwards to bytestay-specwise-mcp
  2. 02No further updates

Use cases

  1. 01Replace the package in an MCP client config
  2. 02Continue using existing environment variables

MCP support

The package is an MCP server entry point that forwards to bytestay-specwise-mcp. Its tools validate OpenAPI and JSON Schema and report OpenAPI breaking-change diffs, as described in the tagline.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"hybridforgelab-specwise": {
"command": "uvx",
"args": [
"hybridforgelab-specwise-mcp"
],
"env": {
"RAPIDAPI_KEY": "<RAPIDAPI_KEY>",
"API_MARKET_KEY": "<API_MARKET_KEY>",
"HFL_MARKETPLACE": "<HFL_MARKETPLACE>"
}
}
}
}
Run commanduvx hybridforgelab-specwise-mcp
Environment variables to set
RAPIDAPI_KEYSecretYour RapidAPI key
API_MARKET_KEYSecretYour api.market key, used when RAPIDAPI_KEY is not set
HFL_MARKETPLACErapidapi or apimarket, when both keys are set

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypihybridforgelab-specwise-mcp0.2.3

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

hybridforgelab-specwise-mcp: moved to bytestay-specwise-mcp

This package has moved to bytestay-specwise-mcp. Hybrid Forge Lab is now ByteStay.

This last version only installs bytestay-specwise-mcp and forwards to it. It prints a one-line notice on stderr and gets no more updates.

Switch

Replace hybridforgelab-specwise-mcp with bytestay-specwise-mcp in your MCP client config:

"command": "uvx",
"args": ["--from", "bytestay-specwise-mcp", "specwise-mcp"]

Or with Claude Code:

claude mcp add specwise --env RAPIDAPI_KEY=your-rapidapi-key -- uvx --from bytestay-specwise-mcp specwise-mcp

The environment variables are the same, so your keys keep working.

Links

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.