stack-overflow-mcp-light
# Stack Overflow MCP Server
A Model Context Protocol (MCP) server that provides comprehensive tools for interacting with Stack Overflow through the Stack Exchange API. This server enables AI assistants to search questions, get detailed answers, and explore Stack Overflow content through a standardized interface.
[](https://opensource.org/licenses/MIT)
[](https://www.python.org/downloads/)
[](https://github.com/jlowin/fastmcp)
## ๐ Features
- **Question Search** - Advanced search with multiple filters and sorting options
- **Question Details** - Get comprehensive information including answers with body content
- **Tag-based Search** - Find questions by specific tags
- **Top Answers** - Retrieve highly-voted answers from the community
- **Type Safety** - Full Pydantic validation with structured response models
- **Error Handling** - Comprehensive error reporting and graceful failure modes
## ๐ฆ Installation
### Using uvx (Recommended)
```bash
uvx stack-overflow-mcp-light
```
### Using uv
```bash
uv add stack-overflow-mcp-light
uv run stack-overflow-mcp-light
```
### Using pip
```bash
pip install stack-overflow-mcp-light
stack-overflow-mcp-light
```
## โ๏ธ Configuration
### Environment Variables
- **`STACK_EXCHANGE_API_KEY`** (Optional): Stack Exchange API key for increased rate limits. Get one at [Stack Apps](https://stackapps.com/apps/oauth/register)
- **`STACK_OVERFLOW_MCP_SHOW_LOGS`** (Optional): Set to `"true"` to enable detailed logging
> ๐ก **API Key**: While optional, an API key significantly increases your rate limits from 300 to 10,000 requests per day.
### Transport Types
1. **`stdio`** (default) - Standard input/output, client launches server automatically
2. **`http`** (recommended for remote) - Modern HTTP transport (aliases: `streamable-http`, `streamable_http`)
3. **`sse`** (legacy) - Server-Sent Events transport (deprecated)
---
## ๐ Quick Start (uvx)
### Stdio Transport
```json
{
"mcpServers": {
"stack-overflow": {
"command": "uvx",
"args": ["--no-progress", "stack-overflow-mcp-light"],
"env": {
"STACK_EXCHANGE_API_KEY": "your_api_key_here",
"STACK_OVERFLOW_MCP_SHOW_LOGS": "false"
}
}
}
}
```
### HTTP Transport
**Start server:**
```bash
export STACK_EXCHANGE_API_KEY="your_api_key_here"
uvx --no-progress stack-overflow-mcp-light --transport http --port 8000 --host 0.0.0.0
```
**Client config:**
```json
{
"mcpServers": {
"stack-overflow": {
"url": "http://localhost:8000/mcp",
"transport": "http"
}
}
}
```
### SSE Transport
**Start server:**
```bash
export STACK_EXCHANGE_API_KEY="your_api_key_here"
uvx --no-progress stack-overflow-mcp-light --transport sse --port 8000 --host 0.0.0.0
```
**Client config:**
```json
{
"mcpServers": {
"stack-overflow": {
"url": "http://localhost:8000/sse",
"transport": "sse"
}
}
}
```
---
## ๐ง Alternative Commands
### Stdio with `uv run --with`
```json
{
"mcpServers": {
"stack-overflow": {
"command": "uv",
"args": ["run", "--with", "stack-overflow-mcp-light", "stack-overflow-mcp-light"],
"env": {
"STACK_EXCHANGE_API_KEY": "your_api_key_here",
"STACK_OVERFLOW_MCP_SHOW_LOGS": "false"
}
}
}
}
```
### Stdio with `uv run --directory` (Local Development)
```json
{
"mcpServers": {
"stack-overflow": {
"command": "uv",
"args": ["run", "--directory", "/path/to/stack-overflow-mcp-light", "stack-overflow-mcp-light"],
"env": {
"STACK_EXCHANGE_API_KEY": "your_api_key_here",
"STACK_OVERFLOW_MCP_SHOW_LOGS": "true"
}
}
}
}
```
### Stdio with `pip` Install
```json
{
"mcpServers": {
"stack-overflow": {
"command": "stack-overflow-mcp-light",
"args": [],
"env": {
"STACK_EXCHANGE_API_KEY": "your_api_key_here",
"STACK_OVERFLOW_MCP_SHOW_LOGS": "false"
}
}
}
}
```
### HTTP/SSE Alternative Commands
All transport types can use these alternative commands:
```bash
# Using uv run --with
export STACK_EXCHANGE_API_KEY="your_api_key_here"
uv run --with stack-overflow-mcp-light stack-overflow-mcp-light --transport http --port 8000
# Using uv run --directory (local development)
export STACK_EXCHANGE_API_KEY="your_api_key_here"
cd /path/to/stack-overflow-mcp-light
uv run stack-overflow-mcp-light --transport http --port 8000
# Using pip install
export STACK_EXCHANGE_API_KEY="your_api_key_here"
stack-overflow-mcp-light --transport http --port 8000
```
## ๐ ๏ธ Available Tools
### โ Question Tools (3 tools)
#### `search_questions`
Search Stack Overflow questions with advanced filters.
- **Input**: Search parameters including:
- `q` - Free-form text search
- `tagged` - Semi-colon delimited list of tags
- `intitle` - Search in question titles
- `nottagged` - Exclude these tags
- `body` - Text in question body
- `accepted` - Has accepted answer (boolean)
- `closed` - Question is closed (boolean)
- `answers` - Minimum number of answers
- `views` - Minimum view count
- `sort` - Sort criteria ("activity", "votes", "creation", "hot", "week", "month", "relevance")
- `order` - Sort order ("asc" or "desc")
- `page` - Page number (1-25)
- `page_size` - Items per page (1-100)
- **Output**: Array of question items with essential fields:
- `question_id` - Question ID
- `is_answered` - Whether the question has answers
- `score` - Question score
- `link` - Link to the question
- `title` - Question title
#### `fetch_question_answers`
Fetch a specific question, always including answers with body content sorted by the specified criteria.
- **Input**: Question details request including:
- `question_id` - Question ID (required)
- `sort` - Answer sort criteria ("activity", "votes", "creation") - defaults to "votes"
- `order` - Sort order ("asc" or "desc") - defaults to "desc"
- `page_size` - Maximum number of answers to return (1-100) - defaults to 30
- **Output**: QuestionItem with detailed information including:
- `question_id` - Question ID
- `is_answered` - Whether the question has answers
- `score` - Question score
- `link` - Link to the question
- `title` - Question title
- `answers` - Array of AnswerItem objects with:
- `answer_id` - Answer ID
- `is_accepted` - Whether the answer is accepted
- `score` - Answer score
- `body` - Answer body content
#### `search_questions_by_tag`
Search questions that have a specific tag.
- **Input**: `tag` (tag name), `sort`, `order`, `page`, `page_size`
- **Output**: Array of question items with essential fields:
- `question_id` - Question ID
- `is_answered` - Whether the question has answers
- `score` - Question score
- `link` - Link to the question
- `title` - Question title
## ๐งช Testing
The project includes comprehensive tests covering all tools:
```bash
# Run all tests
make test
# Run with coverage
make test-cov
# Run specific test categories
uv run pytest tests/test_server.py::TestQuestionTools -v
```
## ๐ง Development
### Setup Development Environment
```bash
# Clone the repository
git clone https://github.com/midodimori/stack-overflow-mcp-light.git
cd stack-overflow-mcp-light
# Install with development dependencies
make install-dev
# Run tests
make test
# Format and lint code
make format
# Check code style and types
make lint
# Run the server locally
make run
# See all available commands
make help
```
### Project Structure
```
stack-overflow-mcp-light/
โโโ src/stack_overflow_mcp_light/
โ โโโ __init__.py
โ โโโ server.py # MCP server implementation
โ โโโ logging_config.py # Logging configuration
โ โโโ models/ # Pydantic models
โ โ โโโ __init__.py
โ โ โโโ requests.py # Request models
โ โ โโโ responses.py # Response models
โ โโโ tools/ # Tool implementations
โ โโโ __init__.py
โ โโโ base_client.py # Base client for Stack Exchange API
โ โโโ questions.py # Question search and retrieval tools
โโโ tests/
โ โโโ test_server.py # Tool function tests
โ โโโ test_mcp_integration.py # MCP integration tests
โโโ pyproject.toml # Project configuration
โโโ README.md
```
## ๐ API Reference
### Question Sort Options
- **activity**: Sort by last activity date (default)
- **votes**: Sort by question score
- **creation**: Sort by creation date
- **hot**: Sort by current hotness
- **week**: Sort by weekly activity
- **month**: Sort by monthly activity
- **relevance**: Sort by search relevance
### Answer Sort Options
- **activity**: Sort by last activity date (default)
- **votes**: Sort by answer score
- **creation**: Sort by creation date
### Sort Order
- **desc**: Descending order (default)
- **asc**: Ascending order
## ๐ค Contributing
1. Fork the repository
2. Create a feature branch (`git checkout -b feature/amazing-feature`)
3. Commit your changes (`git commit -m 'Add amazing feature'`)
4. Push to the branch (`git push origin feature/amazing-feature`)
5. Open a Pull Request
## ๐ License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
## โ ๏ธ Disclaimer
This software is provided for educational and informational purposes only. This tool interacts with Stack Overflow's public API and respects their rate limits and terms of service. The authors are not responsible for any misuse of the Stack Exchange API or violation of their terms of service.
## ๐ Links
- [Stack Overflow](https://stackoverflow.com/)
- [Stack Exchange API Documentation](https://api.stackexchange.com/docs)
- [Stack Apps - API Key Registration](https://stackapps.com/apps/oauth/register)
- [Model Context Protocol](https://modelcontextprotocol.io/)
- [FastMCP Framework](https://github.com/jlowin/fastmcp)
- [Claude Desktop](https://claude.ai/desktop)
## ๐ Support
For questions, issues, or contributions:
- Open an issue on GitHub
- Check the [Stack Overflow Meta](https://meta.stackoverflow.com/) for API-related questions
- Review the comprehensive test suite for usage examplesTDQS
Scored across 3 tools
search_questions and search_questions_by_tag overlap because search_questions accepts advanced filters that likely include tag filtering, making the distinction unclear. fetch_question_answers is clearly distinct, retrieving a specific question with answers, but the two search tools create ambiguity.
All tool names follow a consistent verb_noun pattern: search_questions, search_questions_by_tag, and fetch_question_answers. The 'by_tag' modifier is a clear exception for the second search tool but still follows the same convention, making the naming predictable and uniform.
With 3 tools, the set is on the lean side but appropriate for a 'light' Stack Overflow read-only server. Each tool serves a core purpose without redundancy, and the count is reasonable for the intended narrow scope.
The server covers essential read operations: searching questions generically and by tag, and fetching a question with answers. Missing operations like user lookups or comment retrieval are not critical for a lightweight server, but the surface is slightly thin for full Stack Overflow coverage.