Vinkius
ONES logo
Vinkius
Vinkius runs on Claude Code

How to Use the ONES MCP in Claude Code

Connect Claude Code to ONES and manage enterprise R&D tasks via this MCP integration directly from your terminal or CI/CD pipelines.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

ONES MCP on Cursor AI Code Editor MCP Client ONES MCP on Claude Desktop App MCP Integration ONES MCP on OpenAI Agents SDK MCP Compatible ONES MCP on Visual Studio Code MCP Extension Client ONES MCP on GitHub Copilot AI Agent MCP Integration ONES MCP on Google Gemini AI MCP Integration ONES MCP on Lovable AI Development MCP Client ONES MCP on Mistral AI Agents MCP Compatible ONES MCP on Amazon AWS Bedrock MCP Support
MCP Servers — Included with Plan
Vinkius runs on Claude Code

Connect ONES MCP to Claude Code

Create your Vinkius account to connect ONES to Claude Code — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Key Capabilities

Headless Task Management via MCP Server

DevOps engineers don't want to click through a web portal to log infrastructure changes. Claude Code lets you pipe a failed deployment log straight into `create_task` directly from your shell. The CLI agent automatically formats the payload, checks `list_task_types` to tag it as an incident, and assigns it to the on-call engineer. You handle complete project management without ever leaving your terminal window.

Automate Release Notes and Audits

Scraping together a changelog before a Friday deployment is a massive time sink. You can script Claude Code to run `list_tasks` against your current sprint and filter out everything that isn't merged. It pulls the exact descriptions using `get_task_details` and formats them into a clean markdown file. If you need to verify who approved what, the agent pulls `list_members` to cross-reference the reviewers against your organization chart.

Enforce Strict Workflow Transitions

CI/CD pipelines fail when developers forget to update their ticket statuses. You can integrate Claude Code into a GitHub Action that triggers `list_workflows` via the MCP server whenever a pull request merges. The headless agent verifies the target project via `get_project` to ensure it hits the right board. It then fires `update_task` to push the ticket into the deployment column automatically.

Setup guide

Set up ONES MCP in Claude Code

Prerequisites

  • Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Run the add command

    Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.

  2. 2

    Verify the connection

    Start a Claude Code session and type /mcp to list connected servers. You should see ones-mcp with a green status indicator.

  3. 3

    Start using tools

    Ask Claude Code something like "Check my latest ONES transactions." It will automatically discover and invoke the available ONES tools.

Terminal
claude mcp add --transport http ones-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Why Choose Vinkius

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

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 ONES MCP in Claude Code

Run `claude mcp add --transport http ones-mcp -- ` in your terminal. Make sure you put the transport flags before the server name, then use `claude mcp list` to confirm the connection.
Yes, you can pipe standard output directly into the agent. It parses your script's output and executes `create_task` to log the results on your enterprise board.
The agent queries `list_projects` to match your repository name with the corresponding internal board. If the names differ, you can explicitly pass the project UUID in your prompt.
The user UUID probably doesn't match the display name in your git config. Have the agent run `list_members` to pull the exact internal IDs before it attempts the assignment.
The workflow transition rules and task metadata pulled by the terminal agent are protected by strict endpoint authentication. Vinkius manages the connection so your proprietary sprint backlogs only pass through an encrypted, ephemeral tunnel.

Start using the ONES MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 10 tools

We've already built the connector for ONES. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting. You're up and running in seconds.

Vinkius runs on Claude Claude
Vinkius runs on ChatGPT ChatGPT
Vinkius runs on Cursor Cursor
Vinkius runs on Gemini Gemini
Vinkius runs on Windsurf Windsurf
Vinkius runs on VS Code VS Code
Vinkius runs on JetBrains JetBrains
Vinkius runs on Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.