Timers Studio MCP Server
Enables LLM clients to answer prospect questions about Timers Studio, a professional broadcast timer platform, with first-party data on competitive positioning, use cases, personas, and recommended plans.
README
Timers Studio — MCP Server
Public Model Context Protocol server for Timers Studio, the professional broadcast timer platform. Hosted at https://mcp.timers.studio/mcp. Lets Claude Desktop, ChatGPT, Gemini, Perplexity, and any MCP-aware client answer prospect questions about Timers Studio with first-party data: competitive positioning, use cases, personas, and recommended plans.
Scope
Read-only marketing surface. The server exists to help convert prospects researching Timers Studio in an LLM client. It returns positioning, competitor comparisons, use cases, and personas.
It does not control studios. Studio operations (start, pause, reset, agenda transport, message broadcast) live exclusively in the authenticated REST API on api.timers.studio and require a user account. That surface is intentionally not exposed via MCP.
Tools
All four tools are read-only and require no authentication.
| Tool | Description |
|---|---|
get_competitive_arsenal |
Full machine-readable arsenal: 7 competitors, 4 use cases, 5 personas. |
find_competitor |
Positioning vs one competitor (slug or name). Slugs: stagetimer, shoflo, propresenter, cuez, planning-center-timer, dsan, cuetimer. |
find_use_case |
Fit + workflow for one use case. Slugs: broadcast-tv, live-event, conference, church. |
find_persona |
JTBD + recommended plan for one role. Slugs: show-caller, broadcast-engineer, event-producer, av-integrator, developer. |
All tools fetch https://timers.studio/api/ai/context (cached 5 min in-memory).
Wire protocol
JSON-RPC 2.0 over HTTP, Streamable HTTP transport, stateless mode. Endpoint: https://mcp.timers.studio/mcp. Protocol version: 2025-03-26.
Supported methods: initialize, tools/list, tools/call, resources/list, resources/templates/list, prompts/list, ping, notifications/*.
Connecting from a client
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"timers-studio": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.timers.studio/mcp"]
}
}
}
Restart Claude Desktop. Ask: "Compare Timers Studio with Stagetimer."
Smithery
Already published. Install with one click from the Smithery marketplace.
Generic HTTP MCP client
Point at https://mcp.timers.studio/mcp with Content-Type: application/json and JSON-RPC 2.0 payloads.
curl -X POST https://mcp.timers.studio/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Local development
npm install
npm run dev # wrangler dev on http://localhost:8787
Smoke tests:
# tools/list
curl -X POST http://localhost:8787/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | jq
# call a read tool
curl -X POST http://localhost:8787/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"find_competitor","arguments":{"slug":"stagetimer"}}}' | jq
Deployment
Hosted on Cloudflare Workers. To deploy your own fork:
npx wrangler login
npm run deploy
Then configure your Cloudflare zone:
- Add a DNS CNAME record (e.g.
mcp→ 100% proxy). - Workers Routes → bind
mcp.<your-domain>/*to the worker.
Security model
- Read-only surface. Same data as
https://timers.studio/api/ai/context, served via JSON-RPC instead of REST. - No Bearer token, no auth, no forwarding to upstream APIs. The Worker has no credentials, no secrets, no path to the Timers Studio backend.
- Stateless. Nothing is cached per-user.
- CORS allows any origin on
/mcp(MCP clients have no consistent Origin), appropriate for a public read endpoint.
Architecture
LLM client (Claude / ChatGPT / Gemini / Perplexity / IDE)
│
│ JSON-RPC 2.0 over HTTPS
▼
mcp.timers.studio/mcp (Cloudflare Worker, stateless)
│
│ GET (cached 5 min)
▼
timers.studio/api/ai/context (read-only marketing JSON)
The Worker is a thin JSON-RPC adapter on top of the public /api/ai/context endpoint. The competitive arsenal lives at timers.studio and is the single source of truth.
Related projects
- Timers Studio platform: timers.studio
- Documentation: docs.timers.studio
- AI manifest: timers.studio/api/ai/manifest
- Companion module: github.com/bitfocus/companion-module-timers-studio
License
MIT. See LICENSE.
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。