runn-mcp-server
MCP server for the Runn API, enabling resource management and reporting through natural language.
README
runn.io MCP Server
Standalone MCP server for the Runn API with simple reporting helpers.
Requirements
- Python 3.10+
- Runn API key (
RUNN_API_KEY)
Install
python3 -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
pip install -r requirements.txt
Windows (PowerShell)
py -m venv .venv
.\\.venv\\Scripts\\Activate.ps1
py -m pip install --upgrade pip
pip install -r requirements.txt
Windows (Command Prompt)
py -m venv .venv
.\\.venv\\Scripts\\activate.bat
py -m pip install --upgrade pip
pip install -r requirements.txt
macOS (zsh/bash: Homebrew + venv)
brew install python@3.11
python3 -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
pip install -r requirements.txt
Run (MCP server)
stdio (Claude Desktop)
RUNN_API_KEY=LIVE_... python3 mcp_runn_server.py --transport stdio
stdio (Windows PowerShell)
$env:RUNN_API_KEY="LIVE_..."
py mcp_runn_server.py --transport stdio
stdio (macOS / zsh)
RUNN_API_KEY=LIVE_... python3 mcp_runn_server.py --transport stdio
streamable-http (default)
RUNN_API_KEY=LIVE_... python3 mcp_runn_server.py --transport streamable-http
streamable-http (Windows PowerShell)
$env:RUNN_API_KEY="LIVE_..."
py mcp_runn_server.py --transport streamable-http
streamable-http (macOS / zsh)
RUNN_API_KEY=LIVE_... python3 mcp_runn_server.py --transport streamable-http
Run with Docker
Build the image:
docker build -t runn-mcp-server .
Windows PowerShell
docker build -t runn-mcp-server .
Run the container (HTTP transport):
docker run --rm -e RUNN_API_KEY=LIVE_... -p 8000:8000 runn-mcp-server
Windows PowerShell
docker run --rm -e RUNN_API_KEY=LIVE_... -p 8000:8000 runn-mcp-server
macOS (Docker Desktop)
docker run --rm -e RUNN_API_KEY=LIVE_... -p 8000:8000 runn-mcp-server
GHCR image
The GitHub Actions workflow publishes to:
ghcr.io/gemini2026/runn-mcp-server
Pull and run:
docker pull ghcr.io/gemini2026/runn-mcp-server:main
docker run --rm -e RUNN_API_KEY=LIVE_... -p 8000:8000 ghcr.io/gemini2026/runn-mcp-server:main
Windows PowerShell
docker pull ghcr.io/gemini2026/runn-mcp-server:main
docker run --rm -e RUNN_API_KEY=LIVE_... -p 8000:8000 ghcr.io/gemini2026/runn-mcp-server:main
macOS (Docker Desktop)
docker pull ghcr.io/gemini2026/runn-mcp-server:main
docker run --rm -e RUNN_API_KEY=LIVE_... -p 8000:8000 ghcr.io/gemini2026/runn-mcp-server:main
Claude Desktop config snippet
{
"mcpServers": {
"runn": {
"command": "/path/to/python3",
"args": [
"/path/to/mcp_runn_server.py",
"--transport",
"stdio"
],
"env": {
"RUNN_API_KEY": "<YOUR_API_KEY>"
}
}
}
}
Windows paths example
{
"mcpServers": {
"runn": {
"command": "C:\\\\Python311\\\\python.exe",
"args": [
"C:\\\\path\\\\to\\\\mcp_runn_server.py",
"--transport",
"stdio"
],
"env": {
"RUNN_API_KEY": "<YOUR_API_KEY>"
}
}
}
}
MCP tools
list_projects— returns{id, name}pairs.list_people— returns{id, name, email}by default (setfull=truefor raw objects).billable_hours— aggregates billable hours grouped by project/person/month.list_clients— list clients (raw API objects).list_assignments— list assignments (raw API objects).list_assignments_by_person— assignments for a person, optional date range.list_assignments_by_project— assignments for a project, optional date range.list_assignments_by_role— assignments for a role, optional date range.list_assignments_by_team— assignments for a team’s people, optional date range.list_actuals— list actuals (raw API objects).list_actuals_by_date_range— actuals in a date range, optional person/project filters.list_actuals_by_person— actuals for a person, optional date range.list_actuals_by_project— actuals for a project, optional date range.list_actuals_by_role— actuals for a role, optional date range.list_actuals_by_team— actuals for a team’s people, optional date range.list_roles— list roles (raw API objects).list_roles_by_person— roles that include a person.list_skills— list skills (raw API objects).list_skills_by_person— skills for a person with levels + names.list_teams— list teams (raw API objects).list_people_by_team— people in a team (optionally include archived).list_people_by_skill— people who have a skill (optional min level).list_people_by_tag— people with a tag (by id or name).list_people_by_manager— people managed by a manager id.list_rate_cards— list rate cards (raw API objects).list_rate_cards_by_project— rate cards that include a project.runn_request— call any Runn API endpoint (GET/POST/PATCH/PUT/DELETE).
Pagination for list endpoints:
{
"method": "GET",
"path": "/projects",
"paginate": true
}
Filter-specific tools (e.g., list_assignments_by_person) fetch list endpoints and apply filters client-side.
Usage examples
HTTP transport (streamable-http)
-
Start the server:
RUNN_API_KEY=LIVE_... python3 mcp_runn_server.py --transport streamable-http -
Invoke a specific tool via HTTP:
curl -s http://localhost:8000/api \ -H "Content-Type: application/json" \ -d '{ "tool": "list_actuals_by_person", "args": { "person_id": 123, "start": "2025-01-01", "end": "2025-01-31" } }' | jq -
Go straight to the raw Runn API:
curl -s http://localhost:8000/api \ -H "Content-Type: application/json" \ -d '{ "tool": "runn_request", "args": { "method": "GET", "path": "/projects" } }' | jq
stdio transport (Claude/Desktop or script)
printf '{"tool":"list_projects"}' | RUNN_API_KEY=LIVE_... python3 mcp_runn_server.py --transport stdio
Claude will read the JSON response from stdout, just like any MCP client.
Docker usage
docker run --rm -e RUNN_API_KEY=LIVE_... -p 8000:8000 runn-mcp-server
Connect via the HTTP examples above or switch to stdio by appending --transport stdio on the Docker command.
Reports (optional)
runn_reports.py can export billable hours grouped by project/person/month.
RUNN_API_KEY=LIVE_... python3 runn_reports.py --start 2025-01-01 --end 2025-12-31 --output billable.csv
PDF output requires ReportLab:
python -m pip install reportlab
CI/CD
- CI runs on every push and pull request to
main. - CD publishes a GitHub Release when you push a tag like
v0.1.0.
Example release:
git tag v0.1.0
git push origin v0.1.0
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。