Standalone MCP server for the Runn API with simple reporting helpers.
Runn MCP server exists for a simple reason — assistants are far more useful when they can act on Runn directly instead of describing what you should do. Standalone MCP server for the Runn API with simple reporting helpers.
Once Runn is connected, these are the calls the assistant has available:
list_projects — returns {id, name} pairslist_people — returns {id, name, email} by default (set full=true for raw objects)billable_hours — aggregates billable hours grouped by project/person/monthlist_clients — list clients (raw API objects)list_assignments — list assignments (raw API objects)list_assignments_by_person — assignments for a person, optional date rangelist_assignments_by_project — assignments for a project, optional date rangelist_assignments_by_role — assignments for a role, optional date rangelist_assignments_by_team — assignments for a team’s people, optional date rangelist_actuals — list actuals (raw API objects)list_actuals_by_date_range — actuals in a date range, optional person/project filterslist_actuals_by_person — actuals for a person, optional date rangeYou will need 2 environment variables: RUNN_API_KEY, YOUR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
RUNN_API_KEY)reportlab on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Runn's toolset — list_projects, list_people, billable_hours and 11 more — is a fair guide to whether it matches your workflow. It is maintained by gemini2026; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| list_projects | returns {id, name} pairs. |
| list_people | returns {id, name, email} by default (set full=true for 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. |
{
"mcpServers": {
"runn": {
"command": "/path/to/python3",
"args": [
"/path/to/mcp_runn_server.py",
"--transport",
"stdio"
],
"env": {
"RUNN_API_KEY": "<YOUR_API_KEY>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
RUNN_API_KEY)| Variable | Description | Required |
|---|---|---|
| RUNN_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.