Openapi MCP vs MCP Openapi
A side-by-side look at the Openapi MCP and MCP Openapi MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Openapi MCP for developer tools work as a local process; choose MCP Openapi for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Openapi MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
API_TOKEN, OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET, OAUTH_REFRESH_TOKEN, OAUTH_TOKEN_URL, OAUTH_SCOPE, API_HEADERS, TOOL_FILTER.
Choose MCP Openapi when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
OPENAPI_BEARER_TOKEN, OPENAPI_API_KEY, OPENAPI_API_KEY_HEADER, OPENAPI_BASIC_USER, OPENAPI_BASIC_PASS. - You want tools like
list_endpoints, call_endpoint.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 36/100 · Fair | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | API_TOKENOAUTH_CLIENT_ID |
Tools & capabilities
Openapi MCP tools
No tool names declared yet. Check the project README from the listing page.
MCP Openapi tools 2
list_endpointsReturns all operations grouped by tag with operationIds, methods, paths, and parameterscall_endpointExecutes any operation by `operationId` with path/query/header/body parameters
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Openapi MCP
{
"mcpServers": {
"openapi-mcp-2": {
"command": "npx",
"args": [
"-y",
"@asthanaji/openapi-mcp"
],
"env": {
"API_TOKEN": "YOUR_API_TOKEN_HERE",
"OAUTH_CLIENT_ID": "YOUR_OAUTH_CLIENT_ID_HERE",
"OAUTH_CLIENT_SECRET": "YOUR_OAUTH_CLIENT_SECRET_HERE",
"OAUTH_REFRESH_TOKEN": "YOUR_OAUTH_REFRESH_TOKEN_HERE",
"OAUTH_TOKEN_URL": "YOUR_OAUTH_TOKEN_URL_HERE",
"OAUTH_SCOPE": "YOUR_OAUTH_SCOPE_HERE",
"API_HEADERS": "YOUR_API_HEADERS_HERE",
"TOOL_FILTER": "YOUR_TOOL_FILTER_HERE"
}
}
}
}
MCP Openapi
{
"mcpServers": {
"saurav61091-mcp-openapi": {
"command": "npx",
"args": [
"-y",
"mcp-openapi-runner"
],
"env": {
"OPENAPI_BEARER_TOKEN": "YOUR_OPENAPI_BEARER_TOKEN_HERE",
"OPENAPI_API_KEY": "YOUR_OPENAPI_API_KEY_HERE",
"OPENAPI_API_KEY_HEADER": "YOUR_OPENAPI_API_KEY_HEADER_HERE",
"OPENAPI_BASIC_USER": "YOUR_OPENAPI_BASIC_USER_HERE",
"OPENAPI_BASIC_PASS": "YOUR_OPENAPI_BASIC_PASS_HERE"
}
}
}
}
Frequently asked questions
Openapi MCP is categorized under Developer Tools and uses a local stdio subprocess. MCP Openapi belongs to Developer Tools and uses a local stdio subprocess. Pick Openapi MCP for developer tools work and MCP Openapi for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Openapi MCP has no declared pricing — check the project's own site. MCP Openapi is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add openapi-mcp-2 and saurav61091-mcp-openapi as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Openapi MCP has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MCP Openapi has 39/100 (Fair) with 4 views, 0 installs and 1 GitHub stars.