StackResolve

What StackResolve MCP server does

StackResolve MCP server gives AI agents access to two related data areas. AgentReady covers software and MCP server discovery, evaluation, selection, installation, and use. CompanyData turns web research into structured information about companies, pricing, competitors, and research questions.

The hosted service is available at https://mcp.stackresolve.dev/mcp. It exposes tools for finding software by task, searching the registry, comparing products, retrieving profiles, listing registry entries, auditing domains, generating agent interfaces, and researching companies. The registry contains scored records rather than only undifferentiated search results, which helps an agent choose between candidate tools.

How it works

Agents connect to the hosted MCP endpoint over HTTP. The handshake and registry-reading operations—search_tools, get_profile, compare_products, and list_registry—can be used without an API key. Metered operations require a free key from StackResolve and receive it through the x-api-key request header.

The full tool set includes resolve, how_to, find_tools_for_task, search_tools, compare_products, get_profile, list_registry, audit, generate_agent_interfaces, get_company, get_pricing, research_company, find_competitors, compare_companies, and get_usage. The API can also be consumed directly at https://api.stackresolve.dev; its OpenAPI description is available at /openapi.json.

Setup and configuration

The hosted MCP server does not require a local package installation. Claude Code can register it with the HTTP transport using claude mcp add --transport http stackresolve https://mcp.stackresolve.dev/mcp. Cursor and Codex configurations can point to the same URL and include x-api-key when gated tools are needed.

For local programmatic use, install the TypeScript package with npm install stackresolve; Node 18 or newer is required. The CLI is installed with npm i -g stackresolve, and a setup command can register the hosted server for supported coding agents, write a StackResolve skill file, and verify the API key. Python and LangChain packages are also provided separately.

The TypeScript client reads STACKRESOLVE_API_KEY when no key is passed directly. STACKRESOLVE_BASE_URL can replace the default API host. The client sends the key on each request and raises StackResolveError for non-2xx responses, including the HTTP status and parsed response body.

Tools and capabilities

Use the MCP tools to:

• Find tools for a natural-language task and receive ranked results.
• Search, inspect, compare, and enumerate registry entries.
• Audit a domain for AgentReady scores, facts, and issues.
• Generate agent interfaces from a domain and optional OpenAPI URL.
• Retrieve company descriptions, pricing, competitors, and research results.
• Compare multiple companies and inspect usage information.

The SDK exposes corresponding methods for discovery, score history, categories, monitors, account profiles, and discovery runs. Some account and monitoring methods require an API key.

Limitations and notes

Anonymous access is subject to a rate limit. Registry reads are unauthenticated, but the README identifies resolution, instructional guidance, audits, company research, company retrieval, and pricing as metered MCP operations that need a key. Monitoring, usage, and discovery runs also require authentication through the SDK.

The material documents hosted HTTP configuration for Claude Code, Cursor, Codex, Windsurf, and VS Code, but does not describe a local MCP implementation. The service therefore depends on network access to StackResolve’s hosted endpoint. The SDK, CLI, Python package, LangChain package, and REST API are alternative interfaces rather than separate MCP servers.