{
"mcpServers": {
"teamcity-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 34 days ago.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for Teamcity Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
TeamCity 2025.11 server plugin exposing MCP tools via the Java MCP SDK, using an SSE + message transport implemented on top of TeamCity's javax.servlet endpoints.
The official Java MCP SDK provides Servlet-based transports built on jakarta.servlet (Servlet 6). TeamCity server plugins still use javax.servlet, so this plugin ships a small, compatible SSE transport that implements the MCP server transport interface while running inside TeamCity's web layer.
Set internal property mcp.tokens on the TeamCity server (comma-separated).
Example in internal.properties:
mcp.tokens=token1,token2
Auth headers supported:
Authorization: Bearer <token>X-Api-Token: <token>GET /mcp/ssePOST /mcp/message?sessionId=...The MCP server emits the message endpoint via the SSE endpoint event, e.g.:
/mcp/message?sessionId=....
start_build
{ "buildTypeId": "MyProject_Build" }{ "buildId": 12345, "queueItemId": "678", "state": "queued" }build_status
{ "id": "<buildIdOrQueueItemId>" }{ "buildId": 12345, "state": "running|finished|queued", "status": "success|failure|unknown" }build_log
{ "id": "<buildId>" }{ "buildId": "12345", "logUrl": "<server>/downloadBuildLog.html?buildId=12345&plain=true" }JAVA_HOME=$(/usr/libexec/java_home -v 17) mvn -Dmaven.repo.local=/Volumes/app/work/local-mcp/.m2 package
Plugin ZIP will be produced at:
target/teamcity-mcp-plugin.zip