How to Use the Coding.net MCP in LlamaIndex

Q: How do I index Coding.net issues into LlamaIndex?

You can fetch issues using listissues and pass them to your indexer. Convert the output of this MCP Server into document objects before inserting them into your vector store. This makes your entire issue tracker searchable via natural language.

Q: Can LlamaIndex search through Coding.net merge requests?

Yes, your agent can call listmrs to retrieve active merge requests. It embeds the text descriptions and stores them for semantic querying. This lets developers search for active changes using natural language queries.

Q: How does Vinkius protect my Coding.net project and issue data?

All data fetched via getissue and getproject is transmitted over secure TLS connections. We run each session in an ephemeral V8 sandbox that is destroyed immediately after execution. Your project structures and issue details never persist on our infrastructure.

Index Coding.net repositories and issues directly into your LlamaIndex vector store for semantic search.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Coding.net MCP to LlamaIndex

Create your Vinkius account to connect Coding.net to LlamaIndex and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Coding.net with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build a queryable knowledge base of your Coding.net project using this MCP Server

Feed live repository data straight into your index. Your RAG pipeline uses `list_repos` and `list_projects` to gather structural information about your workspace. It converts this raw data into vector embeddings that your agent can search instantly. Instead of guessing where a bug was tracked, your agent searches past discussions. It uses `get_issue` to pull specific ticket details and matches them against user queries. It ensures your answers are grounded in real project history.

Keep your semantic search updated with live commits

Turn your git history into a searchable index. By calling `get_commit` on demand, your agent fetches the latest changes and updates your vector store. This keeps your documentation accurate and aligned with the actual codebase. Developers can ask the system what changed in a specific release. The MCP Server retrieves the relevant data, and LlamaIndex runs semantic search over it. It eliminates the need to manually read through git logs.

Expose merge requests directly to your RAG pipeline

Make your code review process smarter. Your pipeline calls `list_mrs` to gather open merge requests and indexes their descriptions. This allows your agent to answer questions about pending changes and active feature branches. You can filter tools using the allowed tools list to restrict what the indexer can access. It lets you safely expose `get_repo` data to your users without exposing administrative controls.

Setup guide

Set up Coding.net MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Coding.net MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Coding.net tools.",
)
response = await agent.run("List recent Coding.net data")

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Coding.net. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Coding.net now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Coding.net MCP in LlamaIndex

You can fetch issues using `list_issues` and pass them to your indexer. Convert the output of this MCP Server into document objects before inserting them into your vector store. This makes your entire issue tracker searchable via natural language.

Yes, your agent can call `list_mrs` to retrieve active merge requests. It embeds the text descriptions and stores them for semantic querying. This lets developers search for active changes using natural language queries.

Initialize the client using the Basic MCP Client with your Vinkius endpoint. Then, pass it to `McpToolSpec` and convert it using `to_tool_list_async()`. This registers tools like `get_project` directly with your agent.

Yes, you can use the allowed tools filter during setup. This lets you limit the agent to read-only operations like `list_branches` while blocking write actions. It gives you precise control over tool execution.

All data fetched via `get_issue` and `get_project` is transmitted over secure TLS connections. We run each session in an ephemeral V8 sandbox that is destroyed immediately after execution. Your project structures and issue details never persist on our infrastructure.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript