stackoverflow-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RETRY_AFTER_MS | No | Delay after hitting rate limit | 2000 |
| RATE_LIMIT_WINDOW_MS | No | Rate limit window in milliseconds | 60000 |
| MAX_REQUEST_PER_WINDOW | No | Maximum requests per rate limit window | 30 |
| STACK_EXCHANGE_API_KEY | Yes | Stack Exchange API key required for higher request quota |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| advanced_searchA | Advanced search for Stack Overflow questions with many filter options. |
| search_by_queryB | Search Stack Overflow for questions matching a query. |
| search_by_errorA | Search Stack Overflow for solutions to an error message |
| get_questionA | Get a specific Stack Overflow question by ID. |
| analyze_stack_traceA | Analyze a stack trace and find relevant solutions on Stack Overflow. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Tools have distinct purposes: advanced_search for comprehensive filtering, search_by_query for simpler queries, search_by_error for errors, analyze_stack_trace for stack traces, and get_question for specific retrieval. There is some overlap between advanced_search and search_by_query, but descriptions clearly differentiate them.
All tool names follow a consistent snake_case verb_noun pattern (e.g., advanced_search, get_question, search_by_error). No mixing of conventions, making it easy to predict naming for hypothetical additional tools.
5 tools is slightly below average but appropriate for a focused search-only server. Each tool covers a key use case (general search, error search, stack trace analysis, specific question retrieval). Could benefit from one more tool (e.g., for answers) but current count is reasonable.
Covers main search scenarios well, including advanced filtering, error messages, and stack traces. However, lacks tools for retrieving answers separately or exploring tags/users. The presence of two very similar search tools (advanced_search vs search_by_query) suggests slight redundancy rather than full coverage.