timeghost MCP Server for CursorGive Cursor instant access to 10 tools to Check Timeghost Status, Get Timeghost Entry, Get Timeghost Project, and more
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this App Connector for Cursor
The timeghost app connector for Cursor is a standout in the Productivity category — giving your AI agent 10 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install timeghost and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"timeghost": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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
About timeghost MCP Server
Connect your timeghost account to any AI agent and take full control of your Microsoft 365 integrated time tracking and project orchestration through natural conversation.
Cursor's Agent mode turns timeghost into an in-editor superpower. Ask Cursor to generate code using live data from timeghost and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
What you can do
- Timesheet Portfolio Orchestration — List all time entries, retrieve detailed high-fidelity status metadata, and monitor team productivity programmatically
- Project Intelligence Architecture — Query projects and budgets, retrieve detailed technical metadata, and access real-time project health metrics
- Task Pipeline Management — Access your complete directory of high-fidelity tasks, manage assignments, and stay on top of operational delivery directly through your agent
- Workspace Discovery — Access complete high-fidelity workspace profiles and organizational settings to understand and orchestrate your environment programmatically
- Contact & Team Monitoring — List team members and collaborators to maintain perfect contextual alignment for every time log and project assignment
- Operational Monitoring — Verify account-level API connectivity and monitor time log orchestration volume directly through your agent for perfectly coordinated service scaling
The timeghost MCP Server exposes 10 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 10 timeghost tools available for Cursor
When Cursor connects to timeghost through Vinkius, your AI agent gets direct access to every tool listed below — spanning time-tracking, project-management, microsoft-365, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
Check API Status
Get a specific time entry
Get details for a specific project
Get details for a specific task
List clients
Optionally filter by date range or specific user. List time entries
List workspace members
List projects
Filter by project ID to isolate specific technical pipelines. List tasks
List workspaces
Connect timeghost to Cursor via MCP
Follow these steps to wire timeghost into Cursor. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using timeghost
Why Use Cursor with the timeghost MCP Server
Cursor AI Code Editor provides unique advantages when paired with timeghost through the Model Context Protocol.
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
timeghost + Cursor Use Cases
Practical scenarios where Cursor combined with the timeghost MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for timeghost in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with timeghost immediately.
"List all active projects in my timeghost account."
"Show the last 5 time entries for task 'API Design'."
"Check the connectivity status for the 'Marketing' workspace."
Troubleshooting timeghost MCP Server with Cursor
Common issues when connecting timeghost to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
timeghost + Cursor FAQ
Common questions about integrating timeghost MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
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.