stackexchange-mcp-server
Server Details
Search Stack Exchange questions, fetch Q&A threads as markdown, look up tag FAQs and user profiles.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.4/5 across 5 of 5 tools scored.
Each tool targets a distinct functionality: tag FAQ, thread retrieval, user profile, site listing, and search. No two tools overlap in purpose, and cross-references are clearly documented.
All tools follow a consistent 'stackexchange_verb_noun' pattern with snake_case. Verbs are descriptive and nouns reflect the resource (e.g., get_thread, list_sites).
With 5 tools, the server is tightly scoped to core Stack Exchange read operations. Each tool serves a necessary role without unnecessary duplication.
The set covers all major read actions: site discovery, search, tag-based FAQ, full thread retrieval, and user info. Missing operations like user question lists or comment retrieval are minor gaps for typical agent tasks.
Available Tools
5 toolsstackexchange_get_tag_faqGet Stack Exchange Tag FAQARead-onlyIdempotentInspect
Fetch the highest-voted answered questions for a tag on a Stack Exchange site — the canonical "best answers in X" list. Returns a question list without bodies; use stackexchange_get_thread to read the full body and answers for any result. Use this tool to find the authoritative community resources on a topic (e.g. tag "javascript" on stackoverflow). Use stackexchange_search_questions for free-text search rather than tag-based browsing.
| Name | Required | Description | Default |
|---|---|---|---|
| tag | Yes | Tag to look up (e.g. "python", "javascript", "docker"). Must match exactly. | |
| site | No | Stack Exchange site — use the api_site_parameter value (e.g. "stackoverflow", "superuser"). Defaults to "stackoverflow". Call stackexchange_list_sites to discover valid values. | stackoverflow |
| pageSize | No | Number of results to return (1–30, default 10). |
Output Schema
| Name | Required | Description |
|---|---|---|
| cap | No | The pageSize cap applied to this request. |
| tag | Yes | Tag name used for this FAQ lookup. |
| site | Yes | Stack Exchange site api_site_parameter used for this lookup. |
| shown | No | Number of results returned. |
| notice | No | Actionable guidance when results are empty or filtered. |
| quotaMax | Yes | Maximum API quota calls per day (300 keyless, ~10,000 with API key). |
| questions | Yes | Highest-voted answered questions for the specified tag, ordered by votes. |
| truncated | No | True when results were capped at pageSize. |
| attribution | Yes | Content license notice. Stack Exchange content is licensed under CC BY-SA 4.0 and requires attribution. |
| quotaRemaining | Yes | Remaining API quota calls for the current day. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint and idempotentHint. Description adds that the result is a question list without bodies and directs to another tool for full content. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, front-loaded with purpose, no extraneous information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Has output schema, so return format not needed. Description explains that bodies are excluded, covers parameters via schema, and points to other tools. Adequate for the complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. Description adds minimal extra value beyond schema definitions (e.g., suggests stackexchange_list_sites for 'site' parameter).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Fetch' and resource 'highest-voted answered questions for a tag', and distinguishes from sibling tools like stackexchange_search_questions for free-text search.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states when to use (find authoritative community resources) and when not to (use stackexchange_search_questions for free-text), and suggests stackexchange_get_thread for reading full bodies/answers.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
stackexchange_get_threadGet Stack Exchange Q&A ThreadARead-onlyIdempotentInspect
Fetch a complete Q&A thread — question body and all answers, accepted answer first then sorted by score, rendered as clean markdown with fenced code blocks. Accepts an integer question ID or a full Stack Exchange question URL (e.g. "https://stackoverflow.com/questions/11227809/why-is-processing-a-sorted-array-faster" or "11227809"). HTML is normalized to markdown automatically; attribution (author + link) included per CC BY-SA 4.0. Get question IDs from stackexchange_search_questions or stackexchange_get_tag_faq.
| Name | Required | Description | Default |
|---|---|---|---|
| site | No | Stack Exchange site — use the api_site_parameter value (e.g. "stackoverflow", "superuser"). Defaults to "stackoverflow". Must match the site where the question lives. Call stackexchange_list_sites to discover valid values. | stackoverflow |
| maxAnswers | No | Maximum number of answers to include (1–100, default 10). Answers are sorted: accepted first, then by score. | |
| questionIdOrUrl | Yes | Numeric question ID (e.g. "11227809") or a full Stack Exchange question URL (e.g. "https://stackoverflow.com/questions/11227809/why-is-processing-a-sorted-array-faster"). The integer immediately following /questions/ is extracted from URLs. |
Output Schema
| Name | Required | Description |
|---|---|---|
| cap | No | The maxAnswers cap applied to this request. |
| link | Yes | Direct URL to the question. |
| tags | Yes | Tags applied to this question. |
| score | Yes | Question score (upvotes minus downvotes). |
| shown | No | Number of answers returned. |
| title | Yes | Question title. |
| answers | Yes | Answers sorted: accepted answer first, then by score descending. |
| quotaMax | Yes | Maximum API quota calls per day (300 keyless, ~10,000 with API key). |
| truncated | No | True when answers were capped at maxAnswers. |
| authorLink | No | Question author profile URL when available. |
| authorName | No | Question author display name when available. |
| questionId | Yes | Numeric question ID — identifies this thread on the site. |
| authorUserId | No | Question author numeric user ID when available — pass to stackexchange_get_user to fetch the full profile. |
| bodyMarkdown | Yes | Question body normalized from HTML to markdown. |
| quotaRemaining | Yes | Remaining API quota calls for the current day. |
| acceptedAnswerId | No | ID of the accepted answer when one exists. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint, openWorldHint, and idempotentHint are true. The description goes beyond annotations by detailing that output is in clean markdown with fenced code blocks, HTML is normalized, and attribution is included. This provides rich behavioral context without contradicting annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences, front-loading the main action, then detailing format and input, followed by attribution and sourcing hints. Every sentence adds distinct value, and there is no redundancy. It is appropriately sized for the tool's complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of an output schema (not shown but indicated), the description does not need to explain return values. It covers input formats, output formatting, and attribution. It does not mention error handling or missing question behavior, but for a read-only, idempotent tool, this is acceptable. A score of 5 would require a note on error responses.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema covers all three parameters with descriptions. The description adds value by explaining that questionIdOrUrl accepts both integer and URL, with an example, and clarifies the site parameter's default and discovery via list_sites. For maxAnswers, it mentions sorting. This complements the schema well, though schema coverage is already 100%.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool fetches a complete Q&A thread, including question and answers, and mentions input formats. However, it does not explicitly differentiate from sibling tools like stackexchange_search_questions beyond saying to get question IDs from them, which is a usage hint rather than a differentiation. A score of 5 would require stating when to use this tool versus its siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains that the tool accepts either a question ID or a URL and suggests obtaining IDs from related tools. This provides clear context for when to use this tool (after having a question ID). It does not explicitly state when not to use it, but the alternatives are implied. A score of 5 would require explicit exclusion scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
stackexchange_get_userGet Stack Exchange User ProfileARead-onlyIdempotentInspect
Fetch a Stack Exchange user profile by numeric user ID: reputation, badge counts, top tags by answer score, and account metadata. Useful for credibility context on an answer author — pass the authorUserId from any question or answer in stackexchange_get_thread output. Returns profile fields plus up to 10 top tags by answer score.
| Name | Required | Description | Default |
|---|---|---|---|
| site | No | Stack Exchange site — use the api_site_parameter value (e.g. "stackoverflow", "superuser"). Defaults to "stackoverflow". Call stackexchange_list_sites to discover valid values. | stackoverflow |
| userId | Yes | Numeric user ID — use the authorUserId field from a question or answer in stackexchange_get_thread output. |
Output Schema
| Name | Required | Description |
|---|---|---|
| link | Yes | Direct URL to the user profile. |
| userId | Yes | Numeric user ID on this Stack Exchange site. |
| topTags | Yes | Top tags by answer score (up to 10). Empty array for new users with no answers. |
| location | No | User-provided location string when available. |
| quotaMax | Yes | Maximum API quota calls per day (300 keyless, ~10,000 with API key). |
| reputation | Yes | User reputation score. |
| websiteUrl | No | User-provided website URL when available. |
| answerCount | No | Total number of answers posted when provided by the API. |
| badgeCounts | No | Badge counts when provided by the API. |
| displayName | Yes | Display name shown on the site. |
| questionCount | No | Total number of questions posted when provided by the API. |
| quotaRemaining | Yes | Remaining API quota calls for the current day. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the description does not need to restate safety. The description adds value by detailing that it returns reputation, badge counts, top tags by answer score, account metadata, and up to 10 top tags, which complements the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences with no superfluous words. It front-loads the main action and return fields, then adds usage context and additional detail. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the low complexity (2 parameters, 1 required), 100% schema coverage, and presence of an output schema, the description fully covers purpose, input source, and return contents. It answers the key questions an AI agent would have to invoke this tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for both parameters. The description adds practical context by mentioning 'pass the authorUserId from...' and 'numeric user ID', which is consistent with the schema but reinforces usage. This slightly exceeds the baseline of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Fetch a Stack Exchange user profile by numeric user ID' and lists specific return fields (reputation, badge counts, top tags, account metadata). It distinguishes from sibling tools like stackexchange_get_thread and stackexchange_search_questions by focusing on user profile rather than threads, tags, or search.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says 'useful for credibility context on an answer author' and instructs to use 'the authorUserId from any question or answer in stackexchange_get_thread output'. This provides clear when-to-use guidance. However, it does not mention when not to use or list explicit alternatives, so it falls short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
stackexchange_list_sitesList Stack Exchange SitesARead-onlyIdempotentInspect
Enumerate all sites in the Stack Exchange network — name, api_site_parameter, audience, and URL. The api_site_parameter value is what other tools accept as the site input (e.g. "stackoverflow", "superuser", "serverfault"). Results are fetched live and optionally filtered by name. Use this tool to discover valid site parameters before calling other stackexchange_* tools.
| Name | Required | Description | Default |
|---|---|---|---|
| filter | No | Optional case-insensitive name filter — returns only sites whose name contains all provided tokens. Omit to return all sites. |
Output Schema
| Name | Required | Description |
|---|---|---|
| sites | Yes | Stack Exchange network sites matching the optional name filter. |
| notice | No | Actionable guidance when results are empty or filtered. |
| quotaMax | Yes | Maximum API quota calls per day (300 keyless, ~10,000 with API key). |
| totalCount | Yes | Total number of sites returned after filtering. |
| quotaRemaining | Yes | Remaining API quota calls for the current day. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is clear. The description adds that results are 'fetched live' and optionally filtered, but this is minimal additional behavioral context. With output schema present, no need to detail return values.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences, each purposeful: first enumerates fields, second explains api_site_parameter, third gives usage context. No redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description fully covers the tool's simple behavior (list sites, optional filter), complements annotations and output schema, and guides the agent on when to call it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%. The description adds semantic value by explaining that filter is 'case-insensitive' and that omitting it returns all sites, which goes beyond the schema's basic description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses specific verb 'enumerate' and resource 'sites in the Stack Exchange network', listing exact fields returned. It clearly distinguishes from sibling tools (which deal with tags, threads, users, or questions) by focusing on site enumeration.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly advises using this tool before other stackexchange_* tools to discover valid site parameters. While it doesn't list negative cases, the context and sibling names imply when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
stackexchange_search_questionsSearch Stack Exchange QuestionsARead-onlyIdempotentInspect
Search questions across a Stack Exchange site. Returns ranked questions with title, score, answer count, accepted status, tags, and excerpt — no bodies at this stage. Results supply question_id values for stackexchange_get_thread, which fetches the full question body and all answers. Use the site parameter to target a specific community (e.g. "stackoverflow", "superuser", "unix"); call stackexchange_list_sites to discover valid site values.
| Name | Required | Description | Default |
|---|---|---|---|
| site | No | Stack Exchange site to search — use the api_site_parameter value (e.g. "stackoverflow", "superuser", "serverfault"). Defaults to "stackoverflow". Call stackexchange_list_sites to discover valid values. | stackoverflow |
| sort | No | Result ordering: "relevance" (default, best match), "votes" (highest score first), "activity" (most recently active), "newest" (most recently created). | relevance |
| tags | No | Filter results to questions with all specified tags. | |
| query | Yes | Full-text search query (e.g. "python async generator send value"). | |
| minScore | No | Minimum question score — excludes questions with lower scores. | |
| pageSize | No | Number of results to return (1–30, default 10). | |
| acceptedOnly | No | When true, return only questions that have an accepted answer. |
Output Schema
| Name | Required | Description |
|---|---|---|
| cap | No | The pageSize cap applied to this request. |
| shown | No | Number of results returned. |
| notice | No | Actionable guidance when results are empty or filtered. |
| quotaMax | Yes | Maximum API quota calls per day (300 keyless, ~10,000 with API key). |
| questions | Yes | Questions matching the search query, ordered by the specified sort. |
| truncated | No | True when results were capped at pageSize. |
| attribution | Yes | Content license notice. Stack Exchange content is licensed under CC BY-SA 4.0 and requires attribution. |
| quotaRemaining | Yes | Remaining API quota calls for the current day. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare safe read-only behavior. The description adds the important behavioral trait that no bodies are returned at this stage, providing context beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, each serving a clear purpose: stating goal and result, linking to another tool, and explaining site usage. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of an output schema and rich annotations, the description provides sufficient context: it explains the workflow, site discovery, and the partial nature of results. It covers the essential information an agent needs.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3. The description adds little beyond what is in the schema, but it does summarize key parameters like `sort` and `site` succinctly.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches questions across a Stack Exchange site, returns ranked results with specific fields, and explicitly mentions it returns no bodies, differentiating it from related tools like stackexchange_get_thread.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It tells users to use the `site` parameter and points to stackexchange_list_sites for valid values. It also implies that for full question bodies, stackexchange_get_thread should be used, but does not explicitly list when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!