# Coding.net MCP for AI Agents AI Agent Connect > Coding.net MCP lets your agent manage your entire DevOps lifecycle on the Coding.net platform. It handles project organization, repository auditing, and issue tracking through a natural chat interface. You can check merge requests, pull commit data, and monitor team velocity without leaving your workspace. ## Overview - **Category:** ship-it - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_AJ7odH2bw0ys8H25LcdxuA37au5IdXHcCtzcXMQP/ai-agent-connect - **Tags:** git-repository, issue-tracking, software-lifecycle, collaboration, devops-platform, code-management ## Description Imagine you're trying to track down why a release is stalled. Instead of hunting through nested folders in the web interface, you just ask your agent what's going on with a specific project. It pulls up the active merge requests and identifies the blockers instantly. You're not just looking at data; you're getting answers. This Connector turns your DevOps platform into a conversational workspace. Whether you need to audit every commit in a specific repository or grab a list of all open bugs to share with the team, your agent does the heavy lifting. It pulls the metadata, organizes the list, and gives you the highlights. If you're looking for a way to keep your development flow moving without the constant tab-switching, this is how you do it. It's one of the many specialized connectors available in the Vinkius catalog that brings your specific tools into your daily workflow. You get to stay focused on the code while your agent handles the administrative overhead of the DevOps lifecycle. ## Tools ### get_issue Retrieve the full text and status of a specific bug or task to understand a blocker. It's great for quickly checking the priority of a ticket. ### get_user Fetch the profile information for a team member to see their role and permissions. It's useful for checking who owns which part of the project. ### get_commit Pull specific details for a single commit to see exactly what changed in a push. This helps you understand the history of a specific change. ### get_project Get the core metadata for a project to see its current status and organizational unit. Use this to see how a project is structured. ### get_repo Pull specific details about a repository to check its configuration or size. This gives you a quick snapshot of your codebase. ### list_branches See all active branches in a repository to identify where development is happening. This helps you spot where the latest work is being pushed. ### list_issues Get a full list of project tasks and bugs to monitor team velocity. You can use this to see what's left on the sprint board. ### list_mrs Identify all active merge requests to see what's waiting for a code review. This is a fast way to see where the pipeline is stuck. ### list_projects See every DevOps project in your organization at a glance. It's the easiest way to get an overview of your entire portfolio. ### list_repos List all repositories within a project to audit the codebase structure. Use this to see every repo you have in a specific project. ## Prompt Examples **Prompt:** ``` What's the status of our 'Alpha' project? ``` **Response:** ``` I've checked the status for project 'Alpha'. Here's what I found: * **Open Issues:** 12 * **Active Merge Requests:** 3 * **Recent Activity:** - *Bug: Login Timeout* (High Priority) - *Feature: Dark Mode* (In Review) Would you like me to pull the details for the high-priority bug? ``` **Prompt:** ``` Are there any merge requests waiting for review? ``` **Response:** ``` I found 3 active merge requests waiting for attention: | Request # | Title | Author | Status | | :--- | :--- | :--- | :--- | | 102 | Fix auth header | @dev_user_1 | Pending Review | | 105 | Update README | @dev_user_2 | Pending Review | | 108 | Refactor API | @dev_user_3 | Pending Review | Should I get more details on any of these? ``` **Prompt:** ``` Show me the branches for the main-api repo. ``` **Response:** ``` I've retrieved the branches for the 'main-api' repository. You have 4 active branches: * `master` * `develop` * `feature/api-v2` * `hotfix/auth-patch` Would you like to see the latest commit on any of these? ``` ## Capabilities ### List all DevOps projects See every project in your organization in a single list. ### Retrieve repository metadata Get detailed information about your project's repositories. ### Browse active merge requests Identify pending reviews and blockers across your projects. ### Monitor issue progress Track the status and velocity of tasks and bugs. ### Get commit details Pull specific information about individual code commits. ### Fetch user profiles Retrieve profile data for organization members and the current user. ## Use Cases ### Audit a repository A lead needs to know every branch in a repo. They ask the agent to list them, and it pulls the data from `list_branches` instantly. ### Status check A PM wants to know why a project is late. The agent uses `list_issues` to find high-priority bugs and `list_mrs` to find stuck reviews. ### Onboarding A new dev needs to see the project structure. The agent uses `list_projects` and `list_repos` to give a full map of the workspace. ### Code Review An engineer wants to see the latest work. The agent uses `get_commit` to summarize the most recent changes for a specific pull request. ## Benefits - Stop clicking through the Coding.net web UI by using `list_projects` to see your entire portfolio in one chat. - Identify release blockers faster by using `list_mrs` to see every pending review across your team. - Track team velocity accurately by using `list_issues` to get a real-time count of open bugs and tasks. - Audit your codebase with precision by using `list_repos` and `list_branches` to see your full repository structure. - Get instant context on changes by using `get_commit` to see exactly what went into a specific push without searching logs. - Manage team permissions easily by using `get_user` to see profile info for any member of your organization. ## How It Works The bottom line is you get a conversational interface for your entire Coding.net DevOps workflow. 1. Subscribe to this Connector and get your Coding.net Team Domain and Personal Access Token. 2. Plug those credentials into your AI client's configuration settings. 3. Ask your agent to list projects or check merge requests to see the data appear in your chat. ## Frequently Asked Questions **Does Coding.net MCP work with Cursor?** Yes, it works with Cursor and any other AI client that supports the Model Context Protocol. **Can I use it to see my team's issues?** Yes, you can use it to list and retrieve detailed information about all project tasks and bugs to monitor your team's velocity. **Is this for the Coding.net DevOps platform?** Yes, this Connector is specifically designed to connect your AI agent to the Coding.net DevOps ecosystem. **How do I connect my account to this Connector?** You'll need to provide your Coding.net Team Domain and a Personal Access Token in your client's configuration. **Can it show me specific commits?** Yes, your agent can pull specific details for any commit to help you understand exactly what changed in a push. **Can I use it to audit my repositories?** Yes, you can use it to list all repositories within a project and browse branch information to audit your codebase. **How do I find my CODING Team Domain?** Your team domain is the unique URL you use to access CODING, typically in the format `your-team.coding.net`. You can find it in your browser's address bar when logged in. **How do I generate a Personal Access Token (PAT)?** Log in to CODING, go to [Personal Settings] → [Access Tokens], and click on [New Token]. Ensure you grant the necessary permissions for the resources you want to manage. **Can I access multiple repositories in a project?** Yes. Use the `list_repos` tool with your project name to see all available Git depots. You can then use `get_repo` or `list_branches` with specific repository names.