TaskUp MCP Server

How to use

You connect a compatible MCP client to this server using a variety of methods tailored to your preferred client. The server supports direct SSE URLs for native clients, and a local proxy approach for clients that require a compatibility layer. You can run multiple concurrent sessions safely, thanks to stateless design and session routing that keeps each interaction isolated.

How to install

Prerequisites - Node.js or Bun runtime installed on your machine - Access to a terminal or shell - A compatible MCP client to connect to the server workflow Steps 1. Prepare your environment variables if you plan to run with the local proxy setup. 2. Start the server using the recommended runtime command. 3. Connect with an MCP client using one of the supported connection methods.

# Quick start (local run)
bun run src/server/index.ts

# Or, if you prefer a standard Node.js run (alternative)
node --version
# then execute your startup command as appropriate for your project setup

Configuration, security, and usage notes

Connection options you can use right away are shown in practical examples. Choose the method that matches your client’s capabilities and your security preferences.

Option 1: Claude Desktop compatibility proxy (local proxy required by Claude Desktop) This approach uses a compatibility proxy to connect via a built-in mechanism. You provide a command to run the proxy and point to a local proxy file path. You also supply a remote SSE URL and an Arcade token for authentication.

{
  "mcpServers": {
    "taskup": {
      "command": "bun",
      "args": [
        "run",
        "/Users/you/path/to/your/proxy.ts"
      ],
      "env": {
        "REMOTE_URL": "https://personal-execution-mcp-vfh76wyjna-uc.a.run.app/sse",
        "ARCADE_TOKEN": "YOUR_ARCADE_TOKEN"
      }
    }
  }
}

Option 2: Cursor / Windsurf / ChatGPT clients (direct SSE URLs supported) Use the direct SSE URL provided below for clients that support native SSE connections.

{
  "type": "http",
  "name": "taskup_http",
  "url": "https://personal-execution-mcp-vfh76wyjna-uc.a.run.app/sse",
  "args": []
}

Option 3: Zed Editor (settings.json integration) Add a connection entry pointing to the SSE URL to your editor’s settings.

{
  "context_servers": [
    {
      "name": "taskup",
      "url": "https://personal-execution-mcp-vfh76wyjna-uc.a.run.app/sse"
    }
  ]
}

Observability and health

The server emits structured JSON logs for easy ingestion by monitoring systems. You can verify operational readiness with a health check endpoint.

GET http://localhost:3000/health

Notion integration

Enables interaction with Notion data and workflows via MCP actions.

Google Calendar integration

Allows reading and manipulating calendar events through MCP actions.

Telegram integration

Coordinates messages and actions with Telegram for workflow orchestration.

Health endpoint

Provides a health check to confirm MCP server readiness.