tc-help-mcp
Provides live access to TutorCruncher and Bobbin product documentation via Intercom and GitHub, enabling Claude to search and retrieve help articles and API docs on demand.
README
tc-help-mcp
A remote MCP server that gives the team's Claude.ai workspace live, always-current access to product documentation across the portfolio — TutorCruncher and Bobbin — with room to add more products by config alone.
It is a general product-docs assistant: the team adds it once as a remote connector and asks questions; Claude calls the tools, the server fetches from source on demand, and Claude reasons over the returned content. There is no local index and no persisted copy of the docs — the docs are the only source of truth, so answers never drift. A short in-memory TTL cache (default 300s) exists purely for latency/rate-limit protection.
Sources at launch:
- TutorCruncher help docs — Intercom help centre, via the Intercom Articles API.
- Bobbin help docs — Intercom help centre (separate Intercom workspace → separate token).
- TutorCruncher API docs — the public
tutorcruncher/tc-api-docsrepo.
Tools
Help tools take an optional product filter ("tutorcruncher" | "bobbin"); unset spans all
configured products. Every result carries its product so answers stay correctly attributed.
| Tool | Purpose |
|---|---|
list_help_articles(product=None) |
Lightweight catalogue (product, id, title, description, url, collection). No bodies. |
search_help(query, product=None) |
Server-side Intercom search across product(s); deduped, ranked, top N {product, id, title, summary, url}. |
get_help_article(product, id) |
Full cleaned article body (markdown, boilerplate stripped) + title and url. |
list_api_sections() |
All API sections from api.yml ({id, title, kind}). |
search_api_docs(query) |
Keyword filter over section and subsection titles → matching whole sections. |
get_api_section(id) |
Whole section assembled to markdown: endpoints, params, request/response examples, version notes. |
tc-api-docs structure (Outcome B)
pages/api.yml is an index (info_sections + endpoint_sections), each entry pointing to a
layout file (e.g. pages/clients/clients.yml). A layout's sections: list references separate
content files per subsection: description (.md), attributes/filters (.yml), response
(.json), and code (.py) plus code_type/code_url. Paths are repo-absolute under
pages/. get_api_section resolves a section, fetches its layout, fans out over the referenced
files (cached, concurrency-capped) and assembles one clean markdown document.
Configuration
All configuration is via environment variables (see .env.example). Never
commit values. Each Intercom workspace has its own token — one token does not span both products.
| Variable | Default | Purpose |
|---|---|---|
GITHUB_OAUTH_CLIENT_ID / GITHUB_OAUTH_CLIENT_SECRET |
— | GitHub OAuth App credentials. |
BASE_URL |
— | Public HTTPS base URL of this server (callback <BASE_URL>/auth/callback). |
GITHUB_SCOPES |
read:org read:user |
Scopes needed to verify org membership. |
ALLOWED_GITHUB_ORG |
— | Only active members of this org may use the tools. |
ALLOW_UNGATED |
0 |
Set 1 to run without an org gate (local dev only). |
ALLOWED_REDIRECT_URIS |
https://claude.ai/api/mcp/auth_callback |
Permitted OAuth client redirect URIs. |
JWT_SIGNING_KEY |
— | Signing key for FastMCP-issued JWTs. |
INTERCOM_API_BASE |
https://api.intercom.io |
Intercom API host (same for both workspaces). |
INTERCOM_TOKEN_TUTORCRUNCHER |
— | TutorCruncher Intercom workspace token. |
INTERCOM_TOKEN_BOBBIN |
— | Bobbin Intercom workspace token. |
TC_API_DOCS_REPO |
tutorcruncher/tc-api-docs |
API-docs repo. |
TC_API_DOCS_REF |
master |
API-docs git ref. |
GITHUB_TOKEN |
— | Optional, raises raw-content fetch rate limits (distinct from the OAuth creds). |
CACHE_TTL_SECONDS |
300 |
In-memory cache TTL (latency/rate-limit protection only). |
SEARCH_RESULT_LIMIT |
8 |
Max search_help results. |
PORT |
8000 |
Bind port (Heroku sets this automatically). |
LOGFIRE_TOKEN |
— | Optional. When set, traces httpx upstream calls + tool spans to Pydantic Logfire. Unset = fully disabled. |
Observability
Observability is opt-in via LOGFIRE_TOKEN. With it set, the server instruments httpx
(every Intercom and GitHub request traced with status and latency) and wraps each tool
call in a span. With no token, Logfire runs in local-only mode and exports nothing — tests
and local runs are unaffected. httpx instrumentation uses conservative defaults (no header
or body capture), so workspace tokens and credentials are never sent to Logfire.
Adding another product
A product is one line in KNOWN_HELP_PRODUCTS in app/config.py ((product, help_centre_base))
plus an INTERCOM_TOKEN_<PRODUCT> env var. Products whose token is unset are skipped. No tool
changes are needed.
Local development
make install-dev # deps + pre-commit hooks
cp .env.example .env # fill in tokens; set ALLOW_UNGATED=1 for local use
make lint # ruff + ty
make test # pytest -n auto
make run-dev # serve on 0.0.0.0:$PORT
Deployment
Built as a single-stage Docker image and released to Heroku (container stack) by
.github/workflows/deploy.yml on push to main. Set secrets via Heroku config, never the repo:
Deploys run via .github/workflows/deploy.yml (GitHub Actions builds the image and
releases it to the container-stack Heroku app help-mcp on push to main). The repo
needs a HEROKU_API_KEY secret; the Heroku app needs its config vars set:
heroku stack:set container -a help-mcp
heroku config:set -a help-mcp \
GITHUB_OAUTH_CLIENT_ID=... GITHUB_OAUTH_CLIENT_SECRET=... \
BASE_URL=https://help-mcp-5710e51f90a5.herokuapp.com \
JWT_SIGNING_KEY="$(openssl rand -hex 32)" \
ALLOWED_GITHUB_ORG=tutorcruncher \
INTERCOM_TOKEN_TUTORCRUNCHER=... INTERCOM_TOKEN_BOBBIN=...
Then register https://help-mcp-5710e51f90a5.herokuapp.com/mcp as a remote connector in
the team's Claude.ai workspace.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。