Skip to main content
tickward exposes a remote MCP endpoint for clients that support hosted MCP servers and OAuth: 
https://mcp.tickward.com/mcp
Use these values when a client asks for connector metadata:
FieldValue
Nametickward
DescriptionManage countdown timers, projects, spaces, share links, and webhooks.
Server URLhttps://mcp.tickward.com/mcp
AuthenticationOAuth
Icon uploadDownload 256 x 256 PNG
Remote MCP uses your tickward account consent screen. API keys are for local scripts, CLI tools, and self-hosted agents that call the REST API directly. Do not paste an API key into the hosted remote MCP connector. tickward is not a prebuilt ChatGPT or Claude connector yet. Add it as a custom remote MCP connector. The icon upload file is a 256 x 256 PNG under 10 KB, which fits ChatGPT’s custom app icon limits.

​
Permissions

The consent screen groups OAuth scopes into three labels:
LabelMeaning
Read-onlyThe connector can inspect projects, timers, spaces, share links, and webhooks.
Scoped writeThe connector can write only for the selected resource scopes.
Full accessThe connector can read and write all supported MCP resources.
The scope list is authoritative. If a connector calls an endpoint outside its granted scopes, the API returns insufficient_scope with required_scope and granted_scopes in the error details. Reconnect the client with the missing scope when the user approves that broader access. Existing connections keep the scopes they were granted. Reconnect a client if you want it to use newly added webhook tools.

​
Web apps

The ChatGPT and Claude steps below describe how to add tickward from their web apps. Local CLI tools use the separate local-agent setup below.

​
ChatGPT

Use this path when ChatGPT shows Developer Mode or custom MCP app setup for your plan or workspace:
  1. Open ChatGPT settings, then go to Apps and Advanced settings.
  2. Enable Developer mode.
  3. Click Create app.
  4. For Connection, choose Server URL and enter https://mcp.tickward.com/mcp.
  5. Select OAuth authentication. For Registration method, choose Dynamic Client Registration.
  6. Scan tools, finish the OAuth flow, and create the app.
  7. In a chat, select Developer Mode and enable the tickward app.
Optional: click Advanced OAuth settings before creating the app if you want to review OAuth discovery details. Keep the discovered endpoint values. Use Dynamic Client Registration for the hosted tickward MCP server. Do not enter static client credentials, and do not choose Client Identifier Metadata Document. Use these default scopes if ChatGPT asks for them manually: 
projects:read
projects:write
timers:read
timers:write
spaces:read
spaces:write
shares:read
shares:write
webhooks:read
webhooks:write
The discovered endpoints should be:
FieldValue
Auth URLhttps://mcp.tickward.com/authorize
Token URLhttps://mcp.tickward.com/oauth/token
Registration URLhttps://mcp.tickward.com/oauth/register
Authorization server basehttps://mcp.tickward.com
Resourcehttps://mcp.tickward.com/mcp
ChatGPT availability and labels can vary by plan and workspace policy. If the custom app controls are not visible, use the REST API with an API key from tickward settings. Official OpenAI references:

​
Claude

Use this path when Claude shows custom connectors:
  1. Open Claude, then go to Customize and Connectors.
  2. Click +, then Add custom connector.
  3. Enter the tickward MCP server URL: https://mcp.tickward.com/mcp.
  4. Leave advanced OAuth client credentials empty unless your workspace requires static credentials.
  5. Add the connector, click Connect, and complete the tickward OAuth flow.
  6. Enable the connector for the conversation where you want to use it.
Official Anthropic reference:

​
Local agents

If your local agent supports remote HTTP MCP with OAuth, add the server URL: 
https://mcp.tickward.com/mcp
Common config shapes: 
codex mcp add tickward --url https://mcp.tickward.com/mcp

claude mcp add --transport http tickward https://mcp.tickward.com/mcp

{
  "mcpServers": {
    "tickward": {
      "url": "https://mcp.tickward.com/mcp"
    }
  }
}
If the agent cannot complete remote MCP OAuth, create an API key in tickward settings and call the REST API directly: 
Authorization: Bearer tw_your_api_key
Prefer read-only keys for lookup workflows. Use full-access keys only for changes the user explicitly requested.

​
Self-hosted MCP

Self-hosted deployments can run the separate tickward MCP Worker and point it at their own tickward app/API domain. After deployment, set this in the tickward app environment: 
TICKWARD_MCP_REMOTE_URL=https://mcp.example.com/mcp
The Settings page will then show the remote MCP URL for that deployment.