Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://api.wiscolabs.dev/mcp/devThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http dev.wiscolabs-developer-tools https://api.wiscolabs.dev/mcp/devRun in a terminal.
{ "mcpServers": { "dev.wiscolabs-developer-tools": { "command": "npx", "args": [ "-y", "mcp-remote", "https://api.wiscolabs.dev/mcp/dev" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchTools
No tool list yet. Remote servers get one after the first health check.
FAQ
Check PyPI and npm upgrades: known vulnerabilities, the safe version, and what each upgrade breaks.
{ "mcpServers": { "dev.wiscolabs-developer-tools": { "url": "https://api.wiscolabs.dev/mcp/dev", "headers": {} } }}Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Wisco Labs: Developer Tools is reached over HTTP.
Last checked 2026-11-08. Check PyPI and npm upgrades: known vulnerabilities, the safe version, and what each upgrade breaks.
From the publisher
README is not crawled yet. No repository on file.
Check PyPI and npm upgrades: known vulnerabilities, the safe version, and what each upgrade breaks.
© 2026 MCP Directory.