Content Tools
brainfish.engineering
An MCP server that enables searching, retrieving, and listing help center articles, collections, and sections from a knowledge base.
ENDPOINT 1
https://brainfish.engineering/mcp
MCP server metadata
- Name
- Brainfish Help Center
- Version
- 1.0.0
Known tools 7
get_articleFetch the full markdown content of a help center article by slug or URL id.
Inferred read-onlylist_sectionsList navigation sections and their sources (CMS collections, OpenAPI catalogs, Zendesk).
Inferred read-onlylist_articles_in_collectionList articles in a CMS collection (sourceId) with pagination.
Inferred read-onlyget_api_endpointGet full API endpoint details (params, body, responses) by operationId or method+path.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.brainfish-help-center]
url = "https://brainfish.engineering/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"brainfish-help-center": {
"type": "http",
"url": "https://brainfish.engineering/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: brainfish-help-center
Remote MCP URL: https://brainfish.engineering/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"brainfish-help-center": {
"url": "https://brainfish.engineering/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"brainfish-help-center": {
"type": "http",
"url": "https://brainfish.engineering/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "brainfish-help-center",
"transport": "streamable-http",
"url": "https://brainfish.engineering/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.