Add TimeTackle remote MCP server

[uaday]

---

name: Tackle(timetackle.com) MCP server
about: Requests for adding a new MCP server to the Docker Catalog
title: "Add Tackle MCP server (remote, streamable-http)"
labels: submission

MCP Server Information

Server Name: Tackle (timetackle.com)

Repository URL: Private repo

Brief Description: Remote MCP server for Tackle — calendars, events, automations, and analytics. Single HTTP endpoint (streamable-http transport). OAuth with Bearer token; supports token via Authorization header, query (access_token/token), or headers (X-Access-Token/X-Bearer-Token). Tools: get_account, get_imported_calendars, get_all_calendars, get_events, get_properties, add_property_to_event, add_property_to_events, get_automations, create_automation. Documentation: https://timetackle.gitbook.io/tackle/mcp-server/overview

Endpoint: https://mcp.timetackle.com/mcp (POST, JSON-RPC)

Transport: streamable-http

Authentication: OAuth (Bearer token). Users run docker mcp oauth authorize timetackle to sign in.

---

Basic Requirements

• Open Source: Uses acceptable license (Apache-2.0, MIT, BSD-2-Clause, BSD-3-Clause or other permissive license)
• MCP Compliant: Implements MCP API specification (initialize, tools/list, tools/call over HTTP)
• Active Development: Recent commits and maintained
• Docker Artifact: Dockerfile — N/A for remote server (hosted at https://mcp.timetackle.com)
• Documentation: Basic README and setup instructions — https://timetackle.gitbook.io/tackle/mcp-server/overview
• Security Contact: Method for reporting security issues (add if you have one; e.g. developer@timetackle.com or GitHub Security Advisories)

---

Submitter Checklist

• This server meets the basic requirements listed above (remote server: no Dockerfile required)
• I understand this will undergo automated and manual review.
• I have tested the remote server using task catalog -- tackle then docker mcp catalog import $PWD/catalogs/tackle/catalog.yaml after that docker mcp oauth authorize tackle and docker mcp gateway run
• Build step — N/A for remote servers (no task build -- --tools; tools are discovered dynamically)
• If the server requires credentials to test it, I have shared test credentials using this form

---

Files in this PR (under servers/tackle/)

• server.yaml — name: tackle, type: remote, transport_type: streamable-http, url: https://mcp.timetackle.com/mcp, about + OAuth
• tools.json — [] (dynamic tool discovery)
• readme.md — documentation link and endpoint description