blind-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLIND_COOKIE | No | Optional session cookie header for Blind. Copy from a logged-in browser request. Off by default. | |
| BLIND_MCP_CACHE_DIR | No | Directory for on-disk response caching. | |
| BLIND_MCP_CACHE_TTL | No | Cache time-to-live in seconds (default 6 hours). | |
| BLIND_MCP_USER_AGENT | No | The User-Agent header sent with requests. | |
| BLIND_MCP_MIN_INTERVAL | No | Minimum interval between requests in seconds (default ~1.5s). |
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 |
|---|---|
| company_topicsA | List the discussion topics Blind itself suggests for a company. These are the highest-signal entry points -- e.g. Roku exposes india, wlb,
culture, layoffs, interview, rsu. Use one as the |
| company_postsA | List posts about a company, optionally narrowed to one topic.
|
| read_postA | Read one Blind post in full. Returns the body, Blind's own AI summary of the comment thread, and the comments with each commenter's employer -- which is how you weigh a claim (an answer from someone at the company differs from a passer-by). |
| findA | Find a company's posts about one keyword. This is how you search Blind. The company topic path accepts any keyword,
so Returns no posts when nothing matches, rather than falling back to the generic listing, so an empty result is a real answer. |
| researchA | Answer a question about a company by pulling the most relevant threads. Probes the distinctive words in the question against Blind's keyword-scoped company pages, merges the hits, then returns the best threads in full with Blind's own AI summary and the comments that actually address the question. Ask naturally: "how many days in office in India", "what is the maternity leave policy", "do they require a PhD". |
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
The tools generally occupy distinct layers: topic discovery, listing, keyword search, question answering, and full post reading. The only mild overlap is between company_posts and find, since both return company posts, but their input styles (curated topic vs arbitrary keyword) make the split understandable.
Names are readable and consistently lowercase, but the pattern is mixed: company_topics and company_posts are noun-style resources, read_post is verb_noun, and find/research are bare verbs. There is no single predictable naming convention across the set.
Five tools is a well-scoped size for a read-only Blind search and research server. Each tool serves a meaningful step in the workflow without unnecessary bloat or duplication.
The toolset covers the full read-oriented workflow: discover company topics, list posts, search by keyword, ask a natural-language research question, and read a full post with comments. There are no obvious gaps for the stated domain.