tickadoo MCP Server

@tickadoo/mcp-server is the local stdio entrypoint for tickadoo MCP. Since v2.0.0 it is a thin bridge to the canonical remote server at:

https://mcp.tickadoo.com/mcp

The package no longer defines tools, formats catalogue data, or calls a local tickadoo backend. It connects to the remote Streamable HTTP MCP server and proxies tools/list, tools/call, resources/list, resources/read, and ping. The live remote owns the tool list, schemas, results, and errors.

No API key is required.

Install

Use the hosted remote directly when your MCP client supports Streamable HTTP:

{
  "mcpServers": {
    "tickadoo": {
      "url": "https://mcp.tickadoo.com/mcp"
    }
  }
}

Use the npm package when your MCP client needs a local stdio command:

{
  "mcpServers": {
    "tickadoo": {
      "command": "npx",
      "args": ["-y", "@tickadoo/mcp-server"]
    }
  }
}

Configuration

Set TICKADOO_MCP_URL to point the bridge at another compatible Streamable HTTP MCP endpoint:

TICKADOO_MCP_URL=http://127.0.0.1:8787/mcp npx -y @tickadoo/mcp-server

Set TICKADOO_LOG_LEVEL=none to silence bridge status logs on stderr.

Local Development

npm install
npm run build
npm test

Run the built stdio bridge:

node dist/index.js

Refresh the MCP registry metadata from the live remote:

npm run sync:server-json

Run the optional live integration test:

LIVE=1 npm test

Live Tools

The current tool list is served by the remote MCP server. Visit mcp.tickadoo.com or run npm run sync:server-json to refresh the registry metadata in this repo.