teamcity
teamcity is an MCP server published by Daghis, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does teamcity support the current MCP specification (2026-07-28)?
Not yet confirmed. teamcity is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is teamcity a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for teamcity (as of 2026-08-20).
How do I connect to teamcity?
teamcity is available via the package npm:@daghis/teamcity-mcp, the official MCP Registry under io.github.Daghis/teamcity, the source repository at https://github.com/daghis/teamcity-mcp. Authentication: unknown. Transports: stdio.
Does teamcity support MCP revision 2026-07-28?
No. teamcity was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
Does teamcity support MCP revision 2025-11-25?
Yes. teamcity supports MCP revision 2025-11-25 (checked 2026-08-20).
When were teamcity's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
MCP server exposing JetBrains TeamCity CI/CD workflows to AI coding assistants
Which MCP spec revisions does teamcity support?
teamcity has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2026-07-28 | Not supported | Source | |
| MCP 2025-11-25 | Supported | Source |
How widely adopted is teamcity?
Ranked #260 in The MCP 500 with Adoption Index 49.28 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 493 | API · |
| GitHub stars | 29 | API · |
| GitHub forks | 21 | API · |
| Last push | 2026-08-31T14:25:54Z | API · |
| Repository archived | no | API · |
Repository and package signals for teamcity
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 1
- Primary language
- TypeScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- Present
Declared topics: automation, cd, ci, devops, mcp, model-context-protocol, nodejs, teamcity, typescript — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
2.12.1- Last published
- First published
- Releases
- 109
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 7
- Unpacked size
- 1.7 MB
- Registry signature
- Signed
- Build provenance
- Attested
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.Daghis/teamcity at version 2.12.1 - lists package npm:@daghis/teamcity-mcp and repository https://github.com/daghis/teamcity-mcp - accessed
- npm registry metadata for @daghis/teamcity-mcp at published version 2.12.1, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed