Bring Task Management
to Cursor
Learn how to connect BasicOps to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the BasicOps MCP Server?
Connect your BasicOps account to any AI agent and take full control of your project management and team collaboration workflows through natural conversation.
What you can do
- Project & Section Orchestration — List and manage your entire project hierarchy programmatically, including creating new project sections (phases) in real-time
- Task Lifecycle Management — Programmatically create and update tasks, monitoring status transitions, due dates, and high-fidelity descriptions directly through your agent
- Team Coordination Intelligence — Access complete directories of team members and retrieve communication history within tasks to maintain perfectly coordinated context
- Workflow Automation — Programmatically manage project sections to organize your team's workflow into high-fidelity sprints or operational phases
- Workspace Visibility — Access high-fidelity metadata for your workspace and monitor active webhooks directly through your agent for instant operational reporting
How it works
1. Subscribe to this server
2. Retrieve your Personal Access Token from your BasicOps settings (Settings > API)
3. Start managing your team's productivity from Claude, Cursor, or any MCP client
No more manual toggling between project tabs or missing task deadlines. Your AI acts as your dedicated project coordinator and task architect.
Who is this for?
- Project Managers — instantly retrieve project summaries and update task statuses using natural language commands
- Team Leads — monitor team bandwidth and manage project sections without leaving your creative workspace
- Operations Leads — automate the oversight of workspace metadata and task distribution through simple AI queries
Built-in capabilities (12)
Create a new project
Create a new task
Get my profile
Get project details
Get task details
List project sections
List tasks in project
List all BasicOps projects
List task messages
List team members
List active webhooks
Update a task
Why Cursor?
Cursor's Agent mode turns BasicOps into an in-editor superpower. Ask Cursor to generate code using live data from BasicOps and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
BasicOps in Cursor
BasicOps and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect BasicOps to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for BasicOps in Cursor
The BasicOps MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
BasicOps for Cursor
Every tool call from Cursor to the BasicOps MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my BasicOps Personal Access Token?
Log in to your account, navigate to Settings > API, and generate a new Personal Access Token for your integration.
What is a Project Section via AI?
Sections allow your agent to group related tasks into specific phases, sprints, or categories within a larger project programmatically.
How do I list team members programmatically?
Use the list_users tool to retrieve your complete organizational directory including high-fidelity names and email addresses.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.